What a first-pass review should deliver
A useful first pass answers three questions quickly. What did the other side put in this document, which of those terms depart from our standard, and what would we ask for instead. Reading 40 pages to answer them is the slow part, and it is the part software can do.
The analyzer returns a summary card, a clause table with excerpts and risk levels, and a key dates strip, so a reviewer starts with the problems instead of the preamble.
The clauses it looks for
Detection runs across the clause families that cause most disputes and surprise costs.
- Auto-renewal, termination and notice periods.
- Limitation of liability and indemnification.
- Payment terms, late fees and price increases.
- Confidentiality and data protection.
- IP ownership and assignment.
- Governing law and venue.
- Exclusivity and non-solicit.
Risk depends on which side you are on
A broad indemnity is a risk for the party giving it and a protection for the party receiving it. You choose whether to review as customer, vendor or neutral, and the same clause is scored for that position. A vendor reviewing a customer paper sees different flags than a buyer reviewing a vendor MSA.
You also pick a playbook strength, from light for low-value deals to strict for an enterprise buyer.
Redlines with fallback language
For each flagged clause the analyzer suggests replacement wording and a fallback position. A one-sided uncapped liability clause, for example, comes back with a proposed cap tied to fees paid in the prior twelve months and a lower fallback if the counterparty pushes back.
On Team and Business, the redlines export to DOCX with tracked-change style markup, so you can send them to the other side in a format they already use.
Your own playbook on Team and Business
The standard playbook is a sensible default. Most legal and procurement teams eventually have their own positions, such as net 45 payment terms, a 90 day termination for convenience right, or Delaware governing law. Custom playbooks let you record a preferred position and a fallback for each clause, and every later review is measured against them.
What it does not do
ContractsAnalyzer highlights what to check. It is not legal advice, and it does not replace a lawyer on a high-stakes agreement. What it does is cut the reading time so that attorney hours, inside or outside the company, go to negotiation instead of scanning for the indemnity section.
A worked example with a liability clause
Suppose a vendor sends a services agreement that says the supplier's total liability is limited to fees paid in the month of the claim. The analyzer flags it as high risk for a customer, quotes the sentence, and explains that a single month of fees may be far below the cost of a data incident or a failed project.
The suggested redline raises the cap to fees paid or payable in the prior twelve months, with a carve-out for confidentiality breaches. The fallback accepts six months of fees if the supplier will not move. You choose which to send, and you can edit either one before it leaves.