Framework Contracts Fail on Alignment, Not on Clauses
Why operations, maintenance and procurement need a joint plan before going to market.
An industrial site has worked with the same maintenance contractor for years. When the framework contract comes up for renewal, it is extended with minor changes, because there is no time to do it differently. Meanwhile maintenance and procurement talk past each other: maintenance knows what the contractor does well and where it falls short, procurement manages the contract, and neither fully knows what the other needs. The new contract period starts with the same frustrations as the last one.
- A good framework contract has support across operations, maintenance and procurement, and is built on aligned work processes.
- Most efficiency is gained by aligning preventive and corrective work, priorities and cross-discipline planning.
- Scope and pricing follow from a joint plan: known routine work on unit rates or fixed prices, unplanned work on a reimbursable basis with clear controls.
Three Parties, Three Perspectives
A maintenance framework contract rarely fails because of the document itself. It fails because the parties behind it are not aligned. In most industrial organisations three parties are involved, each with its own role and perspective.
A good framework contract has support across all relevant departments, with work processes that are aligned between them. That sounds obvious, yet in practice the alignment of needs, planning and performance feedback is where most contracts fall short.
Where It Usually Goes Wrong
- Needs and planning are not aligned. Operations, maintenance and procurement each work from their own priorities, and the contractor receives mixed signals.
- Preventive and corrective work compete. Without clear priorities between planned and unplanned work, crews are pulled from one job to the next and efficiency is lost. This is where I most often see room for improvement.
- Cross-discipline checks are missing. Work in one discipline affects another. The classic example: resurfacing a road before the sewer underneath has been replaced. Without a check across disciplines, work is done twice or delayed.
- Performance feedback is informal or absent. Experience with the contractor stays with the people on site and never reaches the contract.
A Joint Plan as the Basis for the Contract
Procurement is well placed to bring the three parties together and draw up a joint plan before going to market. That plan defines the scope, the planning principles and, importantly, how each type of work will be paid for.
| Type of work | Pricing model | Why |
|---|---|---|
| Routine and repetitive work | Unit rates or fixed price | Scope and efficiency are known, so work can be prepared and priced in advance. |
| Unplanned work | Reimbursable (time and materials) | Cannot be prepared, so cannot be priced efficiently in advance. Efficiency is protected through agreed rates and clear controls on each job. |
The same plan should make cross-discipline coordination explicit. The maintenance planner and a regular cross-discipline meeting are usually the natural owners. This is often well organised within operations and maintenance, but less visible to the procurement team and to project departments. It needs continuous attention from all of them.
Small Projects Under the Same Contract
A maintenance framework contract can also be used for small replacement and sustaining capex projects. With an agreed threshold, quotations can be based on the rates and unit rates already in the contract, so a separate tender is not needed. This increases the volume under the contract and frees procurement to focus on larger issues.
It also reflects a commercial reality. A preferred contractor carries a delivery obligation and invests in a site organisation. A contractor that performs well deserves a healthy margin and a meaningful volume of work in return. That is what makes a long-term relationship sustainable for both sides.
Performance Feedback in a Fixed Rhythm
Feedback works best when it follows a clear rhythm, from daily experience to management level:
| Frequency | What happens |
|---|---|
| Daily and weekly | Maintenance collects experience with the contractor: quality, safety, planning and cooperation. |
| Quarterly | Internal preparation with operations, maintenance and procurement, followed by a structured review with the contractor. |
| Annually | Review at management level on both sides: performance, development and the future of the relationship. |
In my experience the difference between a framework contract that works and one that merely exists lies less in the clauses than in the conversations before and after signing. When operations, maintenance and procurement build the contract together, and keep talking to each other and to the contractor in a fixed rhythm, the contract becomes a working tool rather than a document in a drawer.