See how Spellbook helps legal teams draft contracts faster than ever before.
Book Demo
A contract review checklist is a repeatable list of the terms a reviewer confirms, questions or escalates before a commercial agreement is signed. This contract review checklist covers 25+ critical terms in eight steps: parties and basic information, scope and performance obligations, financial terms, intellectual property, liability and risk allocation, compliance and regulatory requirements, termination and exit, and dispute resolution and governance. After the eight steps come the clauses that justify escalation and a worked example on a vendor master services agreement. Contract-type checklists close the article for NDAs, vendor agreements, employment contracts, SaaS subscriptions, procurement paper, and construction and manufacturing supply agreements.
Most of the items below are pattern checks that repeat on every agreement, which is the part that AI-assisted review inside Word now absorbs, and the rest are the judgment calls that stay with the lawyer.
[cta-1]
To review a contract step by step, work these eight stages in order: confirm the parties and basic information, test the scope and performance obligations, check the financial terms, settle intellectual property ownership, read the liability and risk allocation, confirm the compliance obligations, map termination and exit, then close on dispute resolution and governance. The order carries weight, because a defect in the parties or the scope changes how every later clause reads, and a review that opens at the liability cap usually has to be repeated once the scope is understood.
Average contract value erosion was nearly 9 percent in World Commerce & Contracting’s 2023 benchmark report, which surveyed more than 750 organizations with Icertis. Value erosion of that kind is the defect a reviewer catches by reading the same terms in the same order on every agreement, which is the whole argument for working from a fixed list instead of reading for whatever looks unusual.
The full checklist is also available as a print-ready PDF download for reviews that happen away from a screen.
Incorrect party identification can create enforceability problems and complicate dispute resolution. Confirm the basic information at the outset, because a defect here travels into every obligation and every signature block downstream.
When performance obligations are not defined properly, the parties leave the table with different expectations of the same clause, so define each obligation in detail before signature rather than after the first missed milestone.
Unclear payment terms can end in collection efforts and, at times, litigation. Confirm how payments, penalties and invoicing are handled while the commercial team is still in the room.
Intellectual property (IP) provisions carry long-term risk, and IP disputes are expensive to unwind years after the deal closed. Read the ownership, license and confidentiality terms as one block, because an intellectual property assignment can quietly contradict a license grant three pages later.
Unbalanced liability provisions can expose an organization to financial risk the commercial terms never priced. Read the cap, the indemnity and the warranty provisions together, because a carve-out in one can undo the protection in another, and confirm that the force majeure clause names the specific triggering events it covers rather than leaving them to argument at the worst possible moment.
Warranty disclaimers are a common defect on a sale of goods. A disclaimer of the implied warranty of merchantability has to be conspicuous and has to mention merchantability by name under UCC section 2-316, so a disclaimer buried mid-document is worth flagging even when the commercial terms are otherwise acceptable.
Regulatory penalties can exceed the value of the agreement that triggered them. Confirm that the contract terms align with the compliance standards in every relevant jurisdiction, and where the agreement involves AI-powered services, check it against the risk-based obligations the EU AI Act places on providers and deployers of AI systems.
Data protection clauses are the ones most often copied forward from an old template, and the required terms differ by regime: the CCPA and the GDPR impose different obligations on a business that shares personal information with a vendor, and the two sets of terms are not interchangeable. A clause drafted to satisfy one regime can leave a gap under the other, so confirm which regimes apply before accepting the counterparty’s standard addendum.
Termination clauses define what each party owes when the relationship ends. Confirm that the termination provisions specify notice periods, wind-down procedures and data handling, because wind-down cost, transition assistance and data return are rarely priced during the commercial negotiation.
How a dispute gets resolved changes both the cost and the timeline of resolving it, and an ambiguous jurisdiction clause adds a preliminary dispute over forum before the underlying dispute is heard. Teams working from a standardized review process tend to settle the forum question at policy level rather than argue it deal by deal.
Comparing the clause in front of you against the position your team last accepted is faster with a contract terms precedent tool than from memory, particularly on notice mechanics and governing law, where the acceptable answer varies by counterparty rather than by principle.
Seven contract review red flags on this checklist routinely justify escalation beyond the reviewer: uncapped or unlimited liability, one-sided indemnification, overly broad intellectual property assignment or non-compete terms, auto-renewal with no exit right, terms that conflict with applicable regulation, unilateral amendment rights, and an assignment clause that sweeps in pre-existing work. Each one is a red flag because the cost of accepting it does not surface during review. It surfaces at the first dispute, the first renewal date, or the first regulator question.
Where the cap is the issue, the negotiation is usually about the carve-outs rather than the number: a limitation of liability that caps direct damages at fees paid while leaving indemnity, confidentiality and IP infringement outside the cap is a materially different risk profile from a flat cap on everything, even though the two read almost identically on the page.
[cta-2]
Contract review escalation runs on two thresholds: a clause that falls outside the position your team has already agreed, and a commercial exposure the reviewer is not authorized to accept alone. Naming the owner for each threshold before review starts is what keeps a flagged clause from sitting in an inbox for a week:
The thresholds only work when someone has written them down, and the authority limit is the one your team has set rather than a figure any article can supply. Deal Desk, not sales, owns the playbook positions at most mature teams, and a contract playbook that states the fallback as well as the preferred position is what lets a reviewer tell a deviation apart from an ordinary negotiation. Without it, every clause outside the template looks equally urgent, and the escalation list stops working as a filter.
Escalation during review is a different question from the contract approval workflow that follows it. Review escalation decides who has to look at a clause before the negotiation continues, while approval decides who signs once the terms are settled. Teams that collapse the two end up pushing every redline through the signature chain before it is settled, which slows the work to the speed of that chain.
A contract review example shows what the checklist produces on third-party paper. The example below runs the eight steps over a vendor master services agreement (MSA) sent on the vendor’s own template, naming the checklist step, the finding in the document, and the redline the reviewer asks for. Findings cluster in liability and risk allocation, because a vendor’s own template is drafted to defend the vendor. The reviewer’s output is a redline and a short escalation list, not a verdict on whether to do the deal.
| Checklist step | Finding in the document | Redline requested |
|---|---|---|
| Parties and basic information | Counterparty named as a trading name, not the incorporated entity | Replace with the registered legal name and jurisdiction of incorporation |
| Scope and performance obligations | Deliverables defined by reference to a statement of work that is not attached | Attach the statement of work as a numbered exhibit and make it contractual |
| Liability and risk allocation | Liability cap excludes the vendor’s own indemnity obligations | Bring the indemnity inside the cap, or cap it separately at a stated multiple of fees |
| Liability and risk allocation | Unilateral indemnity running from the customer only, with no fault qualifier | Make the indemnity mutual and limit the triggers to fault-based third-party claims |
| Termination and exit provisions | Auto-renewal on a 90-day notice window with no termination for convenience | Shorten the notice window and add a termination-for-convenience right |
Two of those five findings go to the escalation list rather than straight into the redline, because the cap exclusion and the unilateral indemnity both sit above what a reviewer is usually authorized to accept alone. The cap exclusion is the finding with the largest exposure: a limitation that leaves the indemnity outside the cap is not really a cap, and a limited remedy that fails of its essential purpose can be set aside in favor of the remedies the code otherwise provides. The notice window and the missing statement of work are usually conceded or fixed without escalation.
A contract drafting checklist and a contract review checklist cover the same terms from opposite sides of the paper. The drafting checklist asks what each clause should say before the document exists, so it runs in the order you build the agreement and its output is language. A review checklist asks what the clause in front of you says, what it costs to accept, and what to ask for instead, so its output is a redline and an escalation list.
When you draft the contract yourself you control the default, so the checklist becomes a completeness check: did every term this deal needs reach the document, and does the language say what the commercial team agreed. On the counterparty’s template the same items become a risk check, because every default has already been set by someone whose interests run the other way, so more items land outside the position your team has agreed, and more of them need a named owner before the negotiation continues. Indemnity is the clearest case: the mutual indemnification clause you would have drafted arrives as a unilateral one running in the counterparty’s favor.
The two lists also sit at different points in how a deal moves from paper to signature, and treating them as one step is a common source of confusion on a first pass. A reviewer who starts writing replacement clause language has moved into negotiation, and that is a different conversation with a different approval path. The handoff between the two is itself part of the contract review process, which is why the same person rarely runs both on the same agreement.
A contract review checklist by contract type adds the provisions one agreement type carries that the general framework does not: nondisclosure agreements, vendor and supplier agreements, employment contracts, SaaS subscriptions, procurement and services paper, and construction and manufacturing supply agreements. Run the eight steps first, then layer on the items below for the agreement in front of you.
Most of these items repeat unchanged across an NDA portfolio, which is why drafting customized NDAs with AI tends to be the first workflow a high-volume team automates: the remaining variables are the definition, the duration and the carve-outs.
Vendor agreements arrive on the vendor’s template more often than not, so vendor contract review starts from the counterparty’s defaults rather than your own, and the first pass is as much about what the template omits as about what it says.
Enforceability of the restrictive covenants varies by state, so an employment contract review usually closes on a jurisdiction question rather than a drafting one, and the answer can change the value of the whole package.
Judging whether a cap or a renewal window is normal needs comparison data, which is why teams reviewing subscription paper at volume spend time on choosing contract analysis software rather than redlining from memory.
Procurement paper arrives with its own order of precedence, and the purchase order often controls over the master terms unless the master terms say otherwise. Where the services touch regulated data or a regulated process, the items below run alongside a contract compliance checklist rather than replacing it.
Construction and manufacturing paper moves money against milestones and moves goods across a delivery point, so the payment and delivery mechanics carry most of the risk: when payment is earned, and when risk of loss passes. Absent agreed terms, UCC section 2-509 supplies the default for risk of loss on a sale of goods, so read the delivery and title terms before the price terms.
Spellbook helps legal teams automate contract review inside Microsoft Word, which is where most of the time in a manual pass over this checklist goes. The Review feature redlines the agreement and flags missing, ambiguous or non-standard terms across the liability, indemnification, termination and compliance steps above; the Playbooks feature measures each clause against the positions your team has already agreed; and the Compare to Market feature places a cap, indemnity or renewal term against 20M+ real contracts. The judgment calls stay with the lawyer.
The split between what Spellbook automates and what the reviewer decides runs step by step through the checklist above:
| Checklist step | Spellbook automates | Requires lawyer judgment |
|---|---|---|
| Parties and basic information | Extracts party names, entity details and dates | Validating signature authority |
| Financial terms and payment provisions | Flags missing or incomplete payment terms | Negotiating the commercial terms |
| Liability and risk allocation | Flags a missing cap and a unilateral indemnity | Assessing the acceptable risk level |
| Compliance and regulatory requirements | Flags missing data protection clauses | Evaluating jurisdiction-specific obligations |
| Dispute resolution and governance | Flags a missing arbitration clause | Deciding the strategic forum preference |
Run your next agreement through this checklist without leaving your document. Try Spellbook free and review your first contract directly in Word.
[cta-3]
Assemble the review tooling, the template library and the clause bank before the first agreement lands, and identify who signs off on each category of deviation. Change-tracking and record-retention systems matter as much as the tooling, because a review nobody can reconstruct six months later is difficult to defend. Keep a written checklist for the manual path, since the tooling is not always available at the moment the document arrives, and maintain a clause index that records the standard language for each term, because a reviewer working from memory produces inconsistent redlines.
A contract review runs through document intake, flagging of non-standard clauses, compliance validation, negotiation of the flagged terms, approval and execution. The first three steps are the review proper, and the last three belong to the negotiation and approval path that follows it, which is why a reviewer who starts negotiating has usually skipped a validation step.
The 5 C’s is not a formal legal framework but a mnemonic some practitioners use for good drafting: clear, complete, concise, compliant and consistent. Courts do not apply it. For enforceability they look to the elements of contract formation, which are offer, acceptance, consideration, capacity and legality.
It depends on complexity and volume. A standard NDA is a short review; a complex MSA or a mergers and acquisitions (M&A) agreement is a long one, and the gap is what makes a fixed order worth having. AI contract review software shortens the first pass, which moves the reviewer’s time onto the high-risk items rather than the first-pass scan.
A checklist guides the review process and fixes the order in which terms get checked. A playbook governs the negotiation outcome, so a well-structured negotiation playbook states the preferred position and the fallback on each clause, such as a standard liability cap set at one times annual fees. The two are complementary, and neither one substitutes for the other.
Partly. AI contract review software automates the systematic parts, including clause extraction, gap detection and risk flagging across each checklist step, and it completes the first-pass scan quickly. Lawyer judgment is still required for the strategic calls: the acceptable risk level, the negotiation priorities and jurisdiction-specific interpretation.



Submission Received
Thank you for your interest!
Submission Received
Thank you for your interest!
We're connecting you with the best rep