A Contract Review That Quotes the Contract and Cites the Page.
A playbook holds your standard position, a fallback and a severity for each clause. FlowVerify compares a draft, or the other side’s paper, against it in one pass and keeps only the findings it can match to the document’s own words.
- A quote and a page for every finding
- Word redline with tracked changes
- A pre-send check that uses no AI
Their draft v4Page 1 of 2
4. Payment Terms
The Customer shall pay each undisputed invoice within ninety (90) days from receipt of invoice. No interest shall accrue on amounts paid within this period.
5. Service Levels
The Supplier shall meet the service levels set out in the applicable Statement of Work.
Payment terms
Deviatesp. 1Clause 4 · Payment Terms
“within ninety (90) days from receipt of invoice”
Playbook position: invoices are paid within 45 days.
Proposed change
within ninety (90) days
within forty-five (45) days
01The playbook
Your Positions, Written Down Once
For each clause you set the position you want, a fallback you can accept and how much a deviation matters. Four starter playbooks are copied into your workspace once. After that they are yours to edit.
MSA: when we are the supplier
MSADefault for this document typePayment terms
HighStandard position
Invoices are paid within 45 days of acceptance. For a micro or small enterprise supplier, section 15 of the MSMED Act, 2006 caps an agreed period at 45 days, and allows 15 days where nothing is agreed in writing.
Fallback you can accept
No fallback
HighMust be presentLimitation of liability
HighStandard position
Each party’s total liability is capped at the fees paid in the twelve months before the claim.
Fallback you can accept
A cap of up to twice those fees.
HighMust be presentConfidentiality
MediumStandard position
Mutual, and lasting three years after the agreement ends.
Fallback you can accept
Up to five years.
MediumMust be presentTermination
MediumStandard position
Either party may end the agreement on 30 days’ written notice.
Fallback you can accept
Up to 60 days’ notice.
MediumMust be presentGoverning law
LowStandard position
Indian law, with the courts at Bengaluru.
Fallback you can accept
Courts at another city in India.
LowMust be present
A Default for Each Document Type
Mark one playbook as the default for NDAs, MSAs or any other type, and a review of that kind of document starts with it selected.
A Missing Clause Is a Finding Too
Tick Must be present, and a document without that clause gets a finding with the wording to insert and the place to insert it.
Its Own Permission
Playbooks are edited by people who hold the playbooks permission. Grant it to a legal operations role without opening the rest of workspace settings.
02How a review runs
From a PDF to a List of Findings
A review takes the file of a draft document, yours or the counterparty’s, and returns findings grouped by risk. Four things happen in between.
- 01
Pick the Playbook and the Depth
Choose the playbook for this kind of document. Standard suits most agreements. Deep takes a longer look at a long or high-stakes one.
- 02
The Document Is Split Into Clauses
Numbered headings, sub-clauses and the signature block are found from the text on each page, so every clause keeps its page number.
- 03
Every Rule Is Compared in One Pass
The model reads the clauses and your rules together and answers once for each rule: it matches, it deviates, or the clause is missing.
- 04
Only What Matches the Text Is Kept
The server looks for the quoted words in the clause. A finding shows the document’s own text and its page. A rule that could not be checked says so.
Before the Model Reads It
Nothing is sent to a model until a workspace admin accepts the AI terms. Aadhaar numbers, PANs, bank details, email addresses and phone numbers are replaced with placeholders first.
Risk Follows Your Severity
A finding takes the severity you gave the rule, one level lower when the document is within your fallback. Findings are listed high, then medium, then low.
03A finding
One Finding, Read From Top to Bottom
A counterparty MSA reviewed against the supplier playbook, as it appears on the document page. The numbers mark what the notes describe.

