Clause deviation register for contract negotiation

Nothing here is legal advice. A draft is a starting point for a qualified person, not a substitute for one.

Use one register to turn a supplier draft into a negotiation pack that a reviewer can check quickly. This workflow is for commercial lawyers and contract managers who have an approved contract playbook and need clear positions before a negotiation.

Nothing here is legal advice. The register is a draft work product and starting point for a qualified person. The qualified person decides whether a clause is acceptable and what position to take.

1. Assemble the review set

Create a review folder for one transaction. Put only the current documents in it:

• The supplier draft, preferably in an editable format with clause numbering.
• The approved playbook for the contract type.
• Any approved fallback wording or precedent clauses.
• The deal brief: supplier, service, term, value, territory, data use, dependencies and target signature date.
• The previous marked-up draft, if this is a later negotiation round.

Read the deal brief before extracting clauses. A limitation of liability that is normal for a low-risk software subscription may be unsuitable where the supplier handles sensitive operational data. The playbook tells you the baseline. The deal brief tells you which parts need particular attention.

Create a spreadsheet named Supplier deviation register. Add these columns before you begin:

Column	What to record
Clause	Number and short heading from the supplier draft
Supplier position	Plain-English summary and the material wording
Playbook position	Approved rule, fallback, or escalation requirement
Deviation	What differs, without argument
Risk or impact	Operational or commercial consequence for this deal
Proposed position	Accept, reject, amend, or escalate, with wording where needed
Owner	Person who must decide or negotiate it
Status	Open, agreed, rejected, or escalated

2. Set the extraction instruction

Ask the model you are using to extract clauses before asking it to judge them. This separation reduces the chance that a missed clause is hidden behind a neat summary.

Paste the supplier draft and use this instruction. Replace the text in square brackets.

You are preparing an extraction table for a contract review. Do not provide legal advice and do not make acceptability decisions.

Contract type: [type]
Deal facts: [short deal brief]

Extract every clause that concerns the following playbook topics:
- scope and service levels
- fees, charges, invoicing and changes
- term, renewal and termination
- liability, exclusions and insurance
- indemnities
- confidentiality and publicity
- data handling and security
- intellectual property
- warranties and remedies
- subcontracting and assignment
- audit, records and compliance
- governing law and disputes

For each relevant clause, return a table with: clause number and heading; exact supplier wording; a plain-English summary; cross-references; and any missing topic from the list. Quote wording exactly where it affects the obligation, cap, condition, time period, exception or remedy. If the draft is silent, write "not found". Do not infer missing wording.

If the draft is long, work through it in numbered sections and preserve the original clause numbers. The amount you can submit and the features available are version-dependent. Check the xAI documentation overview before choosing a document-handling approach.

Save the output as Supplier clause extraction. Do not put it straight into the deviation register yet.

3. Compare against the playbook

Provide the extracted table and the relevant playbook entries. Ask for a comparison that retains uncertainty rather than smoothing it away.

Compare the supplier clause extraction with the approved playbook below.

For each extracted clause, produce one proposed deviation-register row with these fields:
1. Clause
2. Supplier position
3. Playbook position
4. Deviation
5. Risk or impact tied to the deal facts
6. Proposed position
7. Required decision owner
8. Questions or missing facts

Rules:
- Treat the playbook as the source for the approved position.
- State "no clear playbook match" where no entry applies.
- State "review required" where wording is ambiguous, a cross-reference is missing, or a deal fact is needed.
- Do not invent fallback positions or claim a clause is market standard.
- Keep supplier wording separate from your proposed position.
- Flag provisions that change a defined term, condition, carve-out, notice period, cap, remedy or priority rule.

Playbook entries:
[paste relevant entries]

Use only relevant playbook entries, but include the definitions or policy notes that alter their meaning. For example, a liability-cap rule may depend on whether data protection losses sit inside or outside the cap. A comparison without that note will often look complete while being wrong.

4. Convert the comparison into negotiation positions

Copy the proposed rows into your spreadsheet. Then sort by Status and Owner, not just by clause number. You are preparing a negotiation pack, so the register must show which points need instruction before the call.

For each row, make the proposed position specific:

• Use accept only where the supplier wording matches the approved position and the deal facts do not trigger an exception.
• Use amend where you have approved fallback wording. Put the proposed wording or the precise change in the row.
• Use reject where the playbook requires the supplier position to be removed or replaced.
• Use escalate where the playbook assigns a decision to a named stakeholder or the deal facts are incomplete.

Do not write make mutual or align to playbook as the proposed position. Those phrases leave the negotiator to rediscover the actual request. Write delete the publicity right in clause 14.2 or replace the 12-month cap with the approved cap in the fallback clause.

5. Check the register against the draft

Checking is where this workflow earns its place. Take the register and read the supplier draft again, concentrating on definitions, schedules, exceptions and cross-references. These are common places for a clause to change meaning without changing its heading.

Use this check list:

• Every material playbook topic has a row, including not found rows.
• Each clause number and quotation matches the draft exactly.
• A defined term used in a row has the same meaning as in the draft.
• The register records exceptions, thresholds and time periods, not only the headline obligation.
• Each proposed position is supported by a playbook entry or marked for escalation.
• The owner is a real person or role, not legal.
• Open questions have a route to answer them, such as the deal lead, security team or finance owner.

6. Produce the negotiation pack

Create two views from the same register:

1. A working register with all rows, quotations, questions and owners.
2. A negotiation summary containing only open and escalated points, ordered by commercial impact and urgency.

For the summary, include the clause number, supplier position, your proposed position, owner and decision deadline. Keep the full reasoning in the working register. This gives the negotiator a short agenda without losing the evidence needed by the reviewer.

When the result does not work

If the output is vague, do not ask for a better summary. Identify the failed field. Ask for exact quotations when wording is missing, ask for clause-by-clause output when topics were merged, or provide the missing playbook rule when positions were invented.

If the document has inconsistent numbering, first ask for a clause map showing headings, schedules and cross-references. If the playbook does not cover the issue, mark the row no clear playbook match and escalate it. Do not let the model fill a policy gap with a confident recommendation. Return to the draft, the approved playbook and the qualified reviewer until every material row has a source and an owner.