Regulated Customer Contract Checker
For the legal operations lead whose customer agreements live in a spreadsheet

Every regulated customer contract on your list, read against its customer's regimes.

Paste the list of your regulated customer contracts, one line per agreement you have signed: the list, not the documents. 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 stated in our own words from the published standards, 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.

Regulated Customer Contract Checker: the questions buyers ask

What is the Regulated Customer Contract Checker?

It takes the list of your regulated customer contracts and reads each agreement against the regimes your customer's sector and country pull onto you. It is for the legal operations lead whose customer agreements live in a spreadsheet.

Do I need to upload the contracts themselves?

No. You paste the list, not the documents, one line per agreement you have signed. The register reads your list and not your agreements, and every finding is a question to answer from the agreement itself.

What do I paste in?

`Customer` alone works, or `Customer, Sector, Country`, or the full row with agreement, personal data, DPA or BAA, breach notice, audit right, liability cap, start, term, renewal and notice days. Tabs, commas, pipes or a CSV export of your contract database all work, and a header row is optional.

How many agreements can I run for free?

Eight agreements are free and no account is needed. The dictionaries and the clause text load with the page, and every reading compares the words on your own rows against them in your browser.

How does it know which regimes apply to a customer?

The customer's sector and country decide which regimes attach to a row, each with its reason in a sentence. Every regime is ticked by default and you untick the ones that are not yours, such as a certification you do not hold; a bank in Ireland is a financial entity under DORA, and a hospital in the United States is a covered entity under HIPAA.

Which regimes can it read against?

The GDPR, the UK GDPR, DORA, NIS2, the HIPAA Security Rule, CCPA/CPRA, APRA CPS 230 and CPS 234, ISO/IEC 27001 and ISO/IEC 27701. We read the published text of these clause by clause.

What does it tell me about each agreement?

The regimes the customer's sector and country pull on, 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. It also flags the agreements missing a DPA, BAA or security schedule.

Can it compare breach-notice clocks across customers?

Yes. The breach-notice clocks across every customer are listed shortest first, beside each customer's own clock to its regulator. The specimen shows clocks from 4h to 168h and marks the agreements where the clocks disagree.

What happens with an agreement it does not recognise?

A line that matches nothing against the published dictionary of 40 agreement types in six families and 25 customer sectors is marked unrecognised and never guessed. Its expected terms are left not placed.

Which renewals will it flag?

It lists the renewals and notice dates inside 90 days. You set where you are and the date with a first line such as `home: UK | as at: 2026-09-23`.

Is this legal advice?

No. The register reads your list, not your agreements, and is not legal advice; each finding is a question to answer from the agreement itself. The questions to take to counsel are grouped by finding, each with the clause behind it.

What can I take to the next negotiation?

The breach-notice clocks shortest first, every audit right you have granted, the renewals and notice dates inside 90 days, and the counsel questions grouped by finding. That is the one page for the negotiator who asks which breach clock you have already promised, and to whom.

What this does, and what a spreadsheet, a lawyer or an AI assistant does better

A spreadsheet is better for keeping the contract list as the legal operations team's own record, with the clauses, dates and notes a contract database export does not standardise, and it costs nothing. A lawyer is better on what your agreements actually say and what they bind you to, which this tool never reads, and this register is not legal advice. A general AI assistant is better for drafting the DPA, BAA or security schedule a row is missing, or explaining a regime in prose. What this does that they do not is pull the regimes a customer's sector and country place on you, show which expected terms each row does or does not record, and list the breach-notice clocks shortest first and the renewals inside 90 days; it reads the list and not the agreements, and each finding is a question to answer from the agreement itself.

Primary source: EU GDPR