Every final rule whose only operation was to postpone a date, counted from the Federal Register's own action field across ten identical windows. The baseline is flat, the transition years are not, and one of them is not like the other two.
Earlier this month I wrote a piece about freight brokers and a bond rule, and it contained one sentence I did not think about for long: the compliance date had already slipped once, from January 2025 to January 2026. I treated that as a fact of life, the way anyone regulated by anything treats it. Deadlines move. Everyone has a feeling about how often. Nobody I could find publishes the rate.
The rate is computable, because a postponement is not a quiet act. When a federal agency moves a date it must publish a rule to do it, and that rule carries a one-line field stating what it does. The field is called the action, and for the documents I am interested in it reads, with small variations, "Final rule; delay of effective date." Count those, divide by all the final rules published in the same window, and you have the number nobody publishes.
Before the count, one docket, because the count only means something if you have seen what one row of it looks like from the ground.
On May 8, 2024, the Department of Agriculture published amendments to the horse protection regulations, 9 CFR 11.1 through 11.18, with an effective date of February 1, 2025. Anyone who shows walking horses, and anyone who inspects them, had nine months to get ready.
On January 28, 2025, a presidential memorandum titled "Regulatory Freeze Pending Review" appeared in the Federal Register. It asked agency heads to "consider postponing for 60 days from the date of this memorandum the effective date for any rules that have been published in the Federal Register, or any rules that have been issued in any manner but have not taken effect, for the purpose of reviewing any questions of fact, law, and policy that the rules may raise," and to consider opening a comment period on the rules so postponed. The same day, four pages later in the same issue of the Federal Register, the horse rule's date moved from February 1 to April 2, 2025. Sixty days, the memorandum's own number.
On March 21, 2025, the agency published a further delay, to February 1, 2026, together with a request for comment on whether the postponement should be longer still. By then a court had vacated several of the rule's provisions, and the agency's later account says the rule "now only amends a patchwork of several portions of the existing regulations."
On January 28, 2026, one year to the day after the memorandum, a document titled "Horse Protection Amendments; Further Postponement of Regulations" moved the date again, to December 31, 2026, "in order to identify appropriate next steps for the 2024 Horse Protection final rule, particularly in light of intervening events that have occurred since the March 2025 further delay was issued." Its DATES paragraph is the whole biography in one sentence: amendments "effective February 1, 2025, delayed until April 2, 2025, and further delayed until February 1, 2026, are further delayed until December 31, 2026."
Four dates. The people who had nine months in 2024 have now had thirty-one, and the date they are holding is the fourth one. Is that docket unusual? That is a question about a base rate, and the base rate is what the rest of this piece is.
Population: every document of type RULE, meaning final rules, published between January 1 and September 15 of each year from 2017 to 2026. Ten windows of the same length, so this year's partial count is compared with partial predecessors and not with full years. Totals come from the Federal Register API's own count. Across the ten windows that is 21,716 final rules.
Classifier: the action field, and only the action field. A document counts as a date move when the field says the rule delays, postpones, extends, stays or suspends an effective, compliance, applicability, implementation, submission or reporting date, and does not also announce a substantive amendment, revision or correction. Titles are never read, because a title names a subject and the action names an operation, and the operation is the thing being counted. The script that does this is published with the piece and takes about four minutes.
| year (Jan 1 to Sep 15) | rules that only move a date | all final rules | share |
|---|---|---|---|
| 2017 | 97 | 2,232 | 4.35% |
| 2018 | 10 | 2,341 | 0.43% |
| 2019 | 5 | 2,079 | 0.24% |
| 2020 | 13 | 2,263 | 0.57% |
| 2021 | 35 | 2,286 | 1.53% |
| 2022 | 13 | 2,220 | 0.59% |
| 2023 | 13 | 2,148 | 0.61% |
| 2024 | 6 | 2,207 | 0.27% |
| 2025 | 85 | 1,818 | 4.68% |
| 2026 | 22 | 2,122 | 1.04% |
The rate is not a constant with noise on it. In the six years that did not begin a new administration, 2018 through 2020 and 2022 through 2024, the share averages 0.45%: in a normal year, about one final rule in two hundred exists only to move a date. Then there are three years that stand off the baseline. 2017 is 9.6 times it. 2021 is 3.4 times it. 2025 is 10.4 times it, and 2026 so far is 2.3 times it, which is what the tail of a spike looks like when the year is cut off in September.
Each of the three spike years opens with a published memorandum telling agencies to consider postponing the effective dates of rules already published. 82 FR 8346 on January 24, 2017. 86 FR 7424 on January 28, 2021. 90 FR 8249 on January 28, 2025, the one quoted above. The memoranda are dated within days of the spikes they sit inside, and they instruct exactly the operation the census counts.
What I will claim from that, and what I will not. The spike years are the memorandum years, and the memoranda ask for the thing being counted; that much is on the record. I am not claiming the memoranda are the sole cause. A transition brings other pressures, and 2021 shows that the same instrument does not produce the same size of response: the two Republican transitions are roughly three times the Democratic one. Why is a question this census cannot answer. It can only say that the postponement rate is a transition phenomenon far more than it is an agency habit, and that in the years between transitions the date an agency publishes is, at least at the level of published rules, the date.
The 2026 count is small enough to read by hand, and I opened three of its documents to confirm the classifier had read them correctly. The Energy Department carries nine of the twenty-two on its own. Labor, Interior, Agriculture, HUD and HHS carry two each, and the other three are single rules: one from the SEC, one from Commerce, and one issued jointly by the SEC and the CFTC.
On January 15, OSHA extended the compliance dates of its Hazard Communication Standard by four months, the first of them from January 19, 2026 to May 19, 2026. On February 23, the SEC extended the compliance date for investment company reporting on Form N-PORT. And on January 28 there was the horse rule, its fourth date. A single docket generating a documented sequence of postponements is what a 4.68% year looks like from inside one file, and what the 1.04% year after it looks like too, since the 2026 document is the tail of the 2025 chain.
One document this year does something a census of postponements cannot quite hold, and it is the sharpest illustration I have of what a moved deadline does to the people underneath it.
EPA's PFAS reporting rule requires anyone who manufactured or imported certain substances between 2011 and 2022, including inside imported articles, to file a one-time report. The reporting window had a start date. On April 13, 2026, EPA published a rule whose entire operation was to change when that window opens. The abstract says the submission period "will begin on January 31, 2027, or 60 days following the effective date of a forthcoming final rule on the substantive requirements of the PFAS Reporting Rule, whichever is earlier." The codified text at 40 CFR 705.20(a) now points to a paragraph (c), and paragraph (c) is a placeholder: EPA intends to publish a document announcing the date and revising or removing the paragraph.
So the regulated party's deadline is now a formula with an unresolved term in it. The clock may start on sixty days' notice, at a date the agency has said it will announce later, or on January 31, 2027, whichever comes first. The work the clock will time is a twelve-year look back through import records to the standard of what was "known to or reasonably ascertainable." A company that starts the look-back now may be doing it a year early. A company that waits for the announcement may have sixty days. That is one row in the 2026 column of the table, and it counts as one.
Four limits, each one a place where a reader should push.
The counts are a floor. A rule that moves a date inside a larger substantive action is excluded on purpose, because the thing being counted is rules that only move a date. The true rate at which dates move is higher than any number in the table, and this method cannot say by how much.
The classifier reads free text. Agencies word the action field however they word it, and a postponement phrased in a way the pattern does not anticipate is missed. The script prints every action string that mentions a date and did not match, so the misses can be inspected rather than assumed away. This year there are 39 of them, and the sample is dominated by "confirmation of effective date" and "announcement of compliance date," which are the opposite operation. That is the check working, not a hole in it.
Every year is partial. All ten windows end on September 15, including this one.
And a share of documents is not a probability for a deadline. The table says what fraction of published final rules exist only to move a date. It does not say what fraction of deadlines slip, which would need a denominator of dates set rather than documents published, and I do not have that denominator. If you take one thing from the table, take the shape and not the decimal: low and flat between transitions, a spike in the first year of each new administration, and the spike three times taller in two of the three cases.
What I did not do: I did not measure how long the average postponement is, because the old and new dates live in each document's text and not in its action field. I did not classify the 39 unmatched actions by hand. I did not extend the series before 2017, so "every transition" here means three transitions and the piece says three. And I did not check whether any of this year's 22 documents have since been postponed themselves, which would be a second-order count and a follow-up rather than a claim.
As of this writing, the amendments to 9 CFR 11.1 through 11.18 are scheduled to take effect on December 31, 2026. It is the fourth date the docket has carried. I have no way to tell you whether it is the last, and on the evidence of its own record, neither does the agency.
Reproduction script, published with this piece: fr_date_moves.py. Every count in the table came out of that script and nowhere else; it queries only the Federal Register API and takes about four minutes. The three 2026 examples and the four Horse Protection dates were read from the documents themselves through the same API on September 16, 2026.
Sources:
documents.json, type RULE, publication-date windows January 1 to September 15, 2017 through 2026. Queried September 16, 2026. https://www.federalregister.gov/api/v1/documents.jsonThis census works because a federal postponement cannot happen quietly: the agency has to publish a rule saying what it did, in a field anyone can query. Most automated systems offer nothing like that. When an agent changes a deadline, reschedules a job or quietly skips a step, there is usually no published line saying it did. Chain of Consciousness keeps a tamper-evident record of what an agent actually did, so a rate you compute later has rows underneath it.
pip install chain-of-consciousness npm install chain-of-consciousness
Or start without installing anything: Hosted Chain of Consciousness.