The Document Stays Beside It
The reviewed file, with page thumbnails and find in document. The page link on a finding opens that page.
Risk at a Glance
Two high, one medium and one low finding, under the name of the playbook that was applied.
The Finding
Payment terms is marked Deviates. The p. 1 link opens that page, and the line below names the clause.
The Quote and Your Position
The quoted words come from the document itself. Under them is why they depart from the playbook, then your playbook position.
The Proposed Redline
The words to strike and the words to put in their place.
Accept or Dismiss
You decide each finding. Accepted ones go into the Word redline and, for a draft written in FlowVerify, back into the editor as suggested edits.
04Decisions
Accept, Dismiss, and Send the Redline Back
A person decides each finding. For a document that came from the drafting editor, accepted findings appear there as suggested edits. For the other side’s paper, download the redline as a Word file with tracked changes.
- A deviation becomes a tracked deletion and insertion
- A missing clause becomes an inserted clause
- Dismissed findings are left out of the file
- The file carries the wording read from the PDF, not its original formatting
Findings
3 of 4 decidedPayment terms
HighDeviates · p. 1
AcceptedIn the redlineLimitation of liability
HighMissing · p. 2
AcceptedIn the redlineConfidentiality
MediumDeviates · p. 2
OpenIn the redlineGoverning law
LowDeviates · p. 2
DismissedLeft out
Export redline with
Redline_MSA-Northwind-Systems.docx
3 tracked changesText read from the PDF. Original formatting is not kept. AI-generated, not legal advice.
4. Payment Terms
The Customer shall pay each undisputed invoice within ninety (90) forty-five (45) days from receipt of invoice.
7. Confidentiality
These duties continue for seven (7) three (3) years after this Agreement ends.
9A. Limitation of Liability
Each party’s total liability is limited to the fees paid in the twelve (12) months before the claim.
12. Governing Law
This Agreement is governed by Indian law. The courts at Mumbai have jurisdiction.
05Pre-send check
A Second Check That Uses No AI
The pre-send check is a fixed set of rules. It runs in the send wizard’s Review step and again on the server at every send, over the envelope and the text of the document.
- Structure: a signer with no field, an SMS code without a phone number, a deadline already in the past
- Document text: a lease long enough to need registration, a document outside the IT Act, payment terms beyond 45 days with a micro or small enterprise
- A finding that rests on a statute cites it, and one that needs a change links to the step where you make it
Pre-send check
Lease Deed — Whitefield Warehouse
Blockers
Lease term of 3 years needs registration
Fix in Prepare documentA lease for more than one year must be registered. E-signing alone does not complete it.
Registration Act, 1908, s.17(1)(d)S. Venkatesh has nothing to sign
Fix in Prepare documentPlace at least one field for every signer.
Warnings
S. Venkatesh needs a phone number for the SMS code
Fix in Add recipientsAdd a mobile number or switch to an email code.
Notes
Goes to 1 approver before the signers
Signers are invited once the approver approves.
Admins Choose Which Rules Block
In Settings, tick the rules that should stop a send. The others become warnings. A few, such as a signer with nothing to sign, always block.
Rules that block sending
- Nobody needs to signAlways
- Signer has no fieldsAlways
- Lease over 11 months (registration beyond one year)Blocks
- Document the IT Act does not apply toBlocks
- Payment terms beyond 45 days with a micro or small enterpriseWarns
- Deadline already passedBlocks
Stamp Duty, as an Estimate
The figure comes from FlowVerify’s stamp tables for the state and the document type, with the article it rests on. Where the tables cannot give a figure, it says so. These checks point the sender to what needs a look. They are not legal advice.
Stamp duty
- State
- Karnataka
- Document
- Lease
- Terms read
- ₹25,000 a month · 11 months
- Basis
- Article 30 · term up to 1 year
- Estimate
- ₹500
From FlowVerify’s stamp tables, with the article and formula shown. Verify the figure before you rely on it.
Keep Reading
- Before reviewDrafting & Clause LibraryWrite the first draft from a brief, in your approved clause wording. Accepted findings come back into the editor as suggested edits.Read more
- After reviewSend for SignatureOnce the wording is settled, add recipients, place the fields and send by email, SMS or WhatsApp.Read more
- For legal teamsLegalDrafts from approved clauses, review with redlines, a searchable repository and an evidence record ready to produce.Read more
No. It is a first pass that shows where a document departs from positions you wrote down, so the person reviewing starts from a list and not from a blank page. Every review is labelled AI-generated, not legal advice, and a person accepts or dismisses each finding.
The server checks each finding against the document before you see it. The clause it names must exist, and the quoted words must appear in that clause. The excerpt shown is the document’s own text with its page number. A rule the review could not check is marked not checked. It is never shown as passed.
Yes. Add their PDF or Word file as a draft document and review it against your playbook. The findings you accept export as a Word file with tracked changes that you can send back.
A deviation appears as a tracked deletion and insertion, a missing clause as an inserted clause, and dismissed findings are left out. You choose between every suggestion that was not dismissed and the accepted ones only. The file is built from the text read from the document, so it carries the wording and the changes, not the original formatting.
No. The pre-send check uses no AI. It is a fixed set of rules that runs on every send: a signer without a field, a deadline in the past, a lease long enough to need registration, a document the Information Technology Act, 2000 does not apply to, and payment terms beyond 45 days with a micro or small enterprise. The rules about the document’s text cite the statute they rest on, and admins choose which rules block a send.
No. They are estimates by state and document type from FlowVerify’s stamp tables, shown with the article and formula they come from. Where the tables cannot give a figure, FlowVerify says so and marks it for review. Check the figure before you rely on it. It is not legal advice.
Book a demo
See Your Playbook
Review a Real Contract
Bring a contract the other side sent you. We review it against a playbook with you, live, and download the redline.
What you get
- A live walkthrough on one of your own agreements
- A workspace set up for your team
- Answers from the people who build it