Contract-as-Filing
The contract is signed, filed, and never actively managed. Payment runs on purchase orders, not contract terms.
The contract is signed, filed, and never actively managed. Payment is processed against purchase orders, not contract terms. Acceptance testing, warranty periods, escalation paths, and enforcement mechanisms exist in the contract but nobody drives them.
Recognition signals
- Nobody on the project team has read the full contract. They know the vendor name, the total value, and the broad scope. The clauses that protect the customer are unread.
- PO management operates independently of contract terms. Payment runs on purchase order schedules that don't align with contract milestones or acceptance gates.
- Finance processes payment on invoice receipt. The invoice arrives, it matches a PO, it gets paid. Nobody checks whether the underlying deliverable met contractual acceptance criteria.
- Team's first instinct is to email the vendor, not check the contract. When a delivery issue arises, the project team negotiates informally instead of referencing the contractual remedy.
- Vendor knows the contract better than the customer. They reference specific clauses in their favour. The customer's team reaches for "the spirit of the agreement."
Structural cause
Why this happens
Contract management is treated as a procurement function (signing) rather than a delivery function (enforcing). Once signed, procurement moves on to the next acquisition. The project team was not involved in negotiation and doesn't know what protections they have.
The procurement team negotiated the contract. They understood the clauses, the risk allocation, the acceptance framework, and the enforcement mechanisms. Then they handed the contract to a delivery team that had no involvement in the negotiation. The handover is a PDF and a brief. The delivery team files the PDF and starts managing the relationship — not the contract.
The vendor's team, by contrast, was briefed by their commercial and legal advisors on every clause. They know which obligations they can defer, which milestones trigger payment regardless of acceptance, and which escalation paths favour them. The information asymmetry isn't accidental — it's structural. One side manages the contract as a living commercial instrument. The other side filed it.
Risk mapping
| Risk | Description |
|---|---|
| P6 | Procurement capability fragmentation — contract knowledge doesn't transfer from procurement to delivery |
| CO2 | Competency gap — delivery team lacks contract management capability |
| G7 | Contract literacy gap — nobody on the delivery team understands the contractual protections available |
| CO1 | Leverage gap — contractual enforcement mechanisms exist but are never exercised |
Self-assessment
When to worry
- Nobody on the delivery team has read the full contract
- PO dates don't align with contract milestones
- When a delivery issue arises, the team emails the vendor instead of checking the contract
- No named contract manager — or the "contract manager" has never read the contract
When you're OK
- Key clause extract produced and briefed to the delivery team
- Payment workflow includes an acceptance gate tied to contract terms
- Contract performance data actively collected and reviewed
Related reading
- Acceptance Drift — payment decouples from acceptance when nobody is reading the contract
- Leverage Erosion — enforcement mechanisms that exist but are never exercised degrade over time
- Transition Cliff — contract knowledge is the first casualty at project boundaries
- The contract management gap — the missing role that turns contracts into filing
A contract you don't understand is a contract you can't enforce.
A contract management review extracts key clauses, maps them to delivery workflows, and identifies where enforcement mechanisms have atrophied. 10fifteen — programme governance assessments.