Clause Register
For the legal operations lead whose customer agreements live in a spreadsheet

Every signed agreement, read against your customers' regimes.

Paste the list of customer agreements you have signed. Get, per agreement, the regimes your customer's sector pulls onto you, the clauses those regimes expect the agreement to carry, quoted and cited, the agreements missing a DPA, BAA or security schedule, the breach-notice clocks that disagree across your customers, every audit right you have granted, and the renewals and notice windows inside 90 days.

Paste your own listEight agreements free, no account. The dictionaries and the clause text load with the page; every reading compares the words on your own rows against them, in your browser, and nothing leaves it until you choose to save.
A contracts manager at her desk reading two pages, a laptop and a clipboard beside her
Next time a customer's negotiator asks which breach clock you have already promised, and to whom, the answer is one page, shortest first. It comes from the spreadsheet you already keep, read against the clause text of the regimes your customers answer to, which a contract database export does not carry.
Specimen: an invented software supplier, 30 agreements7 of 30 rows
Item and customerAgreementExpected, and what the row showsClock
1.01Bank, Irelandclocks disagreeOutsourcingprocessor termsDORA termssecurity schedule4h
1.04Insurer, Swedenno DORA terms shownSaaS subscriptionprocessor termsDORA termsaudit right72h
1.09Insurer, UKno DPA shownOutsourcingprocessor termsaudit rightbreach clockwithout undue delay
1.11Hospital, USno BAA shownSaaS subscriptionBAAaudit rightbreach clock72h
1.16Retailer, CaliforniaSaaS subscriptionprocessor termsaudit rightbreach clock72h
1.20Super fund, Australianotice missedOutsourcingCPS 230 termssecurity scheduleaudit rightwithout undue delay
1.30Members guild, IrelandunrecognisedComfort letternot placednot stated
30 agreements29 classified7 distinct clocks, 4h to 168h11 audit rights
What each regime expects of an agreement of that kind with that customer, and whether the row shows it: ticked where it does, open where it does not say. The full register adds the regimes and the reason each is pulled on, the clauses quoted, eleven findings and the counsel questions.
One agreement per line: Customer, or Customer, Sector, Country, or the full row Customer | Sector | Country | Agreement | Personal data | DPA or BAA | Breach notice | Audit right | Liability cap | Start | Term | Renewal | Notice days | Owner. Tabs, commas, pipes or a CSV export of your contract database all work; a header row is optional. A first line home: UK | as at: 2026-09-23 sets where you are and pins the date.
Every regime is ticked; the customer's sector and country decide which attach to a row. Untick the ones that are not yours, such as a certification you do not hold.
01

Paste the agreements you already have

The contract database export, the sales-ops sheet or a line per customer from memory: one agreement per line, a customer on as many lines as it has agreements. Every line is matched against a published dictionary of 40 agreement types in six families and 25 customer sectors, in 70 countries; a line that matches nothing is marked unrecognised and never guessed.

02

Read what each customer pulls onto you

Per agreement: the regimes the customer's sector and country pull on, each with its reason in a sentence (a bank in Ireland is a financial entity under DORA, a hospital in the United States is a covered entity under HIPAA), the terms those regimes expect an agreement of that kind to carry, and a box for each: ticked where the row shows it, open where it does not say.

03

Take the clocks and the questions to the next negotiation

The breach-notice clocks across every customer, shortest first, beside each customer's own clock to its regulator; every audit right you have granted; the renewals and notice dates inside 90 days; and the questions to take to counsel, grouped by finding, each with the clause behind it.

Why a register and not a contract review

A review firm prices per agreement and arrives next quarter. The legal operations lead is asked in this week's negotiation which breach-notice clock the company has already promised to whom, and which customers hold an audit right, and the answer sits in a spreadsheet that does not say. Before anyone reads an agreement again, somebody has to say what each customer's regimes expect and what the row records. That is the register this builds, in your browser, from the list you already hold.

The dictionaries and the obligations table are ours and published in full: every agreement type, every customer sector, every country and what each regime expects of an agreement by its kind and its customer. The clause text behind every expected term is quoted from the standards themselves, published at compliance.theartofservice.com, and ships with this page as a static file. The register reads your list, not your agreements, and is not legal advice: each finding is a question to answer from the agreement itself.