Contracts · Pillar guide
The contract review process for small law firms
A contract review process is the repeatable path a contract takes from arrival to signature and renewal. For a small firm it needs four stages — intake, clause review, approval, and date tracking — plus a record of who checked what.

On this page
- What a contract review process has to produce
- Stage 1 — intake and triage
- Stage 2 — the clause review
- Stage 3 — approval and signature
- Stage 4 — the dates after signature
- Who does what in a small firm
- What to record, and why it matters
- Common failure modes
- Where software helps, and where it does not
- A one-page process you can adopt this week
Most small firms do not have a contract review process. They have a habit: the person who usually reads contracts reads this one, marks a few things in yellow, and sends it back. That works until the person is on leave, the contract is a novation of something signed three years ago, or a renewal notice passes while everyone assumes someone else is watching it.
A process is not bureaucracy. It is the difference between a review you can repeat and a review you have to remember. This guide lays out the four stages, the clause questions worth asking every time, and the records that make the whole thing defensible.
What a contract review process has to produce
Four outputs, in this order:
- A decision — sign, negotiate, or decline, made by someone with authority to accept the risk.
- A marked-up record — the issues found, what was changed, and what was accepted as-is.
- An approved final version — the exact document that will be signed, not a version in an email thread.
- A dates record — end date, notice period, notice deadline and owner, captured at signature.
If the process produces only the first two, the firm is running a review, not a contract function. The expensive failures usually happen after signature: a renewal nobody diarised, a notice window that closed, an obligation nobody owned.
Stage 1 — intake and triage
Every contract should enter through one door. In a small firm that door is usually an inbox, which is the problem: the same agreement can arrive as a PDF attachment, a link to a counterparty's e-signature platform, and a scanned copy in a partner's downloads folder.
Triage asks three questions before anyone reads a clause:
- What kind of contract is this? Master services agreement, statement of work, vendor terms, lease, engagement letter, settlement agreement, licence. The type determines the clause set.
- Whose paper is it? A counterparty's standard terms deserve more scrutiny than the firm's own template, because the deviations are where the risk sits.
- What is the value and the exposure? A low-value, short-term purchase can be reviewed against a short checklist. An indemnity that could exceed the firm's insurance needs a second reader regardless of value.
Triage is also where you decide who reviews. In a two-lawyer firm, one lawyer may own commercial contracts and the other employment matters; a paralegal can run the checklist but should not be the only person to approve a liability cap.
A contract that arrives without a deadline is rare. Write the deadline at intake, because it determines how much review the contract can actually get.
Stage 2 — the clause review
The review itself should run in the same order every time. Order matters because clauses interact: an indemnity means something different depending on whether it sits inside or outside the liability cap.
| Clause | Question to answer |
|---|---|
| Parties and authority | Is the named entity correct, and is the signatory authorised? |
| Scope and deliverables | What exactly is being promised, and what is excluded? |
| Payment | Amount, timing, invoicing, late payment, set-off, expenses |
| Liability cap | Is there a cap, what does it cover, and what is carved out? |
| Indemnity | Who indemnifies whom, for what, and is it capped? |
| Termination | For cause, for convenience, cure periods, consequences |
| Renewal and notice | Auto-renewal, notice window, price adjustment on renewal |
| Confidentiality | Definition, duration, permitted disclosures, return of materials |
| Data protection | Roles, processing terms, breach notification, sub-processors |
| Assignment and change of control | Can the counterparty assign without consent? |
| Governing law and disputes | Which law, which forum, fees, arbitration or court |
| Boilerplate | Entire agreement, notices, severability, force majeure |
Not every clause needs a negotiation. The point of the table is that every clause gets a decision — accepted, negotiated, or flagged — rather than being skipped because the contract is long.
Two clause pairs deserve specific attention because they are where small firms most often accept risk by accident:
Liability cap and indemnity. A cap that applies to "all claims" but excludes indemnities can leave the firm exposed to an uncapped indemnity for a data breach or an IP claim. Read the two together and decide whether the carve-out is acceptable.
Auto-renewal and termination for convenience. A contract that renews automatically for twelve months, with a sixty-day notice window and no termination for convenience, is a one-year commitment that renews itself. If the firm cannot exit early, the renewal date becomes a board-level date even if the contract value is small.
Stage 3 — approval and signature
Approval should be a named person, not a consensus. Write down who can approve what:
- Standard terms, low value — office manager or paralegal prepares, lawyer approves.
- Non-standard liability, indemnity or data terms — lawyer with authority approves; consider insurer notification.
- Above a defined value or term — managing partner or owner approves.
The approval record can be simple: the reviewer's name, the date, the issues accepted, and the version approved. What matters is that the record points to the exact document that was signed. Version control failures are common when the final PDF is assembled from a draft that still contains a comment or a tracked change.
Stage 4 — the dates after signature
This is the stage most small firms skip, and it is the one that costs money. At signature, capture:
- Effective date
- End date
- Notice period
- Notice deadline (end date minus notice period)
- Renewal term and any price adjustment
- Owner — the person responsible for the relationship
- Location of the executed copy
Then diarise alerts at 90, 60 and 30 days before the notice deadline. Alerting on the end date is too late: by the time the end date arrives, the window to prevent renewal has usually closed.
A contract register can be a spreadsheet. It should be one register, not one per practice group, and it should be reviewed on a fixed cadence — monthly is enough for most firms.
Who does what in a small firm
The division of labour that works in a two-to-five-lawyer firm:
- Intake — whoever receives the contract logs it, tags the type and records the deadline.
- First pass — a paralegal or junior associate runs the clause table and marks issues.
- Judgment — a lawyer decides on liability, indemnity, termination and any non-standard term.
- Approval — the named approver signs off on the version that will be executed.
- Dates — the same person who files the executed copy records the renewal fields.
The critical rule is that the person who runs the checklist is not necessarily the person who approves the risk. Separating preparation from approval is what makes the process survive a busy week.
What to record, and why it matters
A contract file should let someone who was not involved answer four questions:
- What did we agree to?
- Who approved it, and on what basis?
- When does it end, and what do we have to do before then?
- Which version is the executed one?
Keep the executed contract, the mark-up, the approval note, and the dates record together. If the firm uses an e-signature platform, export the completed certificate of completion — it is evidence of who signed and when, which the platform's dashboard may not preserve indefinitely.
Common failure modes
- The inbox process. Contracts arrive in three places and one of them is never checked.
- Review by seniority rather than by checklist. The most senior person skims because they have seen it before; the clause that changed is missed.
- Approval by silence. Nobody objects, so the contract is treated as approved.
- The renewal surprise. Dates are captured in a calendar entry owned by someone who has left.
- The version that was signed. The final PDF differs from the approved draft.
- No record of accepted risk. The firm cannot show why a clause was allowed.
None of these require software to fix. They require one owner, one register, and a checklist that is short enough to actually be used.
Where software helps, and where it does not
Software is good at three things in this process: scanning a contract for the clauses on the checklist, storing the dates and sending alerts, and keeping a consistent record of what was reviewed.
It is bad at the judgment call. A tool can flag an indemnity; it cannot tell you whether the indemnity is acceptable for this client, this matter and this insurance policy. That decision stays with a lawyer.
The sensible split for a small firm is: use a checklist and a date tracker from day one, and add a clause scanner when the volume of contracts makes a first pass expensive. Do not buy a contract lifecycle platform to solve a problem that is really "nobody owns the register."
A one-page process you can adopt this week
- Create a single contracts inbox and a single register.
- At intake, record type, counterparty, deadline and owner.
- Run the twelve-clause table on every contract; mark each clause accepted, negotiated or flagged.
- Send anything with a non-standard liability, indemnity or data term to a named approver.
- At signature, record effective date, end date, notice period, notice deadline and owner.
- Set alerts at 90, 60 and 30 days before the notice deadline.
- File the executed copy, the mark-up and the approval note in one place.
- Review the register monthly and clear anything without an owner.
That is the whole process. It fits on a page, it survives a busy month, and it gives the firm something it rarely has: a defensible answer to "when did we agree to that, and who checked it?"
Frequently asked questions
What are the stages of a contract review process?
Four: intake and triage, clause-by-clause review against a fixed checklist, approval at the right authority level, and post-signature tracking of renewal and notice dates. A small firm can run all four with one owner and one shared record.
How long should a contract review take?
That depends on the contract, not the clock. A standard vendor agreement with familiar terms can be triaged in minutes; a non-standard indemnity or liability cap deserves a second reader. What matters is that the same checks run every time, so speed comes from familiarity rather than from skipping steps.
Does a small firm need contract review software?
Not necessarily. A checklist, a shared folder and a date tracker cover the process. Software helps when volume makes memory unreliable — particularly for clause checks and renewal dates, which are the two steps most often missed.
Who should review contracts at a small firm?
The person with authority over the risk being accepted. A paralegal can run the checklist and flag issues; a lawyer should decide on liability, indemnity and non-standard terms. The review record should name both the preparer and the approver.
What is the difference between contract review and contract management?
Review is the decision before signature. Management is what happens after: obligations, renewals, notice windows, amendments and the file that proves performance. Most small-firm failures happen in the second half, not the first.
LawFirmTools provides software tools only. Nothing here is legal advice, and LawFirmTools is not a lawyer or a law firm. This article is general information for legal professionals; it is not a substitute for professional judgment or for your state bar's rules.