Direct answer
A contract register is a structured inventory of agreements and the information a team repeatedly needs to search, review, report, and act on, such as supplier, owner, status, value, sites, and key dates. A contract repository is the controlled place where the agreement and related source documents are stored or made accessible with useful metadata and permissions. The terms are sometimes used interchangeably, but operationally the strongest model connects the register record to the current source documents instead of forcing one to replace the other.
Register and repository compared
| Capability | Contract register | Contract repository |
|---|---|---|
| Primary purpose | Maintain a structured portfolio inventory | Store or expose the source contract documents in a controlled way |
| Typical content | Owner, supplier, status, value, sites, dates, review state, next action | Signed agreement, schedules, amendments, notices, supporting files |
| Search and reporting | Strong for filtering structured fields and portfolio questions | Strong for locating files and document metadata; full-text search may also help |
| Operational workflow | Can drive renewal, ownership, data-quality, task, and reporting queues | Provides the evidence and source context behind those workflows |
| Main risk when isolated | Rows become detached from the document that proves them | Files are findable but owners, dates, status, and next actions remain unclear |
How the two layers should work together
- 01
Create one contract identity
Give the agreement a clear record and reference that users can recognise across the portfolio and document layer.
- 02
Connect the current source set
Attach or reference the executed agreement and relevant amendments, schedules, notices, and approved supporting material.
- 03
Structure only the information you maintain
Record the supplier, owner, status, scope, value, dates, sites, and review fields that are repeatedly searched, reviewed, or reported.
- 04
Keep review and action attached
Use missing information, renewal timing, evidence, tasks, and decisions to update the same record rather than creating disconnected spreadsheets around the repository.
Questions to test your current setup
If you mainly have a register
- Can a user reach the current agreement and amendments from the record without knowing the folder structure?
- Can you tell which source supports a material date or value?
- Are superseded documents clearly distinguishable from the current source set?
If you mainly have a document repository
- Can you filter contracts by owner, supplier, site, status, expiry, notice, or review state?
- Can you see which records are missing critical information or have unowned actions?
- Can the team review upcoming renewal and follow-up work without opening files one by one?
Related resources