Federal Register Deadlines
Pricing
$3.00 / 1,000 regulatory documents
Federal Register Deadlines
US regulations with the days remaining until the comment period closes or the rule takes effect — the countdown the Federal Register never publishes. Sorted by urgency.
US regulations with the days remaining until the comment period closes or the rule takes effect — sorted by urgency.
No login. No API key. No proxies.
The countdown the source never prints
The Federal Register publishes two dates that bind a company: when the comment period on a proposed rule closes, and when a final rule takes effect. It never publishes the number of days left.
That is the only number a regulatory affairs team actually works from. Which proposals affecting us are still open, and how long have we got?
This Actor does the subtraction on every row, flags what is still open, and sorts so the tightest deadline is first. A real run, 13 September 2026:
| Document | Agency | Days left |
|---|---|---|
| Request for Information; Clinical Laboratory Improvement | HHS | 1 |
| Medicare and Medicaid Programs; CY 2027 Payment Policies | HHS | 1 |
| Accreditation, Innovation and Modernization | Education | 8 |
Three comment periods closing within eight days, two of them tomorrow — visible in one column instead of thirty PDF pages.
Output
| Field | Example |
|---|---|
title, type, action | Proposed Rule; request for comments |
agencies | Health and Human Services, Food and Drug Administration |
commentsCloseOn | 2026-09-14 |
daysUntilCommentClose | 1 |
effectiveOn, daysUntilEffective | 2026-11-01, 49 |
commentPeriodOpen, alreadyEffective | true / false |
significant | flagged under Executive Order 12866 |
cfrReferences | 21 CFR 101 |
docketIds, regulationIdNumbers | FDA-2026-N-1234, RIN 0910-AI43 |
documentNumber, citation, startPage, pageLength | |
abstract, topics | |
htmlUrl, pdfUrl | the document itself |
A negative daysUntilEffective means the rule is already in force. A null
means no date was set — not that there is no deadline, so check the
document.
Input
{"documentType": "proposed-rules","openForCommentOnly": true,"searchTerm": "artificial intelligence","maxItems": 300}
| Field | Default | Notes |
|---|---|---|
documentType | proposed-rules | Proposed, final, notices, presidential |
openForCommentOnly | true | Only what you can still influence |
searchTerm | artificial intelligence | Full text |
maxItems | 300 | Sorted by nearest deadline |
agencies | — | Slugs, e.g. food-and-drug-administration |
cfrTitle | — | 21 food and drugs, 40 environment, 47 telecoms |
publishedAfter | — | YYYY-MM-DD |
significantOnly | false | Economically significant rules |
Proposed rules are the ones you can change. Final rules are the ones you must comply with. Pick the type that matches the job.
Use cases
- Regulatory affairs — every open consultation touching your CFR title, ranked by how soon it closes.
- Public affairs and lobbying — where comment windows are still open, and how much time is left to file.
- Compliance planning — final rules and their effective dates, so deadlines reach the calendar before they reach you.
- Competitive and policy monitoring — what a given agency is proposing, continuously.
- Legal research — docket numbers, RINs and CFR references for follow-up on Regulations.gov.
Limits, honestly
- Deadlines come from the source. Agencies extend and reopen comment periods; a date read today can move tomorrow. Re-run before relying on it.
daysUntilCommentCloseis calculated against the run date, so a stored export ages. The dates themselves do not.- Not every document carries a comment or effective date — notices often carry neither. Those sort last rather than being dropped.
- The API stops paginating deep result sets. Narrow by agency, CFR title or date rather than sweeping everything.
- Agency filters use the Federal Register's own slugs, which are not always the agency's common name.
- Requests are paced out of courtesy to a free public service.
- Not affiliated with the Office of the Federal Register.