Contracts that live in the system, not in a drawer.
The award is not the end of it. What was agreed, delivered, certified, still owed, and when it expires are held against the contract itself. Nothing depends on somebody remembering to look.
One record per agreement, and it knows its own dates.
A contract register is only useful if it is complete and current. This one is written by the award rather than typed up afterwards, so it is both.
- GeneratedThe contract is produced from the award and the region's clause rules — the parties, the values and the governing law are not retyped
- SignedE-signature on both sides, with the signed copy held against the record
- TrackedMilestones, obligations, retention and expiry, each with its own state
- AlertedA contract entering its renewal-notice window creates its own pipeline entry, with a start-by date. The missed renewal is the most preventable failure in procurement
From award to signature without leaving the record.
Everything the contract needs is already in the event that produced it, so the buyer's job is to check and issue rather than to assemble.
- SimpleGenerate the contract from the award, review the generated clauses and edit what your organisation needs to change
- ThenWhere contract reviews are switched on, record the legal, commercial and technical sign-offs against the record
- ThenSet milestones, obligations and retention so certification and payment have something to check against
- ComplexFlag an active contract as a standing arrangement and group it, so buyers call off agreed prices without re-tendering. Its own reviews clear first: until they do, nothing can be ordered under it, replenishment included
Pay against what was certified, not against what was invoiced.
A milestone contract is where three-way match usually breaks down. Here the milestone has to be achieved, then certified by somebody else, before it can be invoiced at all.
- GateA milestone cannot be certified by whoever achieved it — the system refuses and records the attempt
- ThenThe invoice is recorded against the certified milestone, and matched
- ThenApprove for payment, then record the payment with its reference
- ComplexRelease retention separately once the final obligation is met, rather than letting it quietly lapse in the supplier's favour
Sign it, then see what is expected of you.
The obligations are not buried in a PDF the supplier filed once. They are on the same screen they use to invoice.
- SimpleReview and e-sign the contract in the portal
- ThenSee the milestones, what has been certified, and what has been paid
- ThenSubmit invoices against the order or the milestone, not into an inbox
- ComplexKeep certifications and insurance current — they are chased before they lapse, and a lapse blocks an award
Nothing expires quietly.
Most contract value is lost at the end, not the start: an auto-renewal nobody reviewed, a re-tender begun too late to be competitive.
- SeesWhat expires when, and what is already inside its notice window
- DoesWorks the renewal entries the system created, with the start-by date calculated from the notice period
- SeesWhich agreements are standing arrangements, so repeat demand is called off rather than re-sourced
- ProofSpend under contract is measured, so 'more of it under contract' is a number rather than an intention
