OPM Publishes Correction to Reduction-in-Force Final Rule
The Office of Personnel Management issued a final rule correcting typographical and clerical errors in its August 3 reduction-in-force rule.
3 reports on this incident · first at Aug 25, 2026, 1:37 a.m. ET
Earlier reports
Aug 25, 2026, 1:53 a.m. ET
OPM Correction to Reduction-in-Force Rule Takes Effect Sept. 2
The Office of Personnel Management (OPM) published a final rule in the Federal Register on August 25, 2026, correcting typographical and clerical errors in its earlier reduction-in-force final rule. The correction takes effect on September 2, 2026, according to the Federal Register document (reference 2026-17335).
The original final rule, published August 3, 2026, contained errors in amendatory instructions and regulatory text. This document corrects those errors.
Aug 25, 2026, 1:37 a.m. ETFirst report
OPM Publishes Correction to Reduction-in-Force Final Rule
The Office of Personnel Management (OPM) published a correction in the Federal Register on August 25, 2026, to address typographical and clerical errors in a final rule concerning reduction in force. The original final rule was published on August 3, 2026, and contained errors in amendatory instructions and regulatory text, according to the Federal Register document (reference 2026-17335).
The correction is effective on September 2, 2026. The document is identified as a final rule correction and is part of the official record.
Was this report accurate and useful?
Sources
Revision history
- Version 125 Aug 2026, 06:23current
First published.
- Version 125 Aug 2026, 05:53current
First published.
- Version 125 Aug 2026, 05:37current
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.