Standard terms read the draft; a lawyer reads deviations

The question this file answersWhen a client sends their paper instead of ours, who reads it clause by clause — and against which version of our terms?

Fits: legal, consulting and accounting firms reviewing 10–100+ contracts or engagement letters a month against written standard terms, with drafts arriving as Word or PDF by email and filed in a DMS such as iManage, NetDocuments or SharePoint.

Not for: firms with a handful of bespoke contracts a year, or teams whose standard terms exist only in a senior partner's memory — that has to be written down first.

Typical day

What the desk looks like today

Typical, from the professional-services playbook — not a client's day. Every new engagement brings a contract or engagement letter to review — 10–100+ a month at a mid-size firm. A lawyer reads each draft clause by clause, holds it against the firm's standard terms — liability caps, IP, payment, termination — marks deviations by hand, negotiates them, tracks versions in email, and files the signed copy in iManage or SharePoint. Most drafts are near-standard, yet each gets the full read. It bites when a large client insists on its own paper, and at quarter-end when several engagements start at once.

What changes

What Monday looks like after

The morning a client's draft arrives. The reviewer opens the DMS and finds the draft already marked up: standard clauses greyed as matching, deviations coloured and graded, the fallback wording beside each, and a summary page short enough to send to the partner. Reading starts at the clause that matters — the uncapped liability, the unusual IP grant — not at page one. Versions and approval status sit on the matter, not in a mail thread. The engagement lead can see how many drafts came in, how many were near-standard, and where negotiation time went. The lawyer still decides every deviation; the first pass is no longer a full read. Deloitte Legal (2023) measured standard agreements only.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

~40–60%

less review time on standard agreements — Deloitte Legal Tech (2023)

Before: someone reads every clause and paints deviations by hand. After: Deloitte (2023) reports 40–60% less review time on standard agreements — the risk call stays human.

Where this number comes from

Deloitte 'Legal Technology' (2023) reports 40–60% less review time on standard agreements with AI-assisted contract review; Thomson Reuters 'State of Legal Technology' (2023): 70% of firms plan AI-assisted review within two years. Industry figures, not ours; playbook range 35–55%. The risk call stays human.

What we install

What we put in front of the systems you already run

Drafts keep arriving by email and filed in iManage, NetDocuments, SharePoint or the DMS you run; we change nothing there. We add a comparison step before the reviewer:

each draft is read from the mailbox and its key clauses located — liability, indemnity, IP, payment, termination
every clause is compared with your standard wording and its agreed fallbacks
deviations are graded for risk, with alternative wording ready to paste where you have one
the marked-up draft and a one-page summary are filed back against the matter, versions tracked
unplaced clauses and any grade above your threshold top the reviewer's list.

Nothing goes to the counterparty without a person. Starting scope: your engagement letter and two client templates.

What stays human — and what this will not do

Risk assessment on a non-standard term. Negotiation strategy. Final approval. The relationship with the client on the other side of the redline.

What can go wrong — and what we do about it

Standard terms that exist only in practice cannot be compared against — the audit writes them down, and every unresolved fallback turns into a deviation for a person. Scanned or image-only PDFs read worse than Word; those drafts get a full human read. An unusual but harmless clause can be graded as a deviation, and a harmful one in standard-looking words can slip — so the reviewer's list starts with the highest grades, and sign-off is never automated. The 35–55% range is for standard agreements; bespoke deals and regulated sectors fall outside it.

How long it takes, and what we need from you

Audit, about two weeks (€1.5–3K): we count contracts by type over the last quarter, sit with a reviewer through several live drafts, and turn your standard terms and fallbacks into a written reference. Pilot, 4–6 weeks (€10–20K); the professional-services playbook calls this medium-to-high complexity because grading rules take iteration: engagement letters and one client template, every mark-up read in full at first. Production: more templates, version tracking, negotiation history. From you: standard terms, examples of accepted deviations, DMS access.

The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →

This is about you if…

Do client contracts arrive as Word or PDF drafts that someone reads in full?
Do one or two senior people mark up every deviation by hand?
Are your standard terms and fallbacks written down, or held in someone's head?

What does this mean in euros?

That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.

Get your free savings estimate 60 seconds · no sales call Or write first → Map an ops process like this one — free, 60 seconds →

Not a named Aperanda client. Process file · Ops.

Deep-dive process file. Volumes, weeks and sources come from the industry playbook; nothing here is a named client.

All process files