Regulatory Change Management: Process, Software and the Data

Regulatory change management is how a business handles rule changes. You notice the change, decide if it applies, update your policies and controls, and keep proof that you did. A regulation is a rule written by a government agency under a law that lets it do so. Regulations are collected in the Code of Federal Regulations (the CFR). Software speeds up routing and record keeping. It cannot decide what a rule means for you, and it depends on the rule text underneath it.

Written and checked on 12 October 2026. This is general information, not legal advice; check the cited statute or opinion before relying on it.

Official text, as of 12 October 2026

• Citation: 29 CFR 541.600(a). It sets a minimum weekly salary for certain workers who are exempt from overtime.
• Quote: an exempt executive, administrative or professional employee "must be compensated on a salary basis at a rate of not less than $684 per week" (with lower figures for U.S. territories).
• Source: the eCFR page for 29 CFR 541.600. The eCFR listed Title 29 as up to date as of 8 October 2026.
• What changed in 2025 and 2026: until 14 May 2026 the code showed $844 and $1,128 per week. Those came from a 2024 rule that courts had already vacated (thrown out). A technical amendment on 15 May 2026 restored the earlier text. Our example below tells that story.

TL;DR

• Five steps: identify, assess, implement, keep evidence, report. Software helps most with routing and records.
• A person must make the assess step. Someone decides if a rule applies and by when.
• The code is not the only signal. A court can change the law while the code text stays wrong. In our example, the code text stayed at the vacated figures for 18 months.
• Ask any vendor where each source comes from and how often it is checked.

What regulatory change management is

A new law is easy to spot. A rule change is harder. Agencies publish rules every business day. Courts can undo them. Then the official code gets edited. Some people call the routine a framework, a workflow or a system. They all mean steps, owners and a record.

Bank supervisors have long expected someone to track rule changes. In April 2005 the Basel Committee on Banking Supervision said a bank's compliance function should advise senior management. That includes "keeping them informed on developments in the area." The paper is written for banks. The idea fits any company with rules to follow.

The five steps

A framework is the same five steps plus named roles, a review calendar and a one-page policy. Where change signals start is covered in our post on regulatory monitoring. For proposed versus final rules, see rulemaking explained.

One real change, followed through the five steps

The rule is a 2024 Department of Labor salary rule for overtime exemptions. The timeline below comes from the Department's own Federal Register notice (91 FR 27833).

• April 26, 2024: the Department published a final rule (89 FR 32842). It raised the standard weekly salary level to $844 on July 1, 2024, and to $1,128 on January 1, 2025.
• November 15, 2024: a federal court in the Eastern District of Texas vacated the rule, in Texas v. U.S. Dep't of Labor, 756 F. Supp. 3d 361.
• December 30, 2024: a court in the Northern District of Texas did the same in Flint Avenue, LLC v. U.S. Dep't of Labor.
• May 5 and 7, 2026: the Fifth Circuit dismissed the appeals in both cases.
• May 15, 2026: the Department published a technical amendment. It removed the 2024 text from 29 CFR part 541 and restored the earlier text, effective that day.

The eCFR keeps dated versions of every section. Look at section 541.600. On November 20, 2024, June 1, 2025 and May 14, 2026 it still read "Beginning on July 1, 2024, $844 per week" and "Beginning on January 1, 2025, $1,128 per week." On May 15, 2026 it read $684. The notice says what the courts' judgments meant. The operative rules were the version "in place on June 30, 2024." The Department says it "has been enforcing" that version. It calls its own action "a technical correction accounting for changes in the law that have already occurred." Read the full Federal Register notice.

From the first vacatur to the correction is exactly 18 months. The correction came 10 and 8 days after the two Fifth Circuit dismissals. The notice makes the amendment effective at once. It says a delay "could, for example, mislead employees and employers who consult the CFR." It also says the CFR should be corrected "as expeditiously as possible following the conclusion" of the litigation. Nothing here says the Department made a mistake. The point is narrower. The law and the code text can differ for a long stretch, and a team that watches only the code cannot see it.

Picture a made-up payroll manager whose staff earn near that cutoff. The five steps would look like this.

1. Identify. The signal was a court order. A team that watched only the code saw nothing happen in November 2024.
2. Assess. Does your overtime status for salaried staff depend on the salary level? Who decides?
3. Implement. Which salary cutoff does payroll use? Was it ever switched?
4. Evidence. A decision record citing the order and, later, the technical amendment.
5. Report. What leadership was told, and when.

This is not advice on what an employer must pay. As of 8 October 2026, the latest date the eCFR showed, section 541.600 reads $684. The Federal Register lists no document amending part 541 after the 15 May 2026 amendment. The notice says new rulemaking remains possible, so recheck any figure before you rely on it.

What the software does and does not do

This software is also sold as tools, solutions or platforms. It usually watches sources, routes alerts, helps with impact analysis, tracks tasks and reports. We read two vendors' own pages and describe only what they say.

MetricStream's product page describes five capabilities. They are monitoring, triaging, impact analysis, issue identification and tracking, and visibility through dashboards and reports. It says monitoring covers "more than 750 legislative and regulatory authorities worldwide." Its content comes from commercial providers and government agencies. PageCrawl's guide names two ways tools get changes. One licenses curated feeds. The other watches the primary sources. It rates tools on four things. They are source coverage, detection accuracy and speed, workflow, and audit trail.

Two limits apply to any product. The assess step is a human decision. And AI can sort and summarize fast, but it can misread a rule, so a person should read the key sentence first.

Where the rule text underneath comes from

Alerts are only as good as their sources. Federal notices come from the Federal Register. Our Federal Register API guide has more. The current federal code is the eCFR. States publish their own registers and codes, covered in the state law update guide. Some vendors license a feed instead. Our regulatory data sources guide compares the options. For push alerts, see law change webhooks.

The overtime case shows what a data layer can tell you. A code source tells you when the code text changed. A court order is a separate signal. You find it in the court record or an agency notice. Vaquill AI's API serves the CFR refreshed daily and records each change it observes to a section; how legal change detection works explains the method. For the wider picture, see US Law Data: The Complete Guide.

What goes wrong

• Watching only the code. A court order or a pending correction is missed, as in the example above.
• Treating the effective date as the only date. The 2024 rule had two staged thresholds, so one rule carried two dates.
• Skipping the assess step because an alert says "high impact." Someone must decide and write the date down.
• No owner on the evidence step, so the record is a screenshot of an alert.
• Alert overload. Send each notice only to the person who owns that duty.
• Trusting an AI summary without reading the operative sentence.

Questions to ask a vendor

1. Which US federal, state and agency sources do you read, and how often?
2. If a court vacates a rule, how does that reach my team, and how fast?
3. Do you show the source text and the date you read it for every alert?
4. Who writes the impact analysis, and who signs off?
5. Can I export the evidence trail for an auditor?
6. Which of the five steps do you not cover?

FAQ

What is regulatory change management? It is the routine of handling rule changes. You notice a change, decide if it applies, update your policies and controls, and keep proof. The five steps are identify, assess, implement, evidence and report.

What are the steps in the regulatory change management process? Identify, assess, implement, keep evidence and report. The table shows the output and owner for each.

Is a regulatory change management framework different from a process? A framework adds roles, a review calendar and a short policy to the same steps. The steps themselves stay the same.

What does regulatory change management software do? It routes alerts to owners, tracks tasks and keeps a record. People still decide whether a rule applies. Ask the vendor which sources it reads, and how often.

Can AI do regulatory change management? AI can sort alerts and summarize long notices. It can also get a rule wrong, so a person should confirm the key sentence and sign off.

How is this different from regulatory monitoring and regulatory mapping? Monitoring is the identify step, covered in our monitoring guide. Mapping turns a rule into a duty with an owner and a control, covered in our mapping guide. Change management is the loop that joins them.

For the US statutes, regulations and court rules these laws sit in, see the US primary law API.

Priyansh Khodiyar

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.