This bill amends the Child Care and Development Block Grant Act of 1990 by removing statutory language that allowed sanctions imposed on States to be waived. Specifically, it targets section 658I(c) (42 U.S.C. 9858lg(c)) and excises multiple references to waiving or suspending sanctions so that penalties imposed under the Act must be sustained.
For state agencies, federal administrators, and compliance teams, the bill replaces administrative flexibility with a hard line: once a sanction under the cited provision is applied, the statute will no longer include the previously available waiver language. That changes the enforcement posture of the federal grant program and raises practical questions about how sanctions will be used and litigated going forward.
At a Glance
What It Does
The bill amends 42 U.S.C. 9858lg(c) by striking language across several subsections that referenced waiving, suspending, or otherwise excepting sanctions imposed under the Child Care and Development Block Grant Act. Those textual deletions remove statutory waiver options and leave sanctions in place once imposed.
Who It Affects
Primary targets are state agencies that administer CCDBG funds and the Department of Health and Human Services (Administration for Children and Families) which enforces the statute. Secondary impacts reach child care providers and low-income families if sanctions translate into reduced federal funding or program disruptions.
Why It Matters
The change narrows enforcement discretion at the statutory level, limiting agency ability to mitigate penalties for noncompliance (including fraud or improper use of funds). For compliance officers this alters risk calculus: the statutory backstop of waivers disappears and the likelihood of sustained fiscal penalties rises.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
HB 7724 is narrowly written but consequential. It targets one enforcement lever in the Child Care and Development Block Grant Act of 1990 by editing section 658I(c) — codified at 42 U.S.C. 9858lg(c) — to remove several phrases that previously allowed sanctions to be waived or excepted.
The bill does not create new sanctions or change the criteria for imposing them; it removes statutory language that provided an escape hatch from those penalties.
Concretely, the bill instructs Congress's chosen statute to say less about waiver authority: across multiple enumerated paragraphs it strikes words and phrases such as references to waiving sanctions imposed under subsection (b)(2) and repeated instances of the phrase "sanction or". Those targeted deletions narrow the statutory text so that the list of enforcement options no longer includes waiver language in the cited clauses.Because the bill edits only the text that references waivers, it leaves in place the underlying enforcement regime — the bases for imposing sanctions, the administrative processes for notice and correction, and any referral mechanisms — unless those are separately changed elsewhere.
The practical consequence will therefore come from reduced administrative discretion: agencies that previously relied on express statutory waiver authority will need to use other tools (policy, regulation, or case-by-case settlement) if they want to mitigate penalties, or they will have to accept that certain sanctions, once applied, will be maintained.That shift matters operationally. States and their legal counsel will have less statutory cover to negotiate or seek relief after enforcement findings.
HHS and program offices will face a clearer statutory imperative to sustain sanctions as written; that may increase the frequency of formal penalties, raise the stakes of enforcement findings, and push more disputes into administrative appeals or federal court. The bill does not appropriate funds or add new procedural safeguards, so the enforcement consequences will play out within existing administrative resources and timelines.
The Five Things You Need to Know
The bill amends the Child Care and Development Block Grant Act of 1990 by modifying 42 U.S.C. 9858lg(c) (section 658I(c)).
It removes the phrase that permitted waiving sanctions imposed under subsection (b)(2), eliminating that explicit waiver pathway.
The text deletions target five places in subsection (c): paragraph (1), paragraph (2) subparagraphs (A) and (B), paragraph (3), and paragraph (7).
The bill does not change the statutory grounds for imposing sanctions or add new penalties—only the ability (in the targeted clauses) to waive or except those sanctions.
Because it is a standalone statutory edit, the effect is immediate in law if enacted: enforcement discretion that relied on the removed language would no longer rest on express waiver authority in 42 U.S.C. 9858lg(c).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title — "No Waivers for Fraud Act"
This establishes the bill’s name. The title signals legislative intent but has no legal effect on enforcement mechanics; it frames the amendments in the context of preventing waiver of sanctions related to fraud or misuse of CCDBG funds.
Remove waiver reference to sanctions under subsection (b)(2)
Paragraph (1) currently includes an explicit reference allowing waivers or exceptions for sanctions imposed under subsection (b)(2). The amendment strikes that clause, meaning sanctions tied to subsection (b)(2) will no longer have an express statutory waiver option in paragraph (1). Practically, this reduces a clear statutory avenue for relief after certain enforcement findings.
Delete repeated "sanction or" language in paragraph (2)
Paragraph (2) contains subparagraphs (A) and (B) that the bill edits by removing the words "sanction or." Those deletions narrow the textual list of remedies or exceptions set out in paragraph (2). Administratively, the change makes paragraph (2) read without an express waiver option, constraining the statutory catalog of flexibility available to the Secretary or agency officials.
Strip "sanction or" phrasing from paragraph (3)
The bill strikes the phrase "sanction or" in paragraph (3), further eliminating instances where the statute provided or contemplated waiving sanctions. While a small textual edit, cumulatively these deletions remove the statutory pattern of waiver-language that could have been used to temper penalties.
Remove "sanction(s) or" from paragraph (7)
Paragraph (7) loses the term "sanction(s) or," completing the set of deletions across subsection (c). Together with the other struck phrases, this makes subsection (c) silent where it previously recognized waiver or exception authority tied to sanctions — an absence that will be treated as a statutory limitation on waiver authority.
This bill is one of many.
Codify tracks hundreds of bills on Social Services across all five countries.
Explore Social Services in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Federal taxpayers — by removing an explicit statutory waiver pathway, the bill increases the likelihood that sanctions tied to misuse of federal child care funds will be sustained, which could reduce improper spending.
- Program integrity advocates and auditors — they gain a statutory environment less permissive of post‑finding exceptions, strengthening enforcement outcomes and precedent for strict accountability.
- Compliant states and providers — they benefit indirectly because consistent enforcement reduces competitive advantages for badly performing actors and can improve program fairness.
Who Bears the Cost
- State child care subsidy agencies — they face higher enforcement risk because removed waiver language reduces a statutory fallback; states may incur more litigation and administrative costs defending against sustained sanctions.
- Low‑income families and providers in sanctioned states — if sanctions result in funding reductions or program disruptions, service availability could decline, imposing immediate welfare costs on beneficiaries.
- HHS/ACF enforcement offices — stricter statutory obligations can increase administrative burdens (appeals, hearings, case development) without adding resources, potentially stretching program office capacity.
Key Issues
The Core Tension
The bill resolves one problem—curbing post‑finding waivers that can let sanctioned states avoid penalties—but creates another: removing statutory flexibility may increase vindictive or technocratic enforcement that harms program beneficiaries and triggers more litigation, forcing a choice between uncompromising accountability and program stability.
The bill is textually narrow but substantively consequential because it eliminates explicit statutory language authorizing waivers of sanctions; however, it does not address substitute mechanisms. That raises two implementation problems.
First, agencies often rely on a combination of statute, regulation, and negotiated settlements to manage enforcement; removing statutory waiver language does not prevent agencies from using settlements or other non‑statutory tools to achieve similar outcomes, but it does increase legal risk and uncertainty when those tools are deployed. Second, by hardening sanctions in statute without adding procedural guardrails or funding for oversight, the bill may increase the frequency and stakes of enforcement disputes, producing more appeals or litigation and potentially incentivizing aggressive penalty use.
A second tension is operational: CCDBG programs frequently involve complex eligibility and reporting systems across counties and providers. Strict removal of waiver authority may lead to sustained penalties for technical compliance failures rather than substantive fraud, producing perverse outcomes—loss of funds and service disruptions for families—when the underlying harms are programmatic rather than fraudulent.
The statute’s silence on waivers transfers the discretion (and the political pressure) from an explicit statutory tool to administrative practice, case law, and intergovernmental negotiation. That shift creates uncertainty about how enforcement will play out in practice and whether the intended anti‑fraud effect will be achieved without collateral damage.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.