Contract Review Checklist: What to Verify Before You Sign Off
You finish reviewing a contract comparison. You've gone through every change. You send your markup to the partner. Two hours later, they ask: "Did you check whether the cross-references still work after they renumbered Section 7?" You didn't. You checked every change the comparison showed. You didn't check the things the comparison doesn't show.
This is the gap between reviewing changes and reviewing the contract. A comparison tool shows you what changed between two versions. A thorough review verifies that the contract as a whole is consistent, complete, and accurate after those changes. The comparison is an input to the review. It is not the review itself.
This post provides a practical checklist for reviewing contract comparisons. It is organized by priority: the items most likely to affect the deal come first. The entire checklist adds 15-20 minutes to a review. For a contract where a missed change can cost thousands or millions, those minutes are the cheapest insurance available.
Before you start: setup checks
Before reviewing a single change, verify you are reviewing the right thing.
Confirm the source documents
Verify that the two versions being compared are the correct pair. Check file names, dates, and version numbers. The most damaging review error is not missing a change: it is reviewing the wrong comparison entirely. If someone sent you "Agreement_v4_FINAL_clean.docx" and you are comparing it against "Agreement_v3_clean.docx" but the actual last agreed version was "Agreement_v3.1_revised.docx," your entire review is based on incorrect inputs.
Check the comparison quality
Scan the comparison output for garbled sections. If large blocks of text show as completely deleted and reinserted (rather than showing specific word-level edits), the comparison may have misaligned the documents. This happens when documents have significantly different formatting or when sections were moved. If the comparison looks garbled, try a different comparison tool or check whether the source documents are the correct versions.
Note the change count and composition
Before diving in, note how many total changes the comparison shows. If your tool classifies changes, note the breakdown: how many are content changes, how many are formatting? This sets your expectations. A comparison with 20 content changes is a focused review. A comparison with 120 content changes signals a heavily negotiated round that needs more time.
Step 1: Defined terms first
Go to the definitions section and review every change there before reviewing anything else.
For each changed defined term:
- Note the term name and what changed (narrowed, expanded, threshold added, made asymmetric).
- Search the document (Ctrl+F) for every instance of that term.
- For each instance, evaluate whether the definition change alters the meaning of that clause.
- If the changed term references other defined terms, check whether those terms also changed.
This step takes 5-10 minutes on a typical contract. It catches the highest-leverage changes: a single definition edit can affect 20+ clauses throughout the agreement.
Step 2: High-priority changes
After defined terms, review the changes most likely to affect the economics and risk allocation of the deal. If your comparison tool classifies changes by importance, start with "critical" and "high" changes. If not, prioritize these sections manually:
- Financial terms: fees, pricing, caps, thresholds, penalties, payment schedules.
- Liability and indemnification: caps, exclusions, carve-outs, basket amounts, deductibles.
- Termination: triggers, cure periods, notice periods, post-termination obligations.
- Intellectual property: ownership, license scope, assignment provisions.
- Confidentiality: scope, duration, exclusions, permitted disclosures.
- Representations and warranties: scope, qualifiers (knowledge, materiality), survival periods.
For each change in these sections, evaluate: does this change the risk allocation, the financial terms, or the obligations? If yes, flag it for discussion. If no (punctuation fix, clarification that doesn't change meaning), note it and move on.
Step 3: Tables and schedules
Tables need separate attention because comparison tools handle them less reliably than running text.
- Identify every table in both versions. Confirm the same tables exist in both.
- For each table, compare the structure: same rows? Same columns? Any merged or split cells?
- For pricing tables: verify every number cell by cell.
- For SLA tables: check thresholds, measurement periods, and penalty formulas.
- For disclosure schedules: compare each entry. Note additions, deletions, and modifications.
- Cross-reference table content against the contract body. If the contract says "$10,000 monthly fee" and the pricing table says "$12,000," there is an inconsistency.
Do not rely solely on the comparison tool for table changes. Open both versions side by side and verify manually. This takes 5-10 minutes for most contracts and catches the changes that carry the most financial risk.
Step 4: Cross-references and numbering
If any sections were added, deleted, moved, or renumbered, verify that all cross-references still point to the correct targets.
- From the comparison, list every section that was renumbered.
- Search the document for references to the old section numbers. Any remaining references are broken.
- For updated cross-references ("Section 7.3" changed to "Section 7.4"), verify the new target is correct.
- If sections were deleted, search for any remaining references to those sections.
- Check exhibit and schedule references if any were added, removed, or reordered.
This step takes 5-10 minutes and prevents a surprisingly common drafting defect: a contract with provisions that reference the wrong sections.
Step 5: Remaining changes
After the priority items, review the remaining changes. These are typically:
- Boilerplate edits: governing law, dispute resolution, notices, assignment provisions. These matter but are lower priority than financial and liability terms.
- Clarifications: language changes that don't alter meaning. Confirm they truly don't alter meaning (sometimes a "clarification" subtly shifts scope).
- Formatting changes: if your tool shows them separately, scan for any structural changes (heading levels, numbering) among the formatting edits. Skip pure visual changes (font, spacing).
Step 6: Final consistency checks
After reviewing all changes, do a final pass on the contract as a whole.
Dates and deadlines
Search for all dates in the contract. Verify they are consistent. If the effective date is January 1 and a milestone table shows a pre-effective-date deadline, there is a conflict. Check that term, renewal, and notice deadlines are logically consistent.
Party names
Verify that party names are consistent throughout. If "ABC Corporation" is used in the preamble and "ABC Corp" or "ABC" appears elsewhere, confirm these are intentional short forms, not errors.
Exhibit and schedule completeness
Confirm that every exhibit and schedule referenced in the contract body actually exists. If the contract says "as set forth in Exhibit D" and there is no Exhibit D, that is a gap. Also confirm that every attached exhibit and schedule is referenced somewhere in the contract body.
Signature block accuracy
Verify party names, titles, and entity types in the signature block match the preamble and defined parties. A mismatch between the defined "Party A" and the entity name in the signature block can create execution issues.
The complete checklist
| Step | What to check | Time |
|---|---|---|
| Setup | Correct source documents, comparison quality, change count | 2 min |
| 1. Defined terms | Every definition change + trace references through the document | 5-10 min |
| 2. High-priority | Financial, liability, termination, IP, confidentiality, reps/warranties | Varies |
| 3. Tables | Structure, cell content, cross-reference with contract body | 5-10 min |
| 4. Cross-references | Renumbered sections, broken references, orphaned pointers | 5-10 min |
| 5. Remaining | Boilerplate, clarifications, formatting with structural significance | Varies |
| 6. Consistency | Dates, party names, exhibit completeness, signature blocks | 3-5 min |
Total overhead: 15-20 minutes beyond reviewing the individual changes. This checklist catches the categories of errors that comparison tools don't surface: cascade effects, broken references, table discrepancies, and internal inconsistencies.
The bottom line
A comparison tool tells you what changed. A review checklist tells you what to verify. The comparison is necessary but not sufficient. The changes it shows are only part of the picture. The defined term cascades it can't trace, the cross-references it can't validate, and the table changes it may have garbled all need separate attention.
The checklist in this post is not exhaustive. It is practical. It covers the categories of errors that we see most often in contract review and that cause the most problems when missed. Adapt it to your practice area and your contract types. The structure matters more than the specifics: review in priority order, check the things the comparison doesn't show, and verify consistency before signing off.
If you want a comparison tool that classifies changes by importance so you can work through the checklist faster, try Clausul. The tool handles detection. The checklist handles everything else.
Frequently asked questions
How long should a contract review take?
It depends on the contract length, complexity, and the number of changes between versions. A 5-page NDA comparison with 10 changes can be reviewed in 15-20 minutes. A 40-page MSA comparison with 80 changes takes 1-2 hours for a thorough review. A purchase agreement with disclosure schedules, exhibits, and 150+ changes can take half a day. These times assume a comparison tool is producing the initial markup. Without one (manual side-by-side reading), double or triple the estimates. The checklist in this post adds 15-20 minutes to any review but catches the categories of errors that cause the most problems.
What is the most commonly missed issue in contract review?
Defined term cascades. A change to a defined term in the definitions section affects every clause that references that term, but the affected clauses show no text change in the comparison. Reviewers see the definition change, evaluate it in isolation, and move on without tracing the downstream impact. This is why the checklist starts with defined terms: they are the highest-leverage items and the most frequently underreviewed. The second most commonly missed issue is broken cross-references after section renumbering.
Should I review a contract comparison top to bottom?
No. Top-to-bottom review is the default approach but not the most effective. A better approach is priority-based review: start with defined terms (highest leverage), then review changes classified as high-importance or critical, then check tables and schedules, then verify cross-references if sections were renumbered, and finally review remaining changes. This ensures the items most likely to affect the deal get your best attention rather than whatever happens to appear on page 1.
What should I do if the comparison has too many changes to review?
First, check whether formatting noise is inflating the count. If the comparison shows 150 changes and 100 are formatting (font, spacing, style), you really have 50 substantive changes to review. Use a comparison tool that separates formatting from content, or manually triage the first 20 changes to estimate the noise ratio. If you still have too many substantive changes, prioritize: financial terms first, then obligations, then defined terms, then boilerplate. Flag anything you cannot review thoroughly and communicate that to the partner or client so they can decide whether to allocate additional review time.
Do I need a checklist for every contract comparison?
Not every comparison needs the full checklist. For a simple NDA with 5 changes, a quick scan is sufficient. The checklist is most valuable for substantive agreements (MSAs, purchase agreements, employment agreements, loan agreements) with 20+ changes, multiple sections, tables, defined terms, and cross-references. The more complex the contract and the more changes between versions, the more value the checklist provides. If the contract value or risk justifies a thorough review, use the checklist. If it is a routine document with minor edits, use your judgment.
What tools help with contract review?
A comparison tool is essential for any multi-page contract review. Word Compare is built into Word and handles basic comparisons. Dedicated tools like Clausul, Litera, and Draftable provide better accuracy, change classification, and table comparison. Beyond the comparison tool, Ctrl+F (Find) is your most important tool for tracing defined terms and checking cross-references. A checklist (like the one in this post) provides the review structure. And a clean, organized file naming convention prevents the most common setup error: comparing the wrong versions.