Image
Workflow
Back office

First-pass contract review against your playbook

Most of a first read is checking the same clauses against the same standard positions. An agent does that comparison against your written playbook and lists every departure with both texts side by side. Interpretation, negotiation and the decision stay with the lawyer.

The short answer

Short answer

An agent does a first pass on a contract by comparing each clause with the standard positions in your written playbook and listing every place the agreement departs from them, with the contract text and the playbook position side by side.

It interprets nothing and recommends no outcome. The lawyer judges each point and decides.

Today

Why does every first read cover the same ground?

The customer's paper arrives. The lawyer opens it and checks the same things as last time: the limitation of liability, the indemnity, the governing law, payment terms, termination rights, confidentiality. Most clauses are close to the company's standard position and some are not, and finding the ones that are not takes most of the first read. The judgment about what matters, and what to push back on, takes far less time than the search.

Who is this for?

An in-house lawyer, a general counsel or a legal operations lead who reviews similar agreements repeatedly and has written down the company's standard positions, even in a short document. It suits teams with a playbook, or the willingness to write one. Without written positions there is nothing to compare against, and the first job is writing them.

What changes when the comparison is done first?

Part of the reviewFirst read by handWith a playbook comparison first
Finding departuresRead every clause to find themListed, each with the clause and your position beside it
Clauses the playbook does not coverNoticed if the reader spots themListed separately as not covered
Missing clausesEasy to overlookFlagged where the playbook expects one
What mattersThe lawyer's judgmentStill the lawyer's judgment
What goes to the other sideThe lawyer's markupStill only the lawyer's markup

How it works, step by step

The playbook is the yardstick, and the agent measures against it. Every judgment about what a difference means stays with the lawyer.

01

Load the playbook the lawyer approved

The legal team gives the agent its playbook: the standard position for each clause type, any acceptable fallback language, and what must always go to a senior reviewer. A new version is used only once the playbook owner approves it.
02

Match each clause to a playbook topic

The agent reads the agreement and matches each clause to the playbook topic it addresses, showing the match. A clause it cannot match is listed as not covered.
03

Compare and list the departures

For each matched clause it sets the contract text beside your standard position and marks where they differ. Where the playbook expects a clause the agreement lacks, it says so.
04

Note the playbook's own fallback text

Where your playbook gives approved fallback language for a departure, the report shows that text, labelled as playbook wording. It writes no new language of its own.
05

Human gate: the lawyer judges every point

The deviation report and the agreement go to the reviewing lawyer. They decide which departures matter, what to accept, what to push back on and what to send to the other side. Nothing from the report reaches the counterparty unless the lawyer sends it. Professional judgment stays with the lawyer bound by the rules their state adopted. The Legal Information Institute notes that the Model Rules of Professional Conduct are not inherently binding but have come into effect only when states choose to adopt certain rules.
06

Record the lawyer's calls

When the lawyer marks a departure as accepted or rejected, the agent records the call with the agreement, so the next review of that counterparty starts with context.

Where it stops

Where does the agent stop?

Interpretation

It shows where text differs. What the difference means legally is the lawyer's call.

Advice. It never tells anyone whether to sign.

New language

It quotes your playbook's fallbacks and drafts no clauses.

The counterparty

It sends nothing outside legal.

Informal agreements. Side letters and emails can carry obligations too, so it flags them for the lawyer. Cornell's Wex entry adds that even informal agreements may be binding if the elements of contract formation are present.

Where this fits

Workflow / Automate a Workflow

Reviewing one agreement against one playbook is a single process, so it belongs in Tier 1, Automate a Workflow. A playbook with written positions is what the readiness checklist looks for. Running the comparison in shadow mode beside your lawyers' own first reads shows where the playbook is thin before anyone relies on it. Questionnaires that come with a deal are covered in security questionnaire automation, and commercial sign-off in deal desk approval routing. The use case library has the rest.

QuestionPlaybook comparisonLegal review
Who does itThe agentThe lawyer
What it answersWhere does this differ from our written positions?Does the difference matter, and what do we do?
What it relies onThe playbook as writtenLaw, context and the business relationship
What it producesA deviation report for the lawyerThe position the company takes
Tier 1 / Prove
How It Works

Questions, answered

No. It shows where the clause departs from your written position. Whether that departure is acceptable is the lawyer's decision.
AI Opportunity Audit · Contract review

Start every review from your playbook

Bring your playbook and the last agreement that took a full day to review.