425 records

Which federal rules take effect in 2026, 2027 and later?

425 records, one fact each. Every value is transcribed from the source that states it and carries the sentence it was taken from: 5 sources across 1 site, last checked 2026-09-18, due for re-check by 2026-09-29. Every record has a page of its own, quoting the line that states it.

Recent changes

• 2026-09-1510 records added or updated
• 2026-09-1439 records added or updated
• 2026-09-0724 records added or updated
• 2026-09-0114 records added or updated
• 2026-08-31104 records added or updated

Full change history · Atom feed

About this data

415 US final rules already published in the Federal Register, listed by the date each one takes effect: 364 in 2026, 44 in 2027 and 7 in 2028 or later, from 66 agencies, running to March 2033. Every record carries the agency, the CFR parts it amends, the effective date as the rule prints it, and the rule's verbatim DATES paragraph. Answers 'which federal regulations take effect on January 1, 2027', 'what rules affecting 47 CFR part 10 are already published but not yet in force', 'what is the compliance date for the DOJ web accessibility rule', and 'what changes are coming for my industry that are already law'. The hard part is that a rule published in 2023 can carry a 2026 or 2033 effective date: the obligation is already binding law, it is nowhere near the front page, and the only way to find it is to know it exists. This is the enumeration keyed on effective date, not a list of things that have not happened yet: a rule stays listed after its date passes until the next re-harvest moves the window, so 196 of the 415 had already taken effect when this was counted on 2026-09-14.

The data

Showing the first 400 of 425 records. Every record has its own page, with its source and the quoted line that states it; these list the rest.

• Records 1–4002026-13685 … 2026-15576
• Records 401–4252026-15577 … 2026-04368

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 5 sources this dataset was assembled from.

• federalregister.govhttps://www.federalregister.gov/api/v1/documents.json?per_page=1000&order=oldest&conditions%5Btype%5D%5B%5D=RULE&conditions%5Beffective_date%5D%5Bgte%5D=2026-08-11&conditions%5Beffective_date%5D%5Blte%5D=2026-12-31&fields%5B%5D=document_number&fields%5B%5D=title&fields%5B%5D=agency_names&fields%5B%5D=effective_on&fields%5B%5D=dates&fields%5B%5D=cfr_references&fields%5B%5D=publication_date&fields%5B%5D=html_url
• federalregister.govhttps://www.federalregister.gov/api/v1/documents.json?per_page=1000&order=oldest&conditions%5Btype%5D%5B%5D=RULE&conditions%5Beffective_date%5D%5Bgte%5D=2026-08-31&conditions%5Beffective_date%5D%5Blte%5D=2026-12-31&fields%5B%5D=document_number&fields%5B%5D=title&fields%5B%5D=agency_names&fields%5B%5D=effective_on&fields%5B%5D=dates&fields%5B%5D=cfr_references&fields%5B%5D=publication_date&fields%5B%5D=html_url
• federalregister.govhttps://www.federalregister.gov/api/v1/documents.json?per_page=1000&order=oldest&conditions%5Btype%5D%5B%5D=RULE&conditions%5Beffective_date%5D%5Bgte%5D=2027-01-01&conditions%5Beffective_date%5D%5Blte%5D=2027-12-31&fields%5B%5D=document_number&fields%5B%5D=title&fields%5B%5D=agency_names&fields%5B%5D=effective_on&fields%5B%5D=dates&fields%5B%5D=cfr_references&fields%5B%5D=publication_date&fields%5B%5D=html_url
• federalregister.govhttps://www.federalregister.gov/api/v1/documents.json?per_page=1000&order=oldest&conditions%5Btype%5D%5B%5D=RULE&conditions%5Beffective_date%5D%5Bgte%5D=2028-01-01&conditions%5Beffective_date%5D%5Blte%5D=2029-12-31&fields%5B%5D=document_number&fields%5B%5D=title&fields%5B%5D=agency_names&fields%5B%5D=effective_on&fields%5B%5D=dates&fields%5B%5D=cfr_references&fields%5B%5D=publication_date&fields%5B%5D=html_url
• federalregister.govhttps://www.federalregister.gov/api/v1/documents.json?per_page=1000&order=oldest&conditions%5Btype%5D%5B%5D=RULE&conditions%5Beffective_date%5D%5Bgte%5D=2030-01-01&conditions%5Beffective_date%5D%5Blte%5D=2040-12-31&fields%5B%5D=document_number&fields%5B%5D=title&fields%5B%5D=agency_names&fields%5B%5D=effective_on&fields%5B%5D=dates&fields%5B%5D=cfr_references&fields%5B%5D=publication_date&fields%5B%5D=html_url

Machine-readable

• data.jsonThe whole dataset — every record with its source URL and source quote.
• Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
• data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
• changes.xmlAtom feed of what changed and when — poll this instead of re-fetching the dataset. Also as changes.json.
• What changedThe same change history as a readable page — each date, what moved, and the records' current state.
• calendar.icsEvery date in this dataset as an all-day calendar entry. Subscribe to this URL in Google Calendar, Outlook or Apple Calendar and the dates appear as they are published; each entry links back to the record and the source it was read from.
• How this is made and checkedWhat "verified against source" does and does not mean.

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup federal-rules-taking-effect agency="Federal Aviation Administration"

npx -y refsource lookup federal-rules-taking-effect agency="Federal Aviation Administration"

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this register up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource-rules": {
      "type": "http",
      "url": "https://referencesource.org/mcp/rules"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource-rules https://referencesource.org/mcp/rules --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "Federal rules taking effect: every US final rule in the Federal Register, by effective date", call the referencesource-rules MCP server at https://referencesource.org/mcp/rules (tool `list_rules_taking_effect`, dataset_slug `federal-rules-taking-effect`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

425 records. last verified against source 2026-09-18. due for re-check by 2026-09-29.

Licence. Federal Register documents are US government works in the public domain. The API is offered without a key and without registration; each record links back to the rule's own page on federalregister.gov.