1. Scope and deliverables
Scope disputes begin with the word "including." A list introduced by "including" is read by the customer as the whole job and by the supplier as an example. Neither is being dishonest; the document allowed both readings.
A defensible scope clause does four things:
Instead of: "Supplier will provide implementation services including configuration, training, and support."
Write: "Supplier will deliver the items in Schedule 1. Items not listed in Schedule 1 are out of scope. Acceptance occurs only when the criteria in Schedule 2 are met. Client will provide the access and data listed in Schedule 3 by the dates stated; delays caused by late access adjust the timeline day for day."
The second version is longer. It is also the version that survives a disagreement about what "support" meant.
- States the deliverables as items that can be accepted or rejected.
- States what is excluded — support, training, hardware, travel, third-party fees.
- States the acceptance criteria, or points to a schedule that does.
- States the assumptions: volumes, dependencies, client responsibilities, and access.
2. Price, payment, and acceptance
Money clauses fail in three familiar ways: the price is clear but the triggers are not; acceptance is silent, so payment depends on approval that never comes; and withholding is permitted without limits.
A workable payment clause answers:
Milestones should be verifiable from documents, not from impressions. "Phase 1 complete" is an argument. "Schedule 2 items 1–6 delivered and accepted in writing" is an invoice trigger.
- What triggers each payment — signature, milestone, acceptance, or calendar date?
- Who accepts, against what criteria, and within what period?
- What happens if the customer neither accepts nor rejects? Deemed acceptance is a choice the parties should make deliberately, not discover later.
- What may be withheld, on what grounds, and for how long?
- What happens to amounts already paid if the contract ends early?
3. Variation
Almost every project changes. The question is whether the change is recorded before the work is done. Where it is not, the supplier performs and later claims, the customer disputes the necessity, and the relationship absorbs the damage.
A variation clause needs a mechanism, not a prohibition:
The commercial reality is that teams often cannot wait for paperwork. A clause that acknowledges this — for example, allowing emergency work with written confirmation within two business days — is more useful than one that pretends change will not happen.
- Who may request a change, and in what form.
- Who assesses cost and time impact, and within what period.
- Whether work continues while the change is priced.
- Whether a change order must be signed before work starts.
- What happens to verbal instructions, which are the most common source of unrecorded change.
4. Liability and indemnities
Liability clauses are where commercial risk is allocated, and where parties most often assume they agree when they do not.
The clause must settle:
Two tests are worth applying. First, can both parties state the maximum exposure in one sentence? Second, does the indemnity procedure require notice within a period that a real business can meet?
A cap that is never read is not a risk allocation. It is a sentence that will be argued about after the loss.
- The cap. Amount, basis (fees paid, contract value, a fixed sum), and whether it is per claim or in aggregate.
- The exclusions. Indirect and consequential loss, lost profit, lost data, business interruption.
- The carve-outs. What survives the cap — fraud, willful misconduct, death or personal injury, confidentiality breach, intellectual property infringement.
- The indemnities. Which risks are indemnified rather than left to general damages, and the procedure for notifying and defending a claim.
- Insurance. Whether cover is required, at what level, and whether the certificate must be provided.
5. Termination and exit
Parties negotiate hard on price and lightly on exit. Then the relationship changes, and the document offers no orderly way out.
A termination clause should cover:
The practical test: if the contract ended next month, could both parties execute the exit from the document alone? If not, the clause is incomplete.
- Termination for cause. What counts as material breach, the notice and cure period, and whether repeated minor breaches aggregate.
- Termination for convenience. Whether it exists, the notice period, and the exit fee or compensation.
- Insolvency and change of control. Whether these are triggers, and on what terms.
- Transition. Handover of data, documents, and access; continued services for a defined period; cooperation obligations.
- Survival. Which clauses continue — confidentiality, IP, liability, payment, dispute resolution.
- Refunds and accrued rights. What is paid, what is returned, what is cancelled.
The clause that decides the rest
Governing law and dispute resolution do not cause the dispute, but they decide how expensive it becomes. A contract that is silent on forum can produce a jurisdictional fight before anyone reaches the merits.
Confirm three things: the governing law, the forum (court or arbitration), and the seat or court with jurisdiction. If arbitration is chosen, check that the clause is capable of being performed — a clause that names no institution, no seat, and no number of arbitrators creates its own dispute.
A five-minute drafting test
Before signature, ask these questions of the document as written:
If any answer is no, the clause needs work — regardless of how standard it looks.
- Can I list the deliverables without reading the emails?
- Does every payment have a trigger and a date?
- Is there a change mechanism someone can actually follow?
- Can both sides state their maximum exposure in one sentence?
- Could either side exit next month using only the contract?
What a good contract review looks like
A review is not a proofread. It is a test of whether the document can be operated by the people who will actually run it.
We read in four passes: the commercial deal (parties, scope, price, term); the failure modes (late delivery, withheld acceptance, a key person leaving, a change in the market); the allocation of risk (liability, indemnities, insurance); and the exit (termination, transition, survival).
Then we test the document against the five clauses above, and against the governing law and forum. A review that produces a list of comments without a view on which issues are commercial and which are legal is only half finished.
The output should be short: an issue list ranked by exposure, proposed wording for the clauses that carry the risk, and a one-page summary a business reader can act on. Length is not diligence.
