Document review
The reason contract review is slow is not that lawyers read slowly. It is that they have no way to know, before reading, which contracts deserve the time. So everything gets the same treatment, and the routine work crowds out the work that matters.
What happens to a submitted contract
- The document type is identified automatically — NDA, MSA, SOW, DPA, vendor, consulting or partnership. Nobody has to categorise anything.
- Key terms are extracted — term length, liability cap, governing law, payment terms, renewal, termination, and the rest, depending on the document type.
- Each term is measured against your policy, not against a generic notion of what is reasonable.
- A verdict comes back: green, yellow or red, with every concern listed and attributed to the clause it came from.
Green does not mean approved
It means a reviewer can move quickly with everything in front of them. Every contract is still decided by a person — there is no auto-approval in AeroSpark, deliberately. Speed should come from a reviewer being well-briefed, not from nobody looking.
It reads the counterparty's paper too
A returned redline is the hardest thing to review, because the changes are the point and they are scattered. AeroSpark detects tracked changes on submission, extracts what actually changed, and runs policy against the proposed edits rather than the original.
Documents from the other side are treated as untrusted input: hidden text and instruction-shaped content are stripped before the AI reads a word.
See also AI redlining and the contract register.