LegalFree
Regulatory Change Impact Assessment Template
River separates the amendatory text from everything around it, so every obligation on the register is one somebody can actually be held to.
River reads the rulemaking document and returns obligations rather than a summary. Each one is a single thing somebody has to do, quoted or closely paraphrased from the text that creates it, with the amendatory instruction and the new paragraph it lands in. Anything that reads like a requirement but sits outside the codified text is kept and labelled as what it is, because the difference decides whether it can be enforced against you at all.
Then every obligation gets the date that actually binds it, which is frequently not the one on the front of the document. A rule carries a publication date, an effective date, and often a separate compliance date for a named class of things, and a major rule has a further statutory delay on top. The register holds all of them and computes the one each obligation runs to, so a phased rule produces four deadlines rather than one.
Each obligation then takes an owner inside the organisation, chosen from who the text applies to rather than from an org chart, with the evidence that would close it named on the row. The briefing for each affected team is built from their own rows. Obligations that reach the contract book land next to the register computing when each notice is actually due. Where a rule changes a term you can accept, the positions the firm has already settled are what have to move.
Three fields, three different answers
A final rule is two documents in one wrapper. The Federal Register's own drafting handbook says the preamble explains the basis and purpose of the regulatory text but contains no regulatory text. Only the amendatory instructions change the Code of Federal Regulations, and everything before them is explanation. So a sentence beginning the agency expects, however firmly it reads, creates nothing enforceable on its own, and an obligation extracted from it is an obligation somebody invented.
The dates caption is where the deadline actually lives, and it holds more than one. The handbook is explicit that some rules carry a compliance or applicability date in addition to an effective date, and that the compliance date is when the affected classes have to comply. A rule can be in force on one day and unenforceable against your labels for another four months. A register with one date column reports the wrong deadline for every phased obligation in it.
Two statutes move the effective date itself. Publication of a substantive rule shall be made not less than thirty days before its effective date. Three exceptions cut that short: a rule granting an exemption or relieving a restriction, interpretative rules and policy statements, and good cause published with the rule. A major rule takes effect on the latest of a set of dates, one of which is sixty days after Congress receives the report or the rule is published.
How it works
Hand over the rule
The published document, any guidance issued with it, and what your organisation currently does.
Text gets separated
The amendatory instructions on one side, preamble and guidance labelled on the other.
Obligations get dated
Every date the rule carries, and the one each obligation actually has to meet.
Owners get named
Assigned from who the text applies to, with the evidence that closes each row.
What you get
- One row per obligation, cited to the amendatory instruction and paragraph that creates it
- Preamble expectations and guidance kept, labelled, and never counted as binding requirements
- Publication, effective and compliance dates held separately, with the one that binds computed
- Applicability read from the text, so an owner is assigned on more than a guess
- Evidence that would close each obligation, named on the row before the work starts
- A briefing per affected team, built from their own rows rather than the whole rule
Common questions
Does it work on guidance and enforcement actions too?
Yes, and it labels them for what they are. A guidance document tells you how an agency reads a rule, and an enforcement action tells you what it does about a set of facts. Both belong on the register as positions to take rather than as deadlines, and the register records what complying would cost against what declining risks.
What if the rule is amending something we already comply with?
Then the useful output is the delta, and that is what it builds. Each new or changed paragraph is set against what the current text required, so the register shows the requirements that moved and the ones that only got renumbered. Renumbering matters, because every internal document citing the old paragraph is now wrong.
How does it assign an owner?
From the class the codified text applies to, matched against what your organisation actually does. A rule reaching any person who packages for retail sale lands on the sites that package for retail sale, not on everyone. Where nothing in the organisation currently performs the function, the row comes back unassigned rather than parked with legal.
What about state or foreign rules?
The structure holds because the problem is the same everywhere: an instrument that mixes explanation with the operative text, several dates, and a defined class of addressees. The captions and the statutory delays differ by jurisdiction. What does not differ is that only the operative text creates something you can be held to.
Does this replace outside counsel on the hard questions?
No, and it makes the hard questions cheaper to ask. Most of a rule is mechanical extraction and most of a memo is spent on it. Sorting the mechanical part first means counsel receives four real questions with the text attached, and the register records the answers against the rows they settle.
How does it fit with the obligations we already track?
Rows merge into an existing register rather than starting a second one, keyed to the paragraph rather than to a title, so a later amendment updates the row it changed. Contractual obligations sit in the same shape, which is why the deadlines computed from each clause and these read together.
Does this feed into an ongoing compliance program?
It produces the obligation, not the program. Once a new obligation is dated and owned here, mapping it to the control that actually covers it, and testing that control on a risk-tiered calendar is where an ongoing program takes over. The two stay in sync as rules keep changing.
Regulatory Change Impact Assessment Template
Fill in the form and your workspace opens with the work already underway.