How to Proofread a Contract: A 15-Point Quality Checklist

A contract with a spelling error is embarrassing. A contract with a date inconsistency, a missing appendix reference, and an undefined term is a dispute waiting to happen.

The proofreading that protects organisations from the second category is not the same as the proofreading that catches the first. Here is a systematic approach.

Before you start

Proofreading a contract effectively requires reading it against itself — checking that internal references resolve, that defined terms are used consistently, and that obligations are stated precisely. This is different from reading for content, and it should be a separate pass.

The 15-point checklist

**Parties and definitions**

1. Every party named in the recitals is defined, and every defined party name is used consistently throughout. Check for variations ("the Company," "the Client," "the Purchaser" — each should have one canonical form).

2. All defined terms are used at least once after being defined. Defined terms that are never used create interpretive confusion.

3. All used capitalised terms are defined somewhere in the agreement or in an incorporated document.

**Dates and deadlines**

4. The execution date is present and consistent with the effective date if they differ. If the effective date precedes the execution date, there is a retroactivity issue to be aware of.

5. All stated deadlines are internally consistent. If the agreement requires notice of 30 days before termination, and the minimum term is 60 days, the arithmetic must work.

6. All date formats are consistent throughout the agreement.

**Obligations and scope**

7. Every obligation has a clear obligor (who must do it), a clear object (what must be done), and where applicable a clear deadline (when it must be done).

8. Absolute language ("all," "any," "every," "none") has been reviewed. Each instance either accurately reflects an absolute obligation or has been qualified to match the actual scope.

9. Hedge language ("should," "may," "generally") has been reviewed. Each instance is either intentionally permissive or has been upgraded to an obligation ("must," "will").

**Cross-references**

10. All cross-references to specific section numbers resolve to existing sections. Renumbering is the most common source of broken references — verify after any structural changes.

11. All references to appendices, schedules, and exhibits are satisfied. Every referenced appendix exists and is attached.

12. All defined terms used in schedules are defined in the main agreement or in the schedule itself.

**Numbers and figures**

13. All financial figures are consistent across sections. If a payment amount appears in the recitals, the payment clause, and a schedule, all three instances must agree.

14. All formulas and calculations are correct. Verify that percentages, caps, and floors work as intended for representative inputs.

**Final review**

15. The signature blocks match the parties identified in the recitals. The signer's name, title, and authority to bind are present and correct.

Automating the mechanical checks

Checks 3 through 14 are mechanical enough to be automated. An automated scanner can verify that defined terms are used consistently, that cross-references resolve, that dates are coherent, and that numerical figures agree across sections.

This does not replace legal review — it augments it by ensuring that the mechanical quality of the document is sound before counsel's time is spent on substance.

The pre-signing discipline

Build a proofreading pass into the contract workflow as a mandatory step before any agreement is circulated for signature. The cost is an hour of careful review. The alternative is disputes, renegotiation, or litigation over issues that could have been caught at the desk.