GroundWorks · Contract Lifecycle Management (CLM)
Every clause, control and obligation stays attached to its contract, with a named owner for each one.
Draft, review, approve and monitor contracts while preserving native document fidelity and human legal authority.
The Workblock
Contract Lifecycle Management (CLM) · GroundWorks Accord
- What changes beyond adding another contract assistant?
- Contract lifecycle system of work
- 1 reference / 1 defined / 3 roadmap
Modules
- Contract data capture and extraction: Capture the contract set, extract terms and metadata with source anchors, resolve agreement identity and route evidence exceptions.
- Contract drafting, negotiation and redlining: Draft and compare clauses, present labelled changes and preserve native DOCX fidelity.
- Contract approval, execution and storage: Assemble approval evidence, bind approval to the exact version, coordinate authorised signature and reconcile the executed agreement to canonical storage.
- Obligation and performance management: Extract agreed obligations into owned records and monitor dates, exceptions and follow-through.
- Renewal, change and compliance: Prepare renewal, renegotiation, amendment, termination and compliance cases from current contract, consumption and performance evidence.
The question, answered
After signature the pattern repeats. Dates and obligations are extracted or keyed in, and owners receive alerts. An alert says a deadline is near. It does not carry the clause, the trigger event, the evidence rule or the authority to close the case. So the contract manager rereads the agreement, chases the service owner and reconciles what an invoice, a performance report or an amendment means for the rights the organisation holds.
The cost lands between systems. A document change does not reopen the approvals it affects. Fulfilment evidence sits in ERP and service systems while closure stays manual. A notice window is discovered after the right has lapsed. None of this is a missing feature in the contract system: it is the work that happens after the repository and before the decision.
What changes beyond adding another contract assistant?
The contract system already extracts clauses and sends reminders. Yet when third-party paper arrives, a reviewer still rebuilds the case by hand: the award context from sourcing, the playbook version that applies, the definition two schedules away that changes a clause's meaning. The findings travel into an approval pack by copy and paste, and the exact language and version stay behind.
What changes
Each material clause arrives as a decision: the exact language, the position it departs from, the options and the reviewer whose authority it needs, with uncertainty stated rather than smoothed over.
Executed language becomes owned cases. A renewal arrives as a decision with the clause, the notice deadline, the performance history and a named owner, before the window closes.
Findings become decisions
A contract is uploaded and a long machine summary comes back: risks, observations and suggested language, hard to verify and structured around nothing in particular.
From repository to active obligations
Executed contracts sit in a repository with reminders. A notification says a contract is about to expire; someone rereads it, works out what it means and chases the owner.
The principles it holds to
The document stays the document
Contract review happens in the native DOCX through Composer: comparison, comments and tracked changes survive the round trip, and nothing is flattened into platform-only fields. The immutable original, the working copy and the executed copy remain distinct artifacts.
A proposal is not a position
Machine-drafted language stays visibly proposed, with its source and playbook basis attached, until the named owner accepts, edits or rejects it. Approval binds to one exact version and reopens when the document materially changes. Approved for signature is not executed: only the authorised signatory commits the organisation.
Obligations become owned cases
Executed language creates cases that carry the source clause, the trigger, the due logic and the evidence rule, with an owner who has accepted the duty. Evidence submitted is not evidence accepted: the named authority closes a material case, and a disputed one stays open until it does.
The records it authors
Contract change. A governed renewal, amendment, notice, waiver or termination case that moves from proposal to an effective contractual outcome.
Contract compliance finding. A variance linking contracted rights or duties to the observed transactions, performance or conduct that differs from them.
Contract intake. A governed request to ingest, classify and establish the authoritative source set for an agreement before drafting or review begins.
Clause deviation. A source-anchored difference between contractual language and a versioned playbook position, including risk, rationale and resolution.
Contract approval. An authority-bound decision and, where applicable, signature execution record for an exact contract content hash.
Contract entitlement. A contractual right, credit, rebate, remedy, option or concession that may be exercised or recovered.
Clause library entry. An approved, reusable and versioned clause position with exact text, applicability, jurisdiction, policy provenance and semantic tags independent of any one agreement.
Contract. The canonical agreement identity and lifecycle header, distinct from each immutable contractual version and its source artifacts.
Contract template. A reusable, approved and content-addressed agreement template whose applicability, effective period and source artifact are governed independently of any individual contract version.
Contract version. An immutable, content-addressed version of an agreement with its structured terms, source artifact and approval provenance.
Contract obligation. A party-owned contractual duty with source anchoring, due logic, evidence requirements and fulfilment state.
Case records
Durable, owned units of work. Each one holds the condition that opened it, the evidence gathered against it, the proposed action and the committed disposition, and it stays open until the condition is answered.
Decision records
Determinations and the proposals that precede them, each pinned to the exact policy, rule and evidence versions it was made against, and each kept structurally distinct from the action it authorises.
Transaction records
The commercial substance itself, canonical and versioned down to the line, with source provenance preserved beside the platform's own processing state.
Document records
Authored and received artefacts, kept at native fidelity as immutable versions, so the extracted terms never displace the thing they were extracted from.
Control records
The governed rules, grants and pre-commitment assessments that bound what may be committed, on which records and by whom.
The roles it serves
Execution flow and task definitions are not published. The dossiers name what each Workblock owns and how much of it there is; the definitions themselves travel with a delivery.
Workblocks can be versioned and changed independently, enabling continuous client tailoring.
Contract manager
Own the contract lifecycle from request to closed obligations: routing, repository quality, milestones and cross-functional follow-through. Which contracts are waiting on a decision, and what does each one need before it can move?
Legal counsel
Interpret legal effect and protect the organisation's legal position on every material deviation. Which clauses actually need my judgement, and is the evidence behind each finding complete?
Sourcing manager
Carry the awarded commercial position into the executed agreement. Does this paper still hold the price, service and risk position we won?
Obligation owner
Perform or coordinate a contractual duty, or exercise a right, and prove it happened. What exactly must I do, by when, and what evidence closes it?
Category manager
Own the commercial outcome of a category across its contracts. Which contracts in my category are about to change what I can commit to?
Module maturity
1 reference / 1 defined / 3 roadmap, of this Workblock's five business modules.
The rest of the register
- Previous
Sourcing & Negotiation
Sourcing decisions you can defend line by line: every score opens the response behind it.
Open the Workblock - The map
The GroundWorks map
Five stages and nine domain Workblocks, summarised once, each linked to the register page that holds it.
Back to the map - Next
Supplier & Third-Party Risk Management (TPRM)
Every risk decision has an owner, a case file and a proportionate response.
Open the Workblock