Contracts Management System
What does this contract require this month?
CMS governs contract operations after award, including obligations, deliverables, notices, variations, claims, payment certification and approval authority.
- 0
- Functional areas
- 0
- Claim stages
- 0
- Governed datasets
- 0
- User types

Contract obligations continue long after signature
CMS governs the operational registers of live contracts so obligations, claims, certification and related commercial positions can be answered from controlled records.
Obligations with evidence
Each obligation retains an owner, due date and discharge evidence. Overdue status is derived from the contract’s own dates rather than a manual status field.
Notices with deadlines
A served notice starts a response window. The dashboard shows which notices are past their response deadline and which contractual windows have already lapsed.
Claims governed through a defined lifecycle
A claim progresses through twelve recorded stages with settlement status retained at each stage. Transitions cannot bypass required lifecycle steps.
One live contract supported by eight governed registers
In CMS, the contract is the governing record linking obligations, claims, notices, certification and related commercial registers.
Contract value retained in its own currency unless an approved conversion basis exists
Active contracts, portfolio value, approaching expiries, overdue obligations and high or critical risks are reported together, with attention ordered by likely delivery impact.
Where portfolio value spans multiple currencies, CMS reports that position without applying unapproved conversion rates.
- Authority by currencyDelegated financial authority is evaluated in the contract’s own currency, so limits are not converted without an approved basis.
- Escalation thresholdA risk escalates when it reaches the configured category threshold, which is defined in contract settings rather than decided ad hoc.
- Close-out checklistOutstanding close-out activities must be verified before contract closure, and incomplete items remain visible.
CMS governs certification. Financial systems govern payment.
Budgets and commitments sit on the financial side, while payment applications and certification sit on the contractual side. The separation is deliberate because certification is a contractual act and payment is a financial transaction.
Differences between headline and underlying contract positions are explained through governed records such as applications awaiting certification, retained amounts and approved variations not yet reflected in the current commercial position.
Thirteen functional areas from intake through archive
CMS navigation covers intake, authoring, live contract management, performance, claims, renewal and close-out.
Origination and authoring
Requests enter through permission-controlled intake, are planned, and are drafted from governed clause and template libraries rather than copied from uncontrolled prior contracts.
- Requests
- Planning
- Clauses
- Knowledge
- Templates
- Authoring
- Review
- Approval
The live contract
The executed contract governs relationships and counterparties, notices and records, obligations and deliverables, and the evidence supporting contractual decisions.
- Contracts
- Relationships
- Relationship reviews
- Notices and records
- Obligations
- Deliverables
Commercial
Budgets, commitments, payment applications, certification and retention are each checked against delegated financial authority in the contract currency.
- Payment applications
- Commitments and budget
- Certification
- Retention
Performance
Key performance indicators and service levels are measured against contract requirements, with performance reviews and corrective actions recorded where required.
- Key performance indicators
- Service levels
- Performance reviews
- Corrective actions
Change and claims
Variations generate controlled amendments, claims follow a twelve-stage lifecycle, and risk, compliance and assurance registers span both processes.
- Variations
- Claims
- Risks
- Compliance
- Assurance
Close-out and reporting
Renewal and close-out include outstanding checklists, lessons learned, search, dashboards, reports and produced files required for contract reporting.
- Renewal and close-out
- Lessons Learned
- Search
- Saved searches
- Dashboards
- Reports
- Produced files
Every lifecycle transition is explicit and permission-controlled
Requests follow a governed intake lifecycle from draft through approval. Each transition records the authorised actor, due date and workflow state explicitly.
- Kind, category, contract type, priority and source recorded at intake
- Record version retained so prior states remain readable
- Approve, reject and return are distinct workflow outcomes with separate records


Templates use organisation-defined allowed values
Generated templates use organisation-defined reference values so imported data is validated against recognised values. Approvals, certificates, settlements and audit records are intentionally excluded from import because they must originate from governed decisions.
Authority evaluated in the contract currency
Delegated financial authority is evaluated separately for each currency, so authority in one currency is not assumed to apply to another without an approved basis.
Value retained in source currency unless conversion is approved
Where portfolio value spans multiple currencies, CMS reports that fact rather than applying an unapproved conversion.
Obligations carry evidence
Obligations are discharged against supporting evidence and verification. Overdue status is derived from contractual dates rather than manually entered status.
Append-only history
Tenant isolation and append-only record history preserve who approved each action and whether the actor had authority at the time.
More of what the application covers
- Clause and template library with approved language
- Notices with deadlines and acknowledgement
- Variations produce controlled contract amendments
- Retention held and released against certification
- Counterparty access restricted to authorised contract records
- Enterprise search with saved searches
- Scheduled execution of recurring checks
- Governed import, bulk update, migration and organisation extract
Contract governance connected to procurement and cost control
- PMSPMS: Procurement Management SystemPMS governs source-to-pay procurement and sealed tendering; CMS governs the contract created by award.
- CVMSCVMS: Contractor / Vendor Management SystemCVMS governs contractor and vendor assurance; CMS governs the contractual obligations associated with that relationship.
- BCMSBCMS: Budget & Cost Management SystemBCMS governs budgets, commitments, actuals and forecasts; CMS governs contractual certification and commercial entitlement.
- RMSRMS: Risk Management SystemRMS governs enterprise risk, while contract risks raised in CMS can reference the same control model.
Review CMS using one of your live contracts.
Bring one live contract. The demonstration will show upcoming obligations, active notices, claim status and the authority check supporting the latest certification.
