Review guide

Commercial Contract Review Checklist for In-House Teams

A contract review is only useful if it ends with a decision someone can make. This checklist orders the reading so the decision comes first and the clauses that change it come next.

Gemma4.net review library Updated 2026-11-13 中文版

Start with the decision, not the document

Most contract reviews begin with page one and end wherever attention runs out. A more reliable order is to write the decision down first: are we approving signature, approving a term sheet, rejecting a clause, or preparing a negotiation position? Each answer changes which parts of the document deserve close reading and which parts can be skimmed.

Write three lines before you open the file: the business decision, the person who will make it, and the threshold that would change the answer. A renewal that saves a working integration may be worth a wider liability cap; a pilot with no integration may not. Without that threshold, every clause looks equally important and the review has no stopping rule.

Next, identify the document type and its role in the deal. A master agreement sets the frame, an order form carries the commercial specifics, a statement of work describes delivery, and a data processing agreement sits alongside all three. Read them in that order and check which document wins when they conflict. Order-of-precedence clauses are short, easy to skip, and decide real disputes.

Map the parties and the paper trail

Check the legal names, registration numbers where they appear, and the addresses used for notices. A contract signed by an entity that is not the entity paying the invoices creates a collection problem later. Where a parent, affiliate, or local subsidiary is involved, confirm which one carries the obligation and which one receives the service.

Then reconstruct the paper trail: the original agreement, every amendment, side letters, statements of work, and any accepted change orders. Reviews go wrong when a reviewer reads the master agreement but not the amendment that changed the liability cap. If the file set is incomplete, say so in the finding rather than assuming the missing document is harmless.

Signature authority is part of the review, not an administrative afterthought. Check who is permitted to sign under the counterparty’s public records or the signature block you were given, and confirm your own signatory has delegated authority for this value. A well-drafted contract signed without authority is still a problem.

Build a clause checklist for this agreement type

Pick the agreement type to get the clause groups and the specific checks that belong in a first-pass review. The checklist runs in your browser; nothing is uploaded.

Read the commercial core before the legal machinery

Scope, price, term, and termination carry most of the commercial risk, so read them before warranties and boilerplate. Scope should describe the service or deliverable in a way a non-lawyer could audit: what is included, what is excluded, and what counts as a change. Vague scope language is not flexible; it is a future negotiation.

For price, check the unit, the currency, the billing frequency, and the mechanism for changing it. A price that can move by an index, by usage, or by renewal uplift is a different commitment from a fixed fee. Usage-based pricing needs a definition of the metered unit, a dispute window, and a rule for overages, or the first invoice becomes the negotiation.

Term and termination decide how long you are exposed. Look for the initial term, the renewal mechanism, the notice window, and the consequences of early termination. A contract that is easy to leave is worth more than a discount, particularly where the service touches customer data or a critical workflow.

Isolate the clauses that create unbounded exposure

Liability, indemnity, intellectual property, and data obligations are where a routine agreement becomes a board item. Read the liability cap as a formula: is it a multiple of fees paid, a fixed amount, or unlimited for certain categories? Then read the carve-outs, because indemnities and confidentiality breaches are often excluded from the cap.

Indemnities should be reciprocal where the risk is reciprocal, and specific where it is not. An indemnity for third-party intellectual property claims is standard; an indemnity for the counterparty’s own negligence, or for your use of their instructions, needs a second look. Check whether the indemnity is subject to the liability cap and whether defence costs count against it.

Intellectual property clauses need a clear line between pre-existing materials, deliverables, and data. Confirm who owns what, what licence each side needs to operate, and what happens on termination. For data, identify the roles: who decides the purpose, who processes, which subprocessors are involved, where data is stored, and what happens to it at the end. These questions are easier to answer before signature than after.

Check the operational clauses teams forget

Notice mechanics are the most common self-inflicted wound in contract management. Confirm the permitted method, the address or portal, the required content, and when notice is treated as received. A notice sent by email to a person who has left, or sent one day after the window closes, is not notice.

Assignment and change of control decide whether the contract survives a merger, a divestiture, or a reorganisation. Subcontracting and affiliate-use clauses decide who can actually perform the work. Insurance requirements need a certificate, a limit, and a named insured that match the obligation, otherwise the clause is aspirational.

Finally, check dispute resolution and governing law together. An escalation ladder with fixed periods, a mediation step, and a venue that is workable for your team is worth more than an elegant arbitration clause nobody can afford to use. Note the language of the proceedings if the counterparty is in another jurisdiction.

Record findings so a non-reader can act

A finding needs four elements: where it is, what the text says, what it changes, and who should act. “Liability is a problem” is not a finding. “Clause 11.2 caps liability at fees paid in the prior 12 months and excludes confidentiality breaches from the cap; this is below our standard for data-processing vendors; legal owner to confirm before signature” is a finding someone can action without reading the contract.

Rank findings by the decision they affect, not by the order they appear. One high finding that changes whether you sign is worth more than twenty low observations. Keep a separate list for questions: items where the answer depends on facts you do not have, such as the actual data volume or the integration owner. Questions and findings should not be mixed, because they go to different people.

Close the review with a short recommendation and an explicit statement of what you did not review. If you read the master agreement but not the security annex, say so. A review that overstates its coverage is worse than a narrow review that is honest about its boundary.

What a checklist cannot do

This checklist is a reading order, not a legal opinion. Whether a clause is enforceable, whether a limitation period applies, and whether a specific indemnity is market-standard all depend on the governing law, the sector, and the negotiating position. Qualified counsel should confirm anything that carries real exposure.

It also cannot replace the commercial context. The same liability cap can be acceptable for a low-value pilot and unacceptable for a payroll system. Use the checklist to make the review consistent and complete, then apply judgement about the deal in front of you.

Next step

Scope a private review by email

Send the matter, file volume, formats, deadline, and decision question. A person confirms fit, handling, and timing before files move.