Contracts
Contract management software and contract repository
Contract management software keeps every agreement, its metadata and its history in one place so obligations do not depend on someone remembering them. DocumentMS extracts counterparty, value, term and renewal date into searchable fields, routes drafts for approval, captures signature, then reminds you before each renewal.
What goes wrong without a contract repository
Almost every organisation can produce a signed contract if you give them a week. The problem is not storage — it is that the obligations inside the contract are invisible. A renewal date, a notice period, an indexation clause and a liability cap exist as sentences in a PDF, which means nobody can answer "which agreements renew next quarter" without opening them one at a time.
The predictable consequence is renewal by inattention. A three-year agreement with a ninety-day notice period auto-renews because the notice window passed unnoticed, and the organisation discovers it has committed to another term at a price it would not have accepted. That failure is not a legal one; it is a retrieval one.
The second failure is version confusion at signature. Someone negotiates from a copy that predates a clause change, and the signed agreement contains a liability position the legal team thought had been retired eighteen months earlier. Both failures are solved by the same thing: making the facts about a contract into data, and generating from a controlled template.
The symptoms you will recognise
- A spreadsheet tracking renewal dates that is maintained separately from the contracts themselves, and is out of date
- Nobody able to say how many active agreements exist with a given supplier
- Agreements signed from a template copy that predates the current approved clause set
- A renewal discovered after the notice window closed
- Amendments filed separately from the agreements they amend
- The signed copy held in someone’s email rather than in a repository
Configuration
Folder structure
Counterparties
- Counterparty / agreement
- Amendments and variations
- Notices given and received
- Correspondence during term
Templates and clauses
- Approved agreement templates (controlled)
- Clause library with approval status
- Fallback positions and playbooks
In negotiation
- Drafts under negotiation
- Redlines received
- Approval requests
Expired and terminated
- Expired agreements pending retention expiry
- Termination correspondence
Configuration
Metadata that turns a contract into data
| Field | Type | Mandatory | Why it exists |
|---|---|---|---|
| Counterparty | Text | Mandatory | The primary retrieval key. Without it the repository is a folder of PDFs. |
| Agreement type | Single-select | Mandatory | Drives the retention rule and the approval chain the draft has to clear. |
| Commencement date | Date | Mandatory | Establishes the term and, with it, every date derived from it. |
| Expiry or renewal date | Date | Mandatory | The field the whole use case exists for. Reported on before it arrives, not after. |
| Notice period | Number (days) | Mandatory | The renewal date minus the notice period is the date that actually matters. |
| Contract value | Currency | Mandatory | Determines the approval threshold and supports spend reporting by counterparty. |
| Governing law | Single-select | Optional | Needed when a dispute arises, and much harder to establish retrospectively. |
| Auto-renewal | Yes / no | Mandatory | Separates agreements that lapse safely from those that commit you by default. |
| Owner | User | Mandatory | Someone has to receive the renewal task. An unowned contract is an unmanaged one. |
Configuration
Approval chain
Step 1: Draft from an approved template
The draft is generated from the current approved template, so a retired clause cannot be reintroduced. The template version used is recorded against the draft.
Step 2: Commercial review
The owner and, above a configured value, a budget holder approve the commercial terms. Value is read from metadata, so the threshold applies automatically.
Step 3: Legal review where triggered
Legal review is required when the agreement type, governing law or a departure from the playbook triggers it — not on every agreement, which is how legal review becomes a bottleneck.
Step 4: Signature and filing
A signature request goes to both parties, and the signed output is filed as a new version of the record with its request history, ready for renewal reporting.
Configuration
Retention rule
What starts the clock
The trigger is expiry or termination, not commencement or signature. A schedule that starts the clock at signature disposes of the agreement while claims under it are still possible — and for a five-year term with a six-year retention period, that is a five-year error.
Outcomes
What changes
- Renewals are surfaced before the notice window closes, because the reported date is renewal minus notice period rather than renewal
- A question about exposure to one counterparty is answered from a filter instead of a canvass
- Signed agreements cannot contain a retired clause, because drafts are generated from the current approved template
- Amendments stay attached to their parent agreement, so the operative terms are the assembled set rather than the newest file
- The contract owner is a named person who receives the task, rather than an assumption
FAQ
Contract management: common questions
Is this a contract lifecycle management (CLM) product?
Not in the sense of an in-document negotiation and clause-comparison suite. DocumentMS covers the parts most organisations are actually failing at: a controlled repository, extracted terms as reportable metadata, generation from an approved template, threshold-driven approval, signature and retention. If your bottleneck is redline negotiation across many counsel, a dedicated CLM will serve you better.
How accurate is automatic extraction of renewal dates?
Good enough to propose, not good enough to trust silently — which is why extraction presents the value with the source passage it came from and requires confirmation. A renewal date nobody verified is worse than one nobody extracted, because it will be relied on.
What is the single most important field to make mandatory?
Notice period, together with renewal date. The date that matters operationally is renewal minus notice, and organisations that capture only the renewal date still miss windows — they just miss them with better data.
When should the retention clock start?
At expiry or termination, not at signature. This is the most common misconfiguration in contract retention: with a five-year term and a six-year period, a signature-triggered clock disposes of the agreement five years early, while claims under it are still live.
Can we keep negotiating in Word?
Yes, and you should. Documents open directly in Word and save back as new versions, with the draft checked out while it is open. What changes is that the version history and the approval record live in the repository rather than in an email thread.
Última revisión: 2026-09-01. See all seven use cases.