Book a time with our legal AI experts for a personalized demo of our autonomous agents. The demo itself only takes 15 minutes and you can deep dive into the use cases most relevant for you, whether it's drafting SoWs, reviewing NDAs, or completing infosec forms.
Use cases/Agentic review
Agentic review,
end to end.
Not a redline suggester. The agent reads the counterparty's paper against your playbook, applies every redline, writes the margin comments and drafts the reply.
Your lawyer opens a finished first draft and decides the flagged checks. Nothing leaves unapproved.
FileHomeInsertLayoutReferencesReview
11 · Limitation of liability
11.2 The aggregate liability of the Supplier under this Agreement shall be unlimited shall not exceed an amount equal to the Charges paid in the twenty-four (24) months preceding the claim, save as provided in clause 11.3.Flank · check 3 of 14Counterparty proposed uncapped liability, an unacceptable deviation under your playbook. Fallback A applied. Held for your review: cap above £2.5m.
3.1 This Agreement shall commence on the Effective Date and continue for five (5) years, renewing automatically for successive periods of twelve (12) months unless two (2) years, unless terminated in accordance with clause 18.Flank · check 1 of 14Silent rollover is outside every position in your playbook. Redlined to your preferred two-year term.
In the same review11 checks auto-approved3 for your decisionReply drafted after sign-off
The counterparty's Word document, every redline already in it, in your lawyer's inbox. Each change carries a margin comment saying which check produced it and why, so the first thing a reviewer sees is the short list of decisions that are actually theirs. Screens are illustrative and use fictional deal data.
01 · The workflow
The whole review, not just the redlines.
Every step from the paper arriving to the reply going out is run by the agent. Your lawyer joins twice, and both times to decide.
AgentTake the paperCounterparty paper arrives by email, in your own environment
AgentRead it against your playbookEvery check, across the whole contract
AgentApply every redlineTracked changes and margin comments, in the document
AgentFlag what needs a lawyerYour rules, or its own doubt. Never risk alone
Your lawyerApprove, edit or revertEach flagged check, card to clause
AgentDraft the replyFrom the final document, only after sign-off
Your lawyerSendOne action, the redlined .docx attached
AgentRecord itMarked handled, the reply on the thread
Two human steps in eight, and both are decisions. The agent runs the reading, the redlining, the comments and the reply. Judgment stays with your lawyers.
Northwind sent their MSA back, can you take a look
Hi both, Northwind's markup attached. They want to move on liability and the renewal term. Can we turn this by Thursday?
The agent picks it up
Identifies third-party paper on the counterparty's form, loads your MSA playbook · 1 min
What the agent checked, across all 42 pages
Term and renewal, clause 3playbook
Limitation of liability, clause 11playbook
Data protection, clause 15 and schedule 3playbook
Assignment and subcontracting, clause 21playbook
Governing law and jurisdiction, clause 24playbook
A sub-processor list your playbook does not coverbeyond playbook
Review agent
The first draft is ready: 14 checks across the contract, every redline applied and commented. Three need your decision.
1Clause 11.2. Northwind proposed uncapped liability. I applied fallback A, a cap at 24 months' fees. Held because your rule holds any cap above £2.5m for review.
2Clause 3.1. A five-year term with silent rollover. No position in your playbook covers a rollover, so I redlined to your preferred two-year term and left a comment. Held because I am not confident the counterparty will accept it without a fallback.
3Schedule 3. A sub-processor list your playbook does not address. Advisory only; it will not hold the review.
One click from your inbox opens the review. Each check anchors to the clause it governs, and the reply is drafted only once you sign off.
The reply goes out
Drafted from the final document after sign-off, the redlined .docx attached, marked handled on the thread
Every redline traces to a check, and every check says why. Your lawyer verifies decisions, not pages.
02 · Where it fits
Counterparty paper, at volume.
Third-party paper is the work legal teams most want off their desk and trust least to hand over. It is also the most playbooked work they have. Four shapes come up again and again.
Supplier and vendor paper
Services agreements, SaaS terms and purchase terms on the supplier's form, under your thresholds, checked against your positions.
Customer paper at scale
The deals where the customer insists on their MSA. Your commercial team's volume, reviewed to one standard.
NDAs on their form
The highest-volume inbound of all, and almost entirely playbook. Mutuality, term, carve-outs and governing law, every time.
Data terms and DPAs
Counterparty data protection terms read against your positions, your transfer rules and your sub-processor requirements.
How to tell whether you have this
Two or more of these usually means first-round review is sitting with the wrong people.
- Counterparty paper waits days in a shared inbox for a lawyer to have an hour
- Your positions exist, in a playbook or in a senior lawyer's head
- The same five clauses cause the same five arguments on every deal
- Sub-threshold supplier paper queues for a lawyer because there is nowhere else for it to go
- Outside counsel is on volume rates for first-round markups
03 · The line
Where assistants stop.
An assistant makes your lawyer faster at a task that still lands on your lawyer. They open the paper, they read every clause, they choose the redline. The agent does the task. What comes back to the lawyer is the part that was always theirs.
The judgment line
Load the playbookEvery position, fallback and red line
Read every clauseAgainst every check, all 42 pages
Write the redlinesSurgical, tracked, in the document
Write the commentsThe rationale the counterparty reads
Draft the replyFrom the final document
Decide the flagged callsThe part that was always a lawyer's
Run by the agentYour lawyer
The line is not difficulty, it is judgment. Everything mechanical about a first-round review moves to the agent. The calls that needed a lawyer still get one, and now they get one with the reading already done.
What the queue costs downstream
Counterparty paper waits because someone has to read all of it to find the five clauses that matter. Days of cycle time, and volume rates at outside counsel, are the price of the reading, not the judgment. That is the spend this workflow brings back in.
04 · What changes
The same paper, before and after.
Same playbook, same standard, same lawyer signing off. What changes is who does the reading.
Today
×Counterparty paper waits in a shared inbox for a lawyer to have an hour
×Read all 42 pages to find the clauses that matter
×Look up the position, or ask the person who remembers it
×Write the redline, then the comment explaining it, clause by clause
×Draft the covering email from scratch, and hope it matches the file
×Or send it to outside counsel at volume rates, and wait
×Apply a slightly different standard depending on who picked it up
With agents
✓The agent takes the paper the moment it arrives
✓Every check assessed across the whole contract, every redline already in the document
✓Three flagged checks land in your lawyer's inbox, not forty-two pages
✓Approve, edit or revert, card to clause, in one sitting
✓The reply is drafted from the final document, after sign-off
✓Nothing reaches the counterparty without your lawyer's send
05 · Supervision
A finished draft, checked card by card.
The agent assembles the complete first draft up front, every redline already applied. Your lawyer reviews that draft one check at a time, with the clause alongside.
Counterparty proposed
LiabilityUncapped
Carve-outsNone
IndemnityMutual, uncapped
Clause riskHigh
Held for reviewCap above £2.5m
Every check, against your playbook
Your playbook
PreferredCap at 12 months' fees
Fallback ACap at 24 months' feesApplied
Fallback BCap at £2.5m, whichever is higher
NeverUncapped, in any form
Held for your decision3 of 14
1Clause 11.2 · liability · fallback A appliedApprove · Edit · Revert
2Clause 3.1 · term · redlined to preferred, no fallback covers a rolloverApprove · Edit · Revert
3Schedule 3 · sub-processors · not in your playbookAdvisory
Three things hold a check for a lawyer, and risk alone is never one of them. Your own rule for that check applies, the agent is not confident of its reading, or a technical failure left it to the human. Everything else lands auto-approved with its work shown, and can be reverted.
Edit the card
Change the redline or the comment
On the check itself, tracked-changes style. Once applied, the change flows through to the document and to the reply.
Tell the agent
Say what to change, in plain language
The agent regenerates the redline, the comment and the reply together, so the three never say different things.
Edit the document
Redline by hand, for what no check covers
Something missing entirely, or a piece of custom negotiation. No card needed; the reply picks the change up.
Where this sits in the platform
The mailbox is the front door, the review agent is the engine, the check panel is the supervision. Your lawyer still signs off every paper. What changes is what sign-off means.
06 · Results
What your legal function gets back.
First-round review off the desk, one standard applied to every counterparty, outside-counsel volume work brought back in, and a record of every position taken.
Compliant, 6 checksThe counterparty already met your position. Shown as reassurance, nothing to do
Fixed, 5 checksRedlined to your position or a pre-approved fallback, commented, auto-approved and revertible
Held, 3 checksYour rule applied, or the agent was not sure. Approve, edit or revert
Settled by the agentDecided by your lawyer
The reading is the work, and the reading moves. Your lawyer opens a finished draft and decides three things, instead of reading forty pages to find them.
Minutes
from arrival to a finished first draft, every redline applied
1 sitting
to take a paper from inbox to sent
0
changes in the document without a card saying why
2–4
weeks from contract to production
Supervised review of third-party paper is the workflow enterprise legal teams ask us for most. It runs on the same engine and the same supervision layer as the drafting agents in production at global hospitality groups and a major international law firm. Counterparty redlines to your own paper are the same shape.
Supplier MSAs
SaaS terms
NDAs
DPAs
Purchase terms
Customer MSAs
Consultancy agreements
Licence agreements
Framework agreements
07 · The reply
Review is half the problem.
The reply has to say exactly what the document does, and the position you took has to be findable next time. Both are the agent's job, not a lawyer's.
After sign-off
The reply, from the final document
Drafted only once every held check has a decision. It reflects your edits, and nothing you reverted. If the document changes, the reply regenerates before it can be sent.
One send
The redlined .docx, attached
A well-formed Word document whose tracked changes and comments open cleanly on the counterparty's side. Nothing leaves without your lawyer's explicit send.
On the record
Handled, and findable
The sent item is marked handled with the reply on the thread. At signature, the executed agreement lands in Flank Record with the positions you took.
CheckIn the documentIn the replyOutcome
Clause 11.2 · liabilityFallback A, approved“We can accept a cap at 24 months' fees”Match
Clause 3.1 · termTwo years, approved“We have amended the term and removed the rollover”Match
Clause 21 · assignmentReverted by your lawyerRemoved from the replyReply updated
Clause 15 · data termsEdited on the cardRegenerated to matchReply updated
Schedule 3 · sub-processorsComment added by hand“Please confirm the sub-processor list”Picked up
The email is never written first. It is drafted from the reviewed document, after sign-off, and kept in step with the file being attached. Document and reply never diverge.
08 · Getting live
Live in weeks, with your playbook as the spec.
Nothing to install and nothing to learn beyond an email address. Your playbook is the configuration. Flank turns it into checks with your lawyers, in two short sessions a week.
W1W2W3W4W5W6W7W8
NDAsBuildYour testLive
Supplier MSABuildYour testLive
DPABuildYour testLive
SaaS termsBuildYour testLive
Your timeTwo thirty-minute sessions a week, plus testing on your own paper
Flank builds and testsYour experts testSigned off and live
A playbook is a set of checks, grouped by clause. For each: the position you want, the fallbacks you would accept, the language you never will, sample wording, and which checks to hold for a human. Well-formed playbooks make well-behaved agents, and the first sessions get yours written down.
Deployment and security
Inside your security perimeter from day one. A dedicated tenant in your chosen region, zero data retention with model providers, SSO and MFA, and a full audit trail behind every check, decision and reply.
09 · The whole platform
Review is one workflow, not the limit.
The same supervised agents run the rest of the function on one platform.
Agentic drafting
Complex, conditional documents and the packs around them, drafted by agents from your templates. In production at global hotel groups.
Learn more →
Franchising & licensing
The deepest deployment of the drafting workflow, live at two global hotel groups.
Learn more →
Negotiation support
Agents prepare positions and redlines across the back and forth. Your lawyers make the calls.
Learn more →
Intake & triage
One front door for everything the business sends legal, routed by your rules.
Learn more →
Contract record
Every executed agreement filed at signature, so the record and the contract stop drifting apart.
Learn more →
Implementation
How a deployment runs: the cadence, the team, and who does what.
Learn more →
FAQ
An assistant makes your lawyer faster at a task that still lands on your lawyer: they open the paper, read every clause, choose the redline and write the email. The agent does the task. Your lawyer opens a finished first draft, every redline already applied, and decides the handful of checks that were held for them. For bet-the-company negotiation you still want a lawyer with a good assistant, and we say so.
Everything your playbook covers, across the whole contract: preferred positions, pre-approved fallbacks and the language you never accept. Insertions, replacements and deletions, each the minimal change that lands the position, in wording a lawyer would send, with a margin comment giving the rationale. It executes your playbook's logic, never logic of its own, and it never restructures or reformats the document.
Exactly three things hold a check: your own rule for that check applies, always or on a trigger you set; the agent is not confident of its reading, or the playbook does not say how to fix what it found; or a technical failure left the check to the human. Risk alone never decides it. A high-risk clause that is compliant sits in the panel as reassurance, not as a task. Anything the playbook does not cover surfaces as advisory and never blocks sign-off.
Every held check gets one of three decisions: approve, edit or revert. Auto-approved checks show the same evidence and take the same actions, so spot-checking them is cheap. Every change in the document traces to a card that shows the original text, the proposed change, the comment and the reasoning. Reverting a check takes its redline and comment back out and updates the reply to match. Nothing reaches the counterparty without your lawyer's explicit send.
It says so. Where a check could not be completed or a redline could not be applied, the card shows a plainly marked error state with what could not be done and a manual path to resolve it, never a raw technical error and never a silent gap. Where it is unsure, it holds the check rather than deciding. And it does not silently learn from your edits: changes to the playbook are decisions your team makes, on a cadence you set.
Inside your security perimeter: a dedicated tenant in your chosen region, zero data retention with model providers, single sign-on and MFA, and integration with your own email estate. Administrators see a full audit trail of every check, decision and reply.
Two to four weeks from contract to production, starting with the contract type that hurts most. Your existing playbook is the specification. Where positions live in a senior lawyer's head rather than a document, the first sessions get them written down, which most teams find is worth doing anyway.
