Form and contract review
Every form and contract is checked against your rules before it reaches the person who signs.
A review system that reads a submitted form or an incoming contract, checks each clause and field against rules you wrote, and prepares a marked summary for the person who decides. It shortens the review; it does not replace the reviewer.
No list price. It starts with a diagnostic at a fixed fee, and the build is quoted after it.
How it works
The pipeline, step by step.
- 01
A document arrives for review
A client intake form, a lease, a vendor agreement, an application. From an inbox, a portal or your document system.
- 02
The type and the template are identified
The system knows which rule set applies.
- 03
Fields and clauses are extracted
Each with a link back to its place in the document.
- 04
Rules are applied
Required clauses, forbidden terms, limits, dates, consistency between sections. The rules are written with you in plain language.
- 05
A summary is prepared
What passed, what failed, what is missing, and the passages that need a human judgement.
- 06
A person decides
The reviewer sees the document and the findings side by side, then signs off, requests changes or rejects.
- 07
The outcome is recorded
The decision, the findings and the notes go to your document or matter system.
Connects to tools such as
- Outlook
- Gmail
- SharePoint
- Google Drive
These are examples. We confirm the method for each of your tools before we build.
Where a person approves
The points where the system stops and waits for a person.
- A person signs off every document. The system never approves on its own.
- The rule set is written with you and changed only on your instruction.
- Findings marked as judgement calls are never resolved by the system.
How it is measured
Named measures, scored on your own files before launch and after every change.
- Rule accuracy on a locked set of your past documents with known outcomes.
- Miss rate: findings a reviewer added that the system did not raise, tracked per rule.
- Review time per document, as an operating measure.
How it is run
After launch: monitoring, updates and what you own.
- Monitoring on every review: failures, stuck documents and rule errors raise an alert.
- Rule changes are tested on the document set before release.
- Handover: a runbook, a data map and code owned by the business.
What it will not do
Limits we set on purpose.
- It does not give legal advice or decide whether to sign.
- It does not change the document.
- It does not review document types whose rules you have not approved.
Sectors we build for
The business types this system is built for.
Questions
Who writes the rules?
You do, with us. We turn your checklist into rules the system applies, in plain language you can read and change.
Does it mark up the document?
It prepares a summary of findings with links to the passages. The document itself is not changed.
Can it handle our standard contracts and third-party paper?
Both. Your templates get a rule set each. Third-party documents are checked against the same rules, with more findings routed to judgement.
What does the reviewer still do?
Everything that needs judgement, and the sign-off. The system does the reading and the checking so the reviewer starts with the findings.
Talk to us about form and contract review
Fifteen minutes on a call is enough to tell whether it fits your work. If it does not, we say so.