
Short answer: regulatory monitoring is the routine of watching official sources for new or changed rules. You read each change, decide what it means for your business and keep a record that you acted. Every change starts at a publisher. Federal rules start in the Federal Register and state rules in a state register. Agencies post guidance on their own pages, and bills sit on a legislature's site. A tool can help you spot changes sooner. It cannot decide what a rule means for your company.
TL;DR
- Regulatory monitoring (some vendors call it regulatory tracking) is four jobs: spot a change, read it, decide what it means for you, and prove you acted.
- Changes appear first in official publications. Know which ones cover your business and when each is published.
- A proposed rule is a draft. A final rule is adopted and has a start date. Treat them as different alerts.
- A tool cannot be fresher than its source. A weekly register is weekly, whatever the software says.
- Before you buy anything, ask where each alert comes from and whether you can open the original.
What regulatory monitoring is
A regulation is a rule written by a government agency under power a law gives it. Agencies write a lot of them, and they change them often. Monitoring is how a business learns about a change before it is caught out by one.
Think of a small lender, a clinic or an online store. Each answers to a handful of agencies. Someone has to notice when one of them publishes something new. That is the whole job, and it comes in four parts:
- Spot. Find out that something changed.
- Read. Open the original text and read what it says.
- Decide. Work out whether it applies to you, what you must do and by when.
- Prove. Keep a dated record of what you reviewed and what you did.
Software mostly helps with the first. The last three are decisions, and someone in your company owns them.
Where change signals really start
Every alert you receive began as a page on a government site. If you know the page, you can check any alert yourself.
| Kind of change | Where it starts | What it tells you |
|---|---|---|
| Federal proposed and final rules | The Federal Register, the daily journal of federal agencies | The proposal, the comment deadline, the final text, the start date |
| State proposed and final rules | A state register, such as the Texas Register (weekly) or the California Regulatory Notice Register (every Friday) | Rulemaking notices, in each state's own format |
| Agency guidance | The agency's own pages, such as the Business Center of the Federal Trade Commission (FTC) | Plain-language advice, often with no fixed schedule |
| Proposed laws | Congress.gov, the Library of Congress site for federal legislation, or your legislature's site | Bill status, text and sponsors |
| Final text | The official code, such as the eCFR, the Electronic Code of Federal Regulations | What the rule says today, with a note on how it was amended |
For every item, note five things: the source, its status (proposed or final), the effective date, the owner and the proof of action.
Three details are worth knowing. First, GovInfo, the federal publisher, says the Federal Register is published Monday through Friday, except federal holidays. Rules are also posted for public inspection, an early preview on the Federal Register site, at least one business day before they are printed. Second, Texas says its register carries proposed, adopted, withdrawn and emergency rules. Adopted rules are then folded into the Texas Administrative Code. Third, the eCFR describes itself as an informational web version of the Code of Federal Regulations, updated daily. We read these pages on October 5, 2026, and publishers can change their schedules, so check them again. Our guide to citing a statute or regulation explains how to read the citations in these sources.
Proposed rules and final rules need different alerts
A proposed rule is a draft the agency publishes to collect comments. It may change, shrink or disappear. A final rule has been adopted and carries an effective date, the day it starts to bind you. For bills, the matching word is "enacted": a bill that has been signed into law.
These need different handling. A proposal tells you to prepare and perhaps to comment. A final rule tells you to act. If your feed lumps them together, you will either panic over drafts or sleep through deadlines. The same split applies to bills and statutes, as we explain in bills versus laws.
The rules about rules, and the signals around them
Most of what makes monitoring possible comes from one old law. Congress passed the Administrative Procedure Act in 1946, and the source note under section 553 of Title 5 traces it to a June 11, 1946 act. That section says general notice of a proposed rule "shall be published in the Federal Register," and that a substantive rule has to be published "not less than 30 days before its effective date." Both come with exceptions, and the exceptions are what trip up a monitoring team.
An agency can skip the proposal when it finds good cause that "notice and public procedure thereon are impracticable, unnecessary, or contrary to the public interest." Unless another law requires notice, the requirement also does not apply to interpretative rules (an agency's reading of a rule it already has) or general statements of policy. So a feed built only on proposals will miss some changes, and the 30-day floor has exceptions too. In the fees example above, the final rule gave four months. Do not count on that.
Congress added another step in 1996. Under the Congressional Review Act (Public Law 104-121, March 29, 1996), an agency has to send each final rule to both houses of Congress and to the Comptroller General, and the chapter lets Congress vote to reject a rule by joint resolution (5 U.S.C. 801). A final rule is not always the last word.
There is also a signal that arrives before any proposal. The government's Unified Agenda describes itself as reporting "the actions administrative agencies plan to issue in the near and long term." The site says agencies have been required by executive orders to publish such agendas since 1978, and it shows editions going back to fall 1995. Entries are plans, so use them to decide what to watch, and rely on the Federal Register notice for dates and text.
One real rule, from proposal to the CFR
Here is a federal rule followed from first notice to the code, with what a monitoring team would have done at each step. The rule is the FTC's Rule on Unfair or Deceptive Fees, now Part 464 of Title 16 of the Code of Federal Regulations (the CFR, which collects agency rules by subject).
November 8, 2022: an early notice. The Federal Trade Commission published an advance notice in the Federal Register asking whether it should write a rule on fees. The citation is 87 FR 67413, meaning volume 87 of the Federal Register, page 67413. Comments closed January 9, 2023. Team action: log it as a watch item. Decide if fees you charge could be in scope.
November 9, 2023: the proposal. The FTC published a proposed rule (88 FR 77420) aimed at hidden fees on goods and services in general, with comments due January 8, 2024. A January 2, 2024 notice (89 FR 38) moved that deadline to February 7, 2024. Team action: read the draft, decide whether to file a comment, and tell the people who set prices.
January 8 to 10, 2025: the final rule. The final rule went on public inspection on January 8 and was published on January 10 (90 FR 2066), effective May 12, 2025. It was much narrower than the proposal. Its summary says it covers fees for live-event tickets and short-term lodging. Team action: this is the moment to decide. A retailer of shoes could stop here. A ticket seller had four months to change its pages.
May 12, 2025: the code. On October 5, 2026 we asked the eCFR to show Part 464 as it stood on dates before May 12, 2025. It returned no content. In this case the text entered the code on the day the rule started. A team that watched only the code would have learned of this rule four months after it was published. A code-only monitor can miss most of the time you had to prepare. The operative sentence, in 16 CFR 464.2(a), reads:
"It is an unfair and deceptive practice and a violation of this part for any business to offer, display, or advertise any price of a covered good or service without clearly and conspicuously disclosing the total price."
Team action: record the citation, who owns it and the proof that you comply. That is the register we describe in regulatory mapping.
The story did not stop there. The same agency has since published two more fee proposals in the Federal Register: rental housing fees on March 13, 2026 (91 FR 12325) and online food delivery fees on April 16, 2026 (91 FR 20381). Monitoring never ends. It repeats.
What a tool can and cannot do
A tool can do the spotting at scale. It can check dozens of pages a day, sort by topic and notify the right person. It can keep a copy of what a page said last week.
It cannot tell you whether a rule applies to your products. It cannot judge what "clearly and conspicuously" means for your checkout page. It also cannot publish faster than the publisher. Nobody can send you a state rule before the state prints it.
How fresh can a signal be?
Freshness has a ceiling set by the source. A weekly register gives weekly news. An annual code edition gives annual text. The Federal Register can show you a rule two days early through public inspection, and in this example the eCFR showed it only from the effective date. When you compare tools, ask for the date each source was last checked. Our note on data freshness shows what that looks like in practice.
What to check before choosing a tool
Reuse the habits from our ten questions for a legal data vendor. For monitoring, five matter most:
- Can I open the original? Each alert should link to the publisher's page.
- Does it separate proposed from final? And does it show the effective date?
- Which sources does it cover? Match the list against your states and agencies.
- When was each source last checked? A date per source beats "updated regularly".
- Does it keep a record? You need to show what you were told and when.
How Vaquill AI approaches change tracking
Vaquill AI's API (a way for software to request data from another system) lets a team follow a source, such as federal regulations or one state's statutes. When the source is re-read and sections have been added, changed or removed, you get an email or an automatic message to your own system. Each changed section has a record showing its text before and after, where available. A source list shows how often each source is re-read, when it was last read and whether it is still being read. The record notes when we saw the change. The publisher's own effective date is a separate field. More on how this works is in our post on how legal change detection works.
What goes wrong
- No one owns it. An alert lands in a shared inbox and nobody reads it.
- Drafts are treated as law. A team rewrites its pages for a proposal that never passes.
- Final rules are missed. The proposal was watched but the final version, which was narrower or broader, was not.
- Only the code is watched. The code can trail the Federal Register, as it did for the fees rule.
- There is no proof. The work was done but nothing recorded it, so an auditor sees nothing.
This is general information, not legal advice. For a risky decision, ask a lawyer who knows your industry.
Your alert feed covers only proposed rules. One day an agency announces a new interpretation of a rule it already has, with no proposal beforehand. Should that surprise you?
FAQ
What is regulatory monitoring? It is the routine of watching official sources for new or changed rules and acting on them. It has four jobs: spot, read, decide and prove. Many vendors also call it regulatory tracking or regulatory change management.
How do I track regulatory changes for free? Subscribe to the Federal Register and your state register, and follow the agencies that regulate you. Many publishers offer email alerts. Set a weekly reminder to read what arrived and note who is responsible for each item. This works until you need many states, many agencies or an audit record.
What is the difference between regulatory monitoring and regulatory updates? Regulatory updates are the news items: this agency published that rule. Monitoring is the process that finds them, routes them to a person, and records the result. Updates are an input to monitoring.
Is regulatory tracking software worth it? It saves time when you must watch many sources or many states. It does not replace someone who decides what a rule means for you. Before buying, ask where each alert comes from and how recently each source was checked.
How quickly can I learn of a new federal rule? Rules usually appear on public inspection at least one business day before printing in the Federal Register. The fees rule in this guide appeared two days early. In the fees example, the eCFR showed the text only from the effective date.
How do I know a proposed rule became final? Look for a final rule in the Federal Register with the same title, and compare its scope with the proposal. The fees rule was narrower than the draft. A proposal that never turns final may simply stop appearing.
Where should the record of what we did live? In a register that links each rule's citation to a person who owns it, the step you take to comply and the proof that you took it. Our guide to regulatory mapping gives a template.
If you want US statutes and regulations, with a record of how they changed, as data your software can pull, start at the legal API. This guide belongs to the series in US Law Data: The Complete Guide.
New legal AI guides, weekly.
Further Reading
Regulatory Mapping: Connect Rules to Your Obligations
Read postHow to Monitor State Law Changes: The State Law Update Guide
Read postCompliance API: Two Meanings, and Where Regulatory Data Comes From
Read postAI Compliance Check: CCPA, GDPR, and SOX for In-House Teams (2026)
Read postUS Law Data: The Complete Guide for Business and Technical Readers
Read postHow Does a Bill Become a Law? From Idea to the US Code
Read post
Co-Founder & CTO
Priyansh leads engineering and AI at Vaquill AI: the pipelines that pull statutes, regulations and court rules from every US jurisdiction's official publisher, and the REST API, MCP server and open dataset that serve them.