Consultant Restriction and Conflict Register
Four documents and three sheets that date each client restriction from the event it actually runs from, then clear one opportunity against the rows still live.
Free download · No account needed
Restriction Register · Marchetti Advisory · 34 restrictions, 11 executed contracts · cleared 05 Mar
The same five rows, before and after the clock was worked out
| Ref | Client and type | Read off the signature page | Trigger event and proving record | Actual status |
|---|---|---|---|---|
| R-05 | Sterling Yards non-compete, 24m | Signed 03 Feb 2023, so dead | Last day of service 12 Jun 2024 final invoice | Expired 266 days ago |
| R-22 | Ellery Foods exclusivity, 12m | Treated as live | SOW end 31 Jan 2026 executed SOW-4 | Expired 33 days ago |
| R-14 | Northbank Group customer non-solicit, 18m | Forgotten | Last day of service 09 Mar 2026 final timesheet | Live, 188 days left |
| R-19 | Dunmore Freight non-compete, 12m | Live to 04 Aug | Governed by Minnesota law | Void where it would bite |
| R-31 | Vance Rail non-compete, 12m | Live to next August | Runs from termination of an MSA that auto-renews and never terminated | Live, no end date |
Two of those five were being obeyed after they died. A freight network diagnostic worth $84,000 was declined against R-05 when it had been dead 98 days, and a cold-chain review worth $61,000 against R-22 when it had been dead 24 days.
Search this and everything on page one is built for the other side of the clause. A restrictive-covenant compliance manager for a firm tracking 2,000 employees. An enforceability checker that scores one agreement against a state law database. An extraction API that turns a non-compete into structured fields for a hiring clearance workflow. All competent, all written for whoever holds the covenant, and none of them written for the person carrying thirty of them across eleven contracts they signed themselves.
The extraction tools get closest and stop one field short. They pull the trigger event out as a string, termination of employment for any reason. Then they date it from the effective date, which is the one date it does not run from. Here the trigger gets a real date and a record that proves it: a final invoice, a last timesheet, a termination notice. That single join is what moved a Sterling Yards non-compete from live to dead 266 days ago, and what left a Vance Rail non-compete with no end date at all.
Marchetti Advisory, three people in logistics consulting, 11 executed contracts, 34 restrictions. Twelve had expired, three are void where they would bite, 19 are live. Two priced opportunities worth $145,000 had already been declined against dead rows. The clearance that mattered took 25 minutes. Pair it with the practice dashboard that prices the resulting gap, or with the SOW pack that drafts the next set of restrictions.
What's in the pack
Restriction Register
One row per restriction with its trigger event, the record proving that date, the resolved population and a three-valued status.
Opportunity Clearance Record
Every live row read against one opportunity, including the ones that turned out not to apply, each with its reason recorded before a proposal exists.
Conflict Check Log
One row per opportunity ever checked, with what the answer rested on, so a decline made from memory is visible as one.
Restriction Summary
Plain language, no defined terms, opening on what you can do and carrying a section for what you wrongly thought you could not.
Clearance Note
The per-opportunity record: what was checked in counts, how each live row reaches the work, and the condition in the form the contract will carry. A licence-back clearing the method is a separate question from whether the deliverable itself is safe to reuse, which the knowledge library pack tests directly. Whether enough associate capacity exists to staff the cleared work at all is a third, which the associate network pack tracks.
Waiver Request Format
The narrow ask that gets answered in a week. One named prospect, one engagement, a stated period, and a response-by date.
How a Restriction Clock Works
The four trigger shapes, what record proves each one, and the auto-renewing agreement that leaves a twelve-month clause running forever.
A restriction has a date or it has a question
The standing rule. An undated row is never cleared against, and a row turning on law is routed rather than guessed at.
How to use it
- 1
Open in River, or take it blank
Open the pack in River and send every executed agreement, or download the Word documents and CSV sheets and build the register yourself.
- 2
Split every contract into rows
One row per restriction rather than one per client. Most practitioners guess eight or ten across their portfolio and find three times that.
- 3
Date each row from its trigger
Find the final invoice, the last timesheet, the termination notice. A row with no proving record stays undated rather than estimated.
- 4
Clear the opportunity, record the misses
Re-resolve the affiliate sets, compare on four axes, and write a reason against every live row that turned out not to apply.
Frequently asked questions
Is this template free?
Yes. The zip is Word documents and CSV sheets, no account and no card. Edit with AI is the optional half: the agent reads the executed contracts, dates each restriction from its trigger and resolves who it covers. The rest of the packs sit in the template library.
What format are the downloaded files?
Four Word documents and three CSV sheets in one zip. The register carries the columns that do the work: trigger event, the record proving its date, live-until, resolved population, status, governing law and the counsel question. Excel, Numbers and Google Sheets all open them.
What does Edit with AI actually do?
It reads every MSA, SOW, NDA and amendment, then writes one row per restriction with the scope in the contract's own words. Each row is dated from its trigger against the record you supplied. Then it resolves the affiliate and customer sets and marks the rows whose status turns on law.
Are non-competes not banned now?
No. The FTC rule was held unlawful and set aside, the Commission acceded to the vacatur in September 2025, and the February 2026 final rule removed the rule from the Code of Federal Regulations. What governs is the contract, the state and the forum.
Why is the status three-valued rather than live or expired?
Because a restriction can be textually live and legally void, and a two-valued column records that as live. California voids any contract restraining a lawful profession and reads that broadly enough to catch a narrowly tailored noncompete. A live-or-expired register would have declined that work.
Can one clause block be void and live at the same time?
Routinely, and it is the finding people miss. Minnesota voids covenants not to compete, counts an independent contractor as an employee, and then says a covenant not to compete does not include a nonsolicitation agreement. So the non-compete dies and the customer non-solicit beside it stands.
Does this replace a lawyer?
No, and it is built so it does not have to. Rows turning on law are routed rather than decided, each as one answerable question about one clause. In the worked example that is seven questions, which is a cheaper purchase than an hour of somebody reading eleven contracts after an engagement has gone wrong.
Answer it from a row, not from memory
Take the Word documents and CSV sheets blank, or send River your executed contracts and get every restriction dated, populated and statused back.
Edit with AI