Contract Register Template (Supplier Contracts and Renewals)
Field definitions, risk tiers, worked register with notice deadlines and alert dates, key terms, renewal workflow, reconciliation checks
How to use: Use it to keep one list of every supplier contract with its end date, renewal type, notice deadline and owner. Fill the field definitions and risk tiers first, then compute notice deadline and alert date for each row. The main pitfall is click-through software subscriptions that never reach the register and renew silently.
Preview
Contract Register: [Organisation name]
Register of supplier contracts: parties, scope, term, renewal type, notice deadline, value, owner, risk tier and the documents that govern each relationship. Built from common contract management practice; it is the single place to answer "what have we signed, with whom, until when, and when must we act?". Replace every
[bracketed]value and every row marked Example. This is a documentation format, not legal advice: the signed contract always prevails over the register.
Document control
| Field | Value |
|---|---|
| Register ID | [REG-CTR-NNN] Example: REG-CTR-001 |
| Version | [1.0] |
| Owner | [@contract-manager] |
| Reviewers | [@head-of-procurement], [@legal-operations], [@financial-controller] |
| Scope | [Entities and contract types] Example: All supplier contracts of Corvanna Instruments Ltd, B.V. and Inc. above GBP 10,000 total value |
| Reconciliation | [Monthly against contract repository and ERP] |
| Last updated | YYYY-MM-DD |
| Classification | [Confidential] |
Revision history
| Version | Date | Author | Change summary |
|---|---|---|---|
| 0.1 | YYYY-MM-DD | [@name] | Register created |
| 1.0 | YYYY-MM-DD | [@name] | Example: Risk tiers added, alert lead time set to 60 days |
1. Purpose and scope
Every contract, order form, framework agreement, statement of work and amendment that commits the organisation to pay a supplier more than [GBP 10,000] over its term, or that involves personal data, system access or a critical service at any value, is entered within [5] working days of signature. Click-through and online subscription terms accepted by employees count as contracts.
2. Field definitions
| Field | Definition |
|---|---|
| Contract ID | Unique ID, format CTR-NNN; amendments keep the ID with a suffix (CTR-001-A1) |
| Supplier | Legal entity name as in the contract, plus supplier number from the ERP |
| Subject | One-line description of the goods or services |
| Category | Category from the category tree (procurement/category-strategy) |
| Contract type | Framework, supply agreement, master services agreement with SOW, subscription, licence, lease |
| Start date | Date obligations begin |
| End date | Last day of the current term |
| Renewal type | None (expires), automatic (with renewal period), option (by our notice) |
| Notice period | Days of written notice required to terminate or not renew, as stated in the contract |
| Notice deadline | End date minus notice period: the last day notice can be served |
| Alert date | Notice deadline minus the alert lead time |
| Annual value | Expected spend per year, excluding VAT or sales tax, in contract currency |
| Total contract value | Annual value multiplied by the term in years, plus committed one-off fees |
| Contract owner | Business person accountable for performance and the renewal decision |
| Risk tier | Tier 1, 2 or 3 (section 3) |
| Data and access | Personal data processed (yes or no), DPA reference, system access |
| Governing law | Law and jurisdiction clause |
| Key obligations | Service levels, price review, liability cap, exclusivity, minimum volume |
| Location | Link to the signed copy in the repository |
| Status | Draft, active, renewing, notice served, expired, terminated |
3. Risk tiers
| Tier | Rule | Review cadence |
|---|---|---|
| Tier 1 | Supplier failure would stop production, a customer-facing service or a regulated activity, or annual value above [GBP 1,000,000] | Quarterly performance review, renewal plan 12 months before end |
| Tier 2 | Supplier processes personal data or has system access, or annual value [GBP 250,000 to 1,000,000] | Half-yearly review, renewal plan 6 months before end |
| Tier 3 | All other registered contracts | Annual check, renewal plan 3 months before end |
4. Register
| Contract ID | Supplier | Subject | Start | End | Renewal | Notice (days) | Notice deadline | Alert date | Annual value | Total value | Owner | Tier | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CTR-001 (Example) | Ostrelby Castings Ltd | Machined and cast housings, supply agreement | 2025-04-01 | 2028-03-31 | None | 90 | 2028-01-01 | 2027-11-02 | GBP 2,950,000 | GBP 8,850,000 | [@ops-director] | 1 | Active |
| CTR-002 (Example) | Daskivo Electronics GmbH | Electronic components framework | 2024-07-01 | 2027-06-30 | Option, 12 months by our notice | 180 | 2027-01-01 | 2026-11-02 | GBP 5,300,000 | GBP 15,900,000 | [@supply-chain-director] | 1 | Renewing |
| CTR-003 (Example) | Brightwick Software Ltd | ERP cloud subscription | 2025-01-01 | 2027-12-31 | Automatic, 12 months | 90 | 2027-10-02 | 2027-08-03 | GBP 410,000 | GBP 1,230,000 | [@cio] | 2 | Active |
| CTR-004 (Example) | Lowmere Facility Services Ltd | Cleaning and facilities, all UK sites | 2026-02-01 | 2028-01-31 | Automatic, 12 months | 60 | 2027-12-02 | 2027-10-03 | GBP 265,000 | GBP 530,000 | [@facilities-manager] | 2 | Active |
| CTR-005 (Example) | Pellacourt Logistics B.V. | Inbound and outbound freight, EU | 2025-10-01 | 2027-09-30 | None | 90 | 2027-07-02 | 2027-05-03 | EUR 1,450,000 | EUR 2,900,000 | [@logistics-manager] | 1 | Active |
| CTR-006 (Example) | Quintrel Packaging Ltd | Packaging supply | 2023-11-01 | 2026-10-31 | Automatic, 12 months | 90 | 2026-08-02 | 2026-06-03 | GBP 720,000 | GBP 2,160,000 | [@ops-director] | 2 | Renewing |
Example notes:
- CTR-006: renewal was approved before the 2026-08-02 deadline, so the contract renews automatically for 2026-11-01 to 2027-10-31. The next notice deadline is 2027-08-02 (2027-10-31 minus 90 days) and the next alert date is 2027-06-03. Update the row on 2026-11-01. The total value shown is for the original 36-month term.
- CTR-002: the alert date (2026-11-02) is three days after "today". The owner must decide to exercise the option, re-tender or exit, and serve any notice by 2027-01-01. A 180-day notice period on a tier 1 framework leaves little time for a tender, which is why tier 1 renewal plans start 12 months before the end date.
- Committed annual value in GBP across CTR-001 to CTR-004 and CTR-006 is GBP 9,645,000, plus EUR 1,450,000 for CTR-005.
5. Key terms per contract
| Contract ID | Price review | Liability cap | Service levels | Termination for convenience | Data and access | Governing law |
|---|---|---|---|---|---|---|
| CTR-001 (Example) | Annual, metals index basket, cap 5% | 150% of annual charges | OTIF 95%, 750 PPM | Our side, 6 months' notice | None | England and Wales |
| CTR-002 (Example) | Quarterly, component index | 100% of annual charges | OTIF 97%, lead time 12 weeks | None | None | Germany |
| CTR-003 (Example) | Annual, CPI capped at 4% | 12 months' fees | 99.9% availability, see ops/service-level-agreement | None in term | Personal data, DPA-003, SSO access | England and Wales |
| CTR-005 (Example) | Fuel surcharge monthly | Carrier liability per convention, plus GBP 250,000 per event | On-time pick-up 98% | 3 months' notice | Shipment data | Netherlands |
6. Renewal and notice workflow
Notice is served in the form the contract requires (for example by letter to a named address), and proof of delivery is filed with the register entry.
7. Monitoring and reconciliation
| Check | Frequency | Owner |
|---|---|---|
| Suppliers with spend above [GBP 10,000] in the last 12 months and no register entry | Monthly | Contract manager |
| Contracts within 30 days of notice deadline without a recorded decision | Weekly | Head of procurement |
| Tier 1 contracts without an exit plan | Quarterly | Contract owners |
| Expired contracts still receiving purchase orders | Monthly | Accounts payable |
8. Glossary and references
| Term | Meaning |
|---|---|
| Evergreen contract | A contract that renews automatically without a fixed final end date |
| Notice deadline | Last day on which notice of non-renewal or termination can validly be served |
| Total contract value | All charges over the term, excluding tax |
| Exit plan | Steps to move a service to another supplier or in-house without disruption |
No statute or standard prescribes this register's format. Some
regulated firms must keep specific registers (for example EU financial
entities under DORA for ICT services, see
compliance/dora-ict-third-party-register, and banks under the EBA
non-ICT third-party guidelines, see
finance/third-party-risk-register-non-ict); use those templates for
the regulatory fields.
Standard and licence note
Based on common contract management practice; no standard text is reproduced. Notice and alert dates in the example are computed from the stated end dates and notice periods. Corvanna Instruments and all suppliers and figures are fictional. The register supports, and never replaces, reading the signed contract and legal advice. Template licence: MIT.
Related templates
Category Strategy Template (Spend Analysis, Kraljic Matrix)
Spend analysis, stakeholder requirements, supply market, Kraljic positioning chart, sourcing levers with savings, risks, roadmap, KPIs
ProcurementProcurement Policy Template (ISO 20400 Sustainable Procurement)
Thresholds, approval matrix, sourcing methods, single-source grounds, evaluation, sustainable procurement, ethics, public sector rules, KPIs
ProcurementPurchase Requisition and Purchase Order Template (Incoterms 2020)
Requisition with sourcing route and approvals, PO header and lines, delivery terms, Incoterms rule, key terms of purchase, error checklist