What this is
What is a contract review record?
What is a contract review record?
It checks an agreement before it renews: whether service was delivered as agreed, whether pricing still holds up, what obligations are or are not being met, and what risks are concentrated before the business commits to another term. It ends in a decision — renew as is, renegotiate, retender, or terminate.
What is the difference between the notice deadline and the expiry date?
The expiry date is when the contract ends; the notice deadline is the last date a party can act to stop it renewing on current terms. A review held before expiry but after notice is a review with nothing left to change, which is why Held Before The Notice Deadline is scored, not a comparison against expiry.
Why is Single Source Dependency asked separately from Alternative Suppliers Identified?
Dependency describes the exposure as it stands; alternatives describe whether anything has been done about it. A contract can carry a genuine dependency and still show alternatives identified only on paper, so the two need reading together, not collapsed into one score.
Scope
When is a contract review record required?
This review is one step ahead of a renewal decision. Using it to hold work that belongs to the register or scorecard produces a record that duplicates data it should only link to.
Use this template when
- A notice deadline is approaching and the agreement needs reviewing before the window to act closes
- A trigger event, such as a performance failure or a change in the counterparty's ownership, calls for an off-cycle review
- The workspace is being set up and this singleton review needs creating for an active agreement
- A linked record needs this one to exist: the Contract Register entry it updates, or the Vendor Scorecard it draws on
- A renewal decision needs a documented basis before it is presented for sign-off
Do not use it for
- Contract Register, which holds every commercial agreement, its value, term, renewal date and owner as a standing list, not a point-in-time judgement
- Purchase Requisition Record, which requests a purchase and routes it for approval, a decision made before an agreement exists
- Rate Confirmation Record, which confirms an agreed rate and terms for a specific load or lane, not the standing relationship this record reviews
- Vendor Scorecard, which tracks ongoing supplier performance over time; this review reads that scorecard rather than re-scoring from scratch
- Anything outside KnowLogistics, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 9001 cl.8.2 requirements does this satisfy?
ISO 9001 treats an ongoing agreement as a live requirement, not a signed document filed away: requirements have to be reviewed, external providers controlled in proportion to their impact, and risks to conformity addressed. This record is where that review happens, contract by contract.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.2 | Review requirements related to products and services, including obligations under an existing agreement, before committing to its continuation | Terms |
| ISO 9001 cl.8.4 | Determine and apply controls over externally provided services proportionate to their impact on conforming product or service | Performance |
| ISO 9001 cl.9.1 | Monitor, measure and evaluate the performance of external providers against agreed criteria | Performance |
| ISO 9001 cl.6.1 | Determine and address risks that could affect the ability to meet requirements, including dependency on a single supplier | Risk |
| ISO 9001 cl.8.4 | Reassess the extent of control required where continuity risk or exposure is identified | Risk |
| ISO 9001 cl.10.2 | Raise and track corrective action where the review finds a nonconformity against contract obligations | Outcome |
| ISO 9001 cl.4.2 | Requirements of interested parties change over time, which the renew, renegotiate, retender or terminate decision must test rather than assume | Outcome |
What it does not cover
- Held Before The Notice Deadline marked Yes because a meeting happened, not because time remained to act on what it found, which turns a genuine deadline into cover for a renewal already effectively locked in.
- Scorecard Reviewed ticked Yes without the Vendor Scorecard actually being opened, which lets Service Delivered As Agreed get answered from memory rather than checked against the record it should be checked against.
- Single Source Dependency answered No because the question was never really tested against the market, which hides an exposure that only becomes visible the day the supplier can no longer deliver.
- Decision recorded as Renew As Is with the Reason field left blank, which leaves the next reviewer unable to tell whether that was a considered call or simply the option nobody challenged.
- Auto Renews left unanswered, or answered from memory rather than the contract wording, which is exactly the term that turns a missed notice deadline into an unwanted extra year on the current price and obligations.
Global
Contract Review Record requirements by country
Contract review sits where commercial risk meets specific legal duty. Three fields on this record each carry an external obligation a soft internal miss would not.
GDPR, article 28
Where a counterparty processes personal data on the organisation's behalf, specific contractual clauses covering scope, security and sub-processing are mandatory, not optional good practice.
Data Or IP Exposure answered Yes is the trigger to check whether the required processor clauses actually exist, not a soft risk note to file and move past.
Modern Slavery Act 2015, s.54
Larger organisations must publish an annual statement on steps taken against slavery and trafficking in their supply chains, requiring ongoing evidence, not a one-off attestation.
Ethical And Labour Risk Reviewed is where that ongoing evidence should live for a standing supplier, review by review.
Uniform Commercial Code, article 2
Absent a valid termination performed strictly under the contract's own notice terms, default UCC rules on renewal can leave a relationship the business believed was ending still legally in force.
Notice Served Where Needed is a matter of enforceability: an unrecorded or late notice can mean the termination the Decision field states never took legal effect.
How to complete it
How to complete a contract review record, step by step
Every field can carry an answer and the review can still miss the point, because the value sits in judgement calls the fields do not settle on their own.
Most Performance, Terms and Risk fields carry a genuine N/A option, and a materials-only contract with no service levels or data handling can legitimately use it. The judgement call is telling that apart from an N/A used to dodge a No that would drag the score down.
The header's Info field exists because expiry is the easier date to hit and notice is the one with consequences. A review two weeks before expiry, after notice has passed, satisfies neither the field's intent nor the point of running the review at all.
One Poor in Value For Money or one Yes in Single Source Dependency is a different situation from a pattern across Terms and Risk together. Deciding in advance what forces Renegotiate or Retender keeps Decision a judgement rather than a habit.
Register Updated should confirm the Contract Register now reflects this review's outcome. Answered before the Decision is finalised, it confirms only that the register was touched, and the record can close showing a state the register does not yet carry.
What auditors find
Most common contract review record findings
Findings cluster around fields answered independently when they were meant to be read together, and dates recorded without evidence they were acted on.
| Finding | Clause | What fixes it |
|---|---|---|
| Auto Renews answered Yes with no cross-check against Held Before The Notice Deadline on the same record. | ISO 9001 cl.8.2 | Treat Held Before The Notice Deadline as a hard gate whenever Auto Renews is Yes, not an independent score. |
| Scorecard Reviewed marked Yes with no Scorecard ID captured until Outcome, after Performance is already answered. | ISO 9001 cl.9.1 | Require the Scorecard ID before Service Delivered As Agreed and Scorecard Reviewed can be completed. |
| Single Source Dependency and Alternative Suppliers Identified answered without reference to each other. | ISO 9001 cl.6.1 | Capture the named alternative supplier whenever Alternative Suppliers Identified is Yes. |
| Data Or IP Exposure assessed without reference to what the counterparty actually processes under the agreement. | GDPR art.28 | Require a short description of the data or IP in scope before Data Or IP Exposure can be answered. |
| Notice Served Where Needed marked Yes with no date or method recorded. | ISO 9001 cl.8.2 | Add a served-on date tied to the existing Notice Deadline field so the record shows timing, not just a Yes. |
| Action Required marked No on a record where Value For Money reads Poor and Obligations We Are Not Meeting reads Yes. | ISO 9001 cl.10.2 | Force Action Required to Yes whenever Value For Money is Poor or Obligations We Are Not Meeting is Yes. |
Case in point
Case in point: the contract that renewed itself twice
A distribution contract carried a ninety-day notice period against a rolling annual term, with Auto Renews correctly recorded as Yes at onboarding. The first review, held six weeks before expiry, found the relationship working well and closed as Renew As Is. Nobody noticed six weeks before expiry was three weeks after the notice deadline had already passed, so the review had confirmed a decision the contract had already made on its own. The second year, pricing had moved against the business and a cheaper alternative had entered the market, but notice was again missed, by a wider margin, because the review was scheduled against the invoice renewal date rather than the notice date in the agreement.
The fix was not a new field. Held Before The Notice Deadline and Notice Deadline already existed; what was missing was treating Auto Renews as the trigger that made the notice date, not expiry, the one the review had to beat, and diarising the review against it directly.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- LOG-033
- Archetype
- Review
- Record ID
- CREV-2026-000
- Scoring
- Reviews before notice
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.8.2
- Links
- Links Contract Register and Vendor Scorecard
- Tags
- Contract, Review
- Sections
- 5
- Fields
- 50
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 5
Header
18 fieldsReview ID*
Auto sequence. Format CREV-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Counterparty*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Agreement Title*
Register ID
Links to LOG-032 Register ID
Contract Owner*
Notice Deadline*
Review Held*
Held Before The Notice Deadline*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Annual Value
Years In Place
Auto Renews*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Before The Notice Date, Not The Expiry Date
A review held two weeks before expiry is a review with no options left. The only useful date is the notice deadline, which is usually months earlier.
Performance
6 fieldsService Delivered As Agreed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Scorecard Reviewed*
- Yes3 pts
- No0 pts
Failures Documented*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Escalations Handled Well*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Relationship Working*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Value For Money*
- Good3 pts
- Acceptable2 pts
- Poor0 pts
Terms
6 fieldsPricing Benchmarked*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Obligations We Accepted Reviewed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Obligations We Are Not Meeting*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Liability And Indemnity Reviewed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Termination Rights Understood*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Insurance Requirements Current*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Risk
6 fieldsSingle Source Dependency*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Switching Cost Understood*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Alternative Suppliers Identified*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Continuity Plan If They Fail*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Data Or IP Exposure*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Ethical And Labour Risk Reviewed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Outcome
14 fieldsDecision*
Renew as is, renegotiate, retender, or terminate.
Reason
Action Required By*
Notice Served Where Needed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Scorecard ID
Links to QUA-041 Scorecard ID
Register Updated*
- Yes3 pts
- No0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Contract Owner*
Signature*
Commercial*
Second Signature*
LOG-033 · record IDs look like CREV-2026-000 · Links Contract Register and Vendor Scorecard
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The review itself is one meeting. Tracking the notice deadline, chasing scorecard evidence before Performance gets answered, and keeping the register in step with the decision is the work that actually slips.
Tracks notice deadlines against Auto Renews across every active agreement, and flags a review scheduled against the wrong date before it becomes a missed window.
Rolls Action Required and CAPA references into the wider compliance picture, so an unmet obligation reaches management review as a tracked item, not a note in a closed record.
Watches Single Source Dependency and Continuity Plan If They Fail across the contract book, so unmanaged supply risk is visible before a renewal decision is made under pressure.
Coordinates the crew, surfaces reviews approaching their notice deadline, and holds every write for your approval before it touches the record or the register.
This template lives in KnowLogistics — supply chain execution. Inbound, outbound, inventory, yard, claims, supplier lifecycle and customs.
Glossary
Contract Review Record definitions and key terms
- Notice deadline
- The last date a party must act, under the contract's own terms, to stop an agreement renewing or ending on its current basis. Distinct from the expiry date, when the term simply runs out.
- Auto-renewal
- A contract term under which the agreement continues automatically unless one party gives notice by the deadline. It converts a missed review into a locked-in outcome.
- Vendor scorecard
- The standing record of a supplier's ongoing performance over time. This review reads it as evidence rather than re-deriving performance from scratch.
- Single source dependency
- A state in which no realistic alternative supplier exists for a good or service, so continuity depends entirely on one counterparty's ability to keep delivering.
- CAPA
- Corrective and preventive action. The reference raised and tracked when Action Required is Yes, linking this review to where the fix is actually managed.
FAQ
Frequently asked questions about contract review record
How is a contract review record different from the Contract Register?+
The register is a standing list of every agreement, its value, term and owner. This record is a point-in-time judgement on one agreement, run ahead of its notice deadline, that feeds an update back into the register rather than replacing it.
What is the difference between Held Before The Notice Deadline and a review held before expiry?+
Only the notice deadline leaves options open. A review held after notice has passed but before expiry may look timely on the calendar while having no practical ability to change the renewal outcome.
Why does Auto Renews matter if the review is happening anyway?+
It decides what a missed notice deadline actually costs. On a contract that does not auto-renew, a late review is administrative. On one that does, a late review means the current terms continue by default, whatever the review concludes.
What should trigger an off-cycle review instead of waiting for the notice deadline?+
A performance failure, a documented risk change such as a new single-source dependency, or a change in the counterparty's ownership. Waiting for the scheduled cycle then defers a decision the business may not be able to afford to defer.
Does a Decision of Renew As Is need a Reason?+
It should. Reason is not marked required on the field itself, but an unreasoned Renew As Is is indistinguishable from a review nobody engaged with, the exact failure mode this record exists to prevent.
Can the scoring on this template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to the register and scorecard travel with it. Most teams install it as it is, run it against a handful of agreements, then adjust.
Keep going
Related templates and programmes
Industries this is written for
More in Contracts and Commercial
Contract Register
Holds every commercial agreement, its value, term, renewal date and owner
Purchase Requisition Record
Requests a purchase, states the justification and routes it for the right level of approval
Rate Confirmation Record
Confirms the agreed rate, accessorials and terms for a load or a lane in writing before the vehicle moves
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 clause 8.2, requirements for products and services
- ISO 9001:2015 clause 8.4, control of externally provided processes, products and services
- ISO 9001:2015 clause 6.1, actions to address risks and opportunities
- GDPR (Regulation (EU) 2016/679), article 28, processor
- Modern Slavery Act 2015, section 54 (UK)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.