Finance knows what you pay the supplier. Operations knows who uses the service. Nobody is certain where the signed order form went or whether the contract renews automatically.
A contract register is a structured record of the agreements your business has signed. Each record connects the agreement to its documents, owner, financial commitment, key dates and source clauses. Start with the fields needed for decisions, mark uncertainty clearly and keep the record current when terms or owners change.
For a small team, a spreadsheet can be a useful starting point. The important part is whether someone can trace a field back to the agreement and act on it. A neat list of dates without documents or owners is difficult to trust.
Download the template and choose where it lives
Use the contract-workflow workbook in Excel. For Google Sheets, import the workbook or start with the contract-register CSV. The downloads contain fictional examples and blank entry rows; they contain no customer documents or macros.
The workbook separates contracts, renewal decisions, obligations, review briefs and founder events. Use the sheets you need. The register links agreements to the other records through a contract ID, so one agreement can have several obligations without being duplicated in the main list.
Keep the working file in a location with appropriate access controls. Do not upload signed agreements to a public spreadsheet. Contract documents can contain personal data, confidential commercial information and security details.
Decide what one record represents
Use one contract ID for a defined agreement set. Identify the executed agreement, order form and applicable schedules. Attach amendments to the same set when they change it, preserving their dates and history.
One vendor can have several separate agreements. A software provider may supply two products under distinct orders with different terms. Do not compress them into a single row if that loses separate obligations or deadlines.
If a new agreement replaces an old one, link the records and mark the earlier agreement's status after checking the effect. Do not delete the earlier documents merely because a new proposal exists.
Keep the core fields useful
| Field | Why it belongs in the register |
|---|---|
| Contract ID and name | Gives related documents and tasks a stable reference |
| Contracting entities | Identifies the actual parties, not only their brand names |
| Contract type and your side | Helps the next reader interpret the terms |
| Owner and backup | Identifies who must decide or follow up |
| Status | Distinguishes proposed, active, expired and otherwise closed records |
| Executed documents and amendments | Shows what supports the current agreement |
| Value, currency and billing basis | Makes the financial commitment interpretable |
| Effective, term-end and renewal dates | Identifies the agreement's timing |
| Notice period and action deadline | Shows when a decision may need to happen |
| Source clauses and verification status | Makes checked facts distinguishable from assumptions |
| Next action and review date | Turns the record into useful work |
Do not require every contract to have every date. Some agreements do not have automatic renewal. Record “not applicable” when you have checked the terms; leave a field “unconfirmed” when you have not. Those states mean different things.
Use unambiguous dates such as 2027-04-02 and record a time zone if the agreement makes time relevant. Retain the wording of the notice requirement alongside the calculated date.
Complete one record from the source documents
Here is a fictional example used throughout these guides:
| Field | Example |
|---|---|
| Contract ID | CT-001 |
| Contract name | Harbor Analytics annual subscription |
| Our side | Customer |
| Owner / backup | COO / finance lead |
| Annual fee | €12,000; fictional amount before tax |
| Status | Active in this example |
| Renewal | 1 July 2027 |
| Notice | Supplier receipt at least 90 calendar days before renewal |
| Illustrative notice deadline | 2 April 2027, under the stated example assumptions |
| Internal review | 3 March 2027 |
| Documents | Executed service agreement, order form, DPA and security schedule |
| Source | Agreement sections 7.2 and 14; order form checked |
The renewal-deadline guide explains the example and its assumptions. Do not transfer those dates or notice terms to your agreement. Check its own wording and amendments.
In the actual register, document references should lead to the signed files. Store access-sensitive records in the appropriate restricted location, rather than copying every clause or personal detail into a widely shared sheet.
Keep agreement facts separate from tasks
The main register says what the agreement is and where its terms are recorded. The renewal sheet records a decision process. The obligation sheet records what each party must do.
For CT-001, the register can identify the annual subscription and the executed documents. A linked renewal record can show who is deciding whether to continue. Several linked obligation records can cover an invoice, a service report and a deletion task after an eventual exit.
Avoid a single cell containing “pay, renew, check security and delete data.” Each action can have a different owner, trigger and completion evidence. Use the obligation-tracking guide to separate them.
Mark uncertain information before it becomes authoritative
When importing an old spreadsheet, keep each questionable field visible. You may have an invoice date but no signed order form, or an expiry date copied from a previous renewal.
Record the missing source, the person responsible for checking it and the next action. Prioritise contracts approaching a decision deadline and agreements supporting critical services. Do not fill blank notice periods with a standard number to make the sheet look complete.
If you use extracted or AI-generated information, treat it as a candidate until checked against the source. Record the amendment and clause that establish the current term. A precise date with no evidence is still uncertain.
Update the register when the business changes
Update a record when an agreement is executed, an amendment is signed, a renewal is agreed, an owner changes or a relevant notice is given. Preserve what changed and which document supports it.
During a regular review, check upcoming action deadlines, records without owners, missing executed documents and unresolved fields. Ask each owner for a decision or a specific next action. Use the cadence your team can maintain rather than adding fields nobody will revisit.
For personal data in the register, consider what is necessary, accurate and appropriately protected. GDPR Article 5 sets out principles including data minimisation, accuracy and storage limitation; it does not prescribe a universal retention period for every contract. Choose retention and access with the relevant obligations in mind.
When a spreadsheet needs more support
A spreadsheet may remain sufficient if the document links work, owners maintain it and deadlines are acted on. Review the arrangement when amendments are frequently missed, people maintain conflicting copies or reminders no longer lead to a decision.
Evaluate software using a real signed agreement. Can you locate its executed documents, trace a date to the source, keep amendments connected and see who owns the next action? Ask what happens to records when you export or leave. Avoid treating a long feature list as proof that your process will work.
Put one signed agreement into the register
Choose a contract your team is already managing. Add its executed documents, owner, checked dates and next action. Then see Outlex Contract Review if the terms need a closer review before the next decision.
This guide is general information, not legal advice. The template is a working record, not a compliance certificate, legal interpretation or substitute for the signed agreement.
