Bill
H 3401
Massachusetts H 3401 would require state-funded construction contracts to include a firm two-year completion schedule with a 10% monthly penalty for delays, potentially shaping pro
Note: The legislative record provided for H 3401 contains two distinct and inconsistent texts. One is a short Massachusetts bill introduced by Rep. Kelly W. Pease concerning state‑funded construction work. The other is an extensive “Technology Transparency” draft (appearing to be a South Carolina-style privacy/technology chapter) that is longer and partially truncated. Below I summarize each text and then note the bill’s procedural timeline and likely impacts.
Purpose
- Require state agencies to include firm timelines in state‑funded construction contracts and impose financial penalties for delays.
Key provisions
- All Commonwealth agency construction contracts must specify a two‑year schedule for project completion (notwithstanding other laws, including Chapter 149).
- Failure to complete within the two‑year schedule triggers a financial penalty equal to 10% of the contract value, “levied each month until the project is concluded.” (Text as filed.)
- Contractors encountering unforeseen issues may submit a written explanation and appeal to the Commissioner of the Division of Capital Asset Management and Maintenance (DCAMM) for an extension of up to six months.
- The Commissioner is authorized to promulgate rules and regulations governing the appeal/extension process.
- Effective upon passage.
Who is affected
- State agencies that award and manage construction contracts.
- Contractors and construction firms bidding on or performing state projects.
- DCAMM (commissioner) — responsible for appeal process and rulemaking.
- Taxpayers indirectly, through potential changes to project costs, contract pricing, and schedule management.
Potential impacts and considerations
- Strong financial penalties could incentivize faster completion but may lead contractors to increase bids (to cover risk), pursue more change orders, or litigate disputes.
- Monthly 10% penalty compounded each month, as written, could create extraordinarily large liabilities — courts or contracting officers may contest applicability or interpretation.
- The six‑month extension process centralizes discretion with DCAMM; the administrative burden to evaluate extensions could increase.
- May conflict with existing procurement and public construction statutes; litigation or rulemaking may be required to reconcile.
Purpose (high level)
- Establish definitions and substantive rules around governmental interactions with social media platforms, consumer privacy rights, controller/processor duties, prohibition on dark patterns, limits on processing or sale of certain personal data, appeals and enforcement mechanisms.
Key highlights (from available excerpts)
- Extensive definitions: “Affiliate,” “Aggregate consumer information,” “Controller,” “Processor,” “Biometric data,” “Dark pattern,” “Deidentified data,” “Governmental entity,” etc.
- “Controller” is narrowly defined to include entities with >$1 billion global annual revenue and additional criteria (e.g., deriving ≥50% revenue from online ads, operating certain smart speakers, or operating an app store with ≥250,000 apps).
- Provisions (implied by headings) to:
- Prohibit certain governmental communications with social media platforms in specified instances.
- Create consumer rights (access, deletion, opt‑out, appeals).
- Void contracts or agreements that waive these rights.
- Require privacy notices, data protection assessments, and duties for controllers/processors.
- Prohibit processing of certain personal data and sale of certain personal data.
- Treat violations as unfair and deceptive trade practices (enforcement/penalties).
- The draft is truncated; full scope and enforcement details are not present in the provided text.
Who is affected
- Large technology platforms/companies meeting the “controller” thresholds.
- State and local governmental entities (limits on communications with platforms).
- Consumers within the state (new rights and remedies).
- Businesses acting as processors or controllers for consumer data.
Potential impacts and considerations
- Targets a narrow class of very large tech companies, but could have broad compliance costs for affected entities.
- Intersects with federal law and existing state privacy statutes; definitions (e.g., revenue thresholds, “sale” of data) determine reach.
- Treating violations as unfair/deceptive trade practices opens consumer protection enforcement and private civil actions.
Compiled from official sources — confirm details with the bill’s official record.
Sign in to ask a question.
