HUD Issues Supplemental Rule on Title VI Disparate-Impact Liability
Official records show HUD is proposing to remove disparate-impact liability provisions from its Title VI regulations.
2 reports on this incident · first at Aug 20, 2026, 7:41 a.m. ET
Earlier reports
Aug 20, 2026, 7:41 a.m. ETFirst report
HUD Issues Supplemental Proposed Rule on Title VI Disparate-Impact Regulations
According to official Federal Register records published on August 10, 2026, under reference 2026-16228, the Housing and Urban Development Department (HUD) has issued a supplemental notice of proposed rulemaking. The proceeding remains open and developing as public feedback is collected.
Official records show that HUD published a notice of proposed rulemaking in January 2026 that proposed to remove HUD's disparate-impact regulations and leave interpretation of disparate-impact liability under the Fair Housing Act to the courts. This supplemental notice continues HUD's efforts to remove or revise regulations that prohibit conduct having a disparate impact without evidence of discriminatory intent. Through the rule, HUD proposes to remove provisions in its Title VI implementing regulations that impose disparate-impact liability on recipients of HUD Federal financial assistance. HUD stated that if finalized, the rule would improve consistency within its regulations and with Title VI regulations recently revised by the Department of Justice.
According to official records, this rule reopens the public comment period for HUD's January 2026 proposed rule on disparate-impact liability. HUD will only consider comments on topics related to this supplemental notice of proposed rulemaking during the reopened comment period, which closes on October 9, 2026.
Was this report accurate and useful?
Sources
Revision history
- Version 120 Aug 2026, 11:53current
First published.
- Version 120 Aug 2026, 11:41current
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.