[Review and redline]
Their paper, marked
to your playbook.
Upload the other side's contract and say whose side you act for. Clausel returns a tracked-changes redline. Each change names your playbook position and the contract's own words. Nothing lands in the document until you accept it.
Renews for twelve months unless the Customer gives 180 days' notice either party gives 60 days' notice before the renewal date.
The Customer pays each invoice within thirty days without deduction or set-off and may set off sums the Supplier owes it.
The Customer's liability shall be unlimited shall not exceed the fees paid in the twelve months before the claim, save for fraud.
This Agreement is governed by the laws of the State of New York, and the parties submit to the courts of New York.
Clause 9.1, Term and renewal.Moderate risk·Rests on Playbook §2.3, Renewal and notice
Clause 11.3, Payment.Moderate risk·Rests on Playbook §3.2, Set-off
Clause 14.2, Limitation of liability.High risk·Rests on Playbook §4.1, Liability caps
Clause 18, inserted.Missing term·Rests on Playbook §9.1, Governing law and forum
How a review runs
Code finds. The model explains. Code checks the model.
Seven stages, and each one leaves something you can read. Your playbook is checked rule by rule before the main run, so no rule is skipped, and every fix is read again once it is written.
§4.1, Liability caps: breach. Clause 14.2 leaves the Customer's liability unlimited. The preferred position is a cap at twelve months' fees. The fix edits 14.2, and nothing else.
Read again once the fix is written. The amended clause meets §4.1, and the elements it must carry are all there.
Scout the document. On a long contract, a first pass reads the numbered clauses section by section, several at a time, and hands its candidates to the main run.
Run the thirteen detectors. Code looks for the classic one-sided terms: a renewal trap, no set-off, unlimited liability, a one-way termination right, the reach of a restraint. Each candidate quotes one sentence word for word. Whether it is a problem for your side is the model's call, and then yours.
One verdict for every rule. Before the main run, each rule in your playbook gets a verdict: breach, meets, absent or not applicable. An absent term comes with the clause to insert. A rule is never left out.
Prove each fix. The amended clause is read again and graded against the rule's own elements. A fix that falls short goes back with the missing elements named. What is still missing is said out loud, never passed off as fixed.
Place it in the document. Each change lands as a tracked change, only the words that differ. A change that cannot find its words is not placed, is not counted, and the review says so.
Check consistency. A deterministic engine, with no model in it, checks references, numbers, definitions, dates, values, wording and blanks across the whole document.
Check the quotes. Every card's quoted words are looked for in the document. A quote that cannot be found is reported as not found, never shown as the contract's own words.
Consistency
The mistakes a tired reader misses.
The consistency engine runs over the whole document without a model, so the same document gives the same answer every time. Each finding is located in the document. These are the kinds it returns.
Clause 16.2 refers to clause 22.4. The agreement ends at clause 21.
"Thirty (60) days" in clause 7.3. The words and the figure disagree.
"Services" is defined in 1.1 and again in Schedule B, with a narrower meaning.
Clause 1.1 starts the term on 1 August. The header table says 1 July.
The notice period is 30 days in clause 9.2 and 60 days in Schedule C.
Clause 5.1 still holds a fill-in. The finding names it by the words in front of it: the deposit.
Clause 12 gives the Customer the IP in deliverables. Schedule D grants the Supplier ownership of "all work product".
This playbook declares services agreements. The document is a residential lease. Playbook findings are withheld, and the review says so.
Redline or report
A redline or a report. You choose which.
Some matters need the document marked up. Others need a note to the partner. Clausel keeps the two apart, so a report never rewrites the contract.
The Customer's liability shall be unlimited shall not exceed the fees paid in the twelve months before the claim, save for fraud.
Tracked changes, placed where they belong, only the words that differ.
The risk, rated for your side, the clause, and the playbook rule it rests on.
Accept or reject, one by one or all at once. Nothing lands until you do.
Supplier-leaning. Four items to negotiate. The highest risk is the Customer's unlimited liability in clause 14.2.
The findings in plain words, and the document left as it is.
Every figure in the answer is looked for in the document. One that is not there is flagged, not shown as fact.
An MSA above the document, or an amendment to it, is read with it. A statement of work that is silent on liability is not reported as uncapped.
Review this lease from the tenant side.
Clausel reads the side from the brief and does not ask it again. Leave it out, and the intake asks once, before the review starts.
Long documents
A long agreement gets the same care as a short one.
A contract that does not fit in one pass is split into windows along clause boundaries, never inside a clause, and at most six. Every clause is read once, the cards carry the document's own numbers, and the closing verdict is written over all of the findings, not the last batch.
A window starts and ends on a clause, so no provision is read in halves.
The scout treats a schedule and the final boilerplate as closely as the operative clauses. A number buried in a fee schedule is a finding.
When a PDF has no text layer, Clausel reads the page images with a vision model and transcribes them before the review starts.
Six passes, one ledger of cards, one closing verdict over everything found.
Word
Opens in Word the way your counterparty expects.
The export writes native Word tracked changes, not a coloured copy, so the other side accepts or rejects each one in Word. Your reasons travel as Word comments. When their markup comes back, import the .docx and their tracked changes land as live marks in the canvas.
Insertions and deletions as Word revisions, author Clausel. Their own edits are tracked too.
Each change carries its note as a Word comment on the words it changes.
Import the counterparty's .docx. Its tracked changes become live marks, ready to accept or reject against your playbook.
A download card offers all three. The firm's letterhead frames the signed PDF, not the Word file.
The Customer's liability under this Agreementshall be unlimitedshall not exceed the fees paid in the twelve months before the claim arose, save for fraud or wilful misconduct.
shall be unlimited
shall not exceed the fees paid in the twelve months before the claim arose
Playbook §4.1: liability capped at twelve months' fees.
After the review
Reviewed here. Approved here. Signed here.
A redline does not leave Clausel to get finished. You decide each change, an approver binds one exact version, the other side gets a link once a second person agrees, and every party signs, all on the same contract.
You decide each change. Nothing lands until you do.
The limit. A change is a tracked mark until you accept it. Accept all is your action too, and the Word file carries every decision as a native revision.
Approval belongs to one exact version of the text.
The gate. Sending is refused until the firm's send rule, the review approval and the approver chain are met, wherever they apply.
The other side sees the named items, and nothing else.
The limit. One person cannot share alone. Every view and comment by a guest is logged.
Every party signs, in order, on one document.
The gate. An edit after sending pauses signing. If a party named in the document has nobody signing for it, the envelope does not go.
Speed
Fast where the document is heavy.
No stopwatch figure here. Three things in the code keep a long review short, and each one is on this page because it is there.
Sections read at once
The scout reviews up to four sections at the same time and merges what they find before the main run.
The proof runs alongside
The proof of each fix runs alongside the main run, not after it.
Accept all is one action
Accepting every change happens in the canvas at once. No model is asked to retype the document.
Testing
Tested on contracts with planted problems.
We test the review on contracts written to trip it: planted defects, a key of what must be found, and clauses that already meet the book and must be left alone. No score is quoted here. Your results depend on your contracts and your playbook.
Each carries planted contradictions and missing terms. The consistency engine runs over them with no model and no playbook, and its findings are scored against a key. A finding that matches no row is printed, not hidden.
Every applicable rule must get a verdict, a breach must land on a clause the key names, an absence must be reported, and a clause that already meets the book must be left alone. Breaches the key did not plant are printed in full. Each document runs three times, and a disagreement between runs is a defect.
A real contract goes through the real lane, and the test reads the document that comes back, not the list of cards.
Separate tests run a review and an analysis and check that the quote check and the grounding check ran, and that neither accused a document that was read correctly.
On your own repository, the rule simulator tries firm rules, such as routing, approval gates and automations, read-only, before they go live. It does not test redlines or playbook positions.
Questions lawyers ask about review
No. Every change arrives as a tracked change. Nothing is written into the document until you accept it, one by one or all at once. A rejected change leaves the original words as they were.
Clausel still reviews the contract. The thirteen detectors find the classic one-sided terms, and the consistency engine finds where the document contradicts itself. A written playbook is what lifts the review to your firm's own positions. See the rules engine.
On a redline the check is placement: a change that cannot find its words in the document is not placed, is not counted, and the review says so. Each card's quoted words are also looked for in the text, and a quote that cannot be found is reported as not found. In Analyse, compare and ask, the figures in the answer are checked against the document.
Yes. Import their .docx and their tracked changes land as live marks in the canvas, ready to accept or reject against your playbook.
The side you tell it. Say it in the brief, for example "from the tenant side", and Clausel does not ask again. Leave it out, and the intake asks once. Risk is rated for that side: a term that hurts the side you act for is High, and one that hurts the other side is Moderate.
Yes. An Associate equipped to review, pointed at a contract, runs the same review and files the issue table on the contract. A workflow can run the review as a step too, and a person approves before anything reaches an outside system.
The contract stays in Clausel. You decide each change, an approver binds one exact version, the other side gets a link once a second person in the firm agrees, and every party signs on one document with a sealed certificate. See approval and signing.
Bring the contract you negotiated last week.
Book a demo and read the redline Clausel writes against it. Decide each change, then send it on to approval and signature.
- FirstA redline on a contract you know well
- ThenAnalyse, long documents and the Word round trip
- LastApproval and signing on the same contract