Federal Register Deadline Calendar — Comments & Rules

Which US federal regulatory deadlines land in the next N days, sorted by how little time is left. Comment periods closing on proposed rules, and final rules taking effect.

The data is the official Federal Register API — free, public, no key. One request returns the whole universe for each deadline type, so the calendar is complete rather than a sample.

What you get per deadline

Field	Example
deadline / daysRemaining / urgency	2026-10-13 / 2 / within_7_days
deadlineTypeLabel	Comment period closing or Rule taking effect
isSignificant	true, false or null — see the note below
title / action / abstract	what the document actually does
primaryAgency / agencies / agencyCount	Environmental Protection Agency
cfrTitles / cfrReferences	[40] / ["40 CFR 261"]
rin / docketIds / documentNumber	the identifiers you need to file a comment
primaryAgencyDeadlinesInResult	how many deadlines that agency has in this run
url	the Federal Register page

urgency is one of today, within_7_days, within_14_days, within_30_days, within_90_days, over_90_days. A deadline that closes today is today, not past.

Two dataset views: Deadline calendar (what is due and when) and Docket detail (RIN, docket IDs and CFR references, for actually filing).

Filters

• Days ahead — measured on 2026-10-11: of 186 open comment periods, 25 closed within 7 days, 58 within 14 and 122 within 30.
• Agencies — Federal Register slugs such as environmental-protection-agency.
• Keywords — full-text, e.g. PFAS, cybersecurity.
• CFR titles — numbers, e.g. 40 for environment, 17 for securities.
• Significant rules only.

Two things worth knowing about the source

The API's sort parameter is ignored. Passing order=comment_date, order=effective_date, order=newest or order=relevance returns exactly the same results, and the actual order is publication date descending. So sorting by days remaining — the whole point of a deadline calendar — is done by this Actor, not by the API. That is stated plainly in the output caveats rather than implied.

isSignificant has three states. true, false, and null. A null means the document carries no flag, not that it is insignificant. significantOnly keeps only true, and the summary counts only true.

How it checks its own output

Check	What it catches
Truncated universe	If the API reports more documents than were fetched, the run stops — an incomplete calendar is worse than none. Measured: 186 documents arrive in one request, so this should not fire unless the universe grows.
Missing deadline dates	Documents selected by a date condition should carry that date. Measured: zero missing out of 186. A material share missing means the filter and the field have come apart.
Filter ignored	A "not before today" condition should not return expired deadlines. Measured: zero expired out of 186. Checked rather than assumed, because two other public APIs were observed silently ignoring query parameters the same week.
Unknown deadline type	Rejected, not silently dropped — dropping one type hides half of what the user asked for.
Unknown agency slug	Checked against the official agency list before searching, and refused with the closest matching slugs. The API itself answers a misspelled slug with HTTP 400.
Nothing matches	Zero deadlines under your filters is a valid answer: the run succeeds with no rows and its status message says what was searched.
Request failure	A non-200 response is raised, not returned as an empty calendar.

Notes on the data

• Comment deadlines come from proposed rules; effective dates come from final rules. Notices and presidential documents are out of scope.
• A deadline is the date printed in the Federal Register. Agencies can extend or reopen a comment period, and an extension is published as a separate document — this Actor does not merge the two into one timeline.
• Agency filtering uses slugs, not display names.
• This is a deadline-tracking tool, not legal advice.