The contract management gap:
why most projects lack the role they need most

The role nobody assigns

I once walked into a program review where the executive sponsor was frustrated. There were three vendor streams, three different complaints about the project team, all landing on the same PM. The vendors were not coordinating with each other.

They had independently discovered that complaining about the PM was easier than addressing the deliverable defects the PM kept raising. The pattern was not a coincidence. It was structural. The program had no contract manager.

In The vendor management trap, I described how PMs absorb commercial authority by default when nobody else steps into the gap. The most common reason nobody steps in is simple: the organisation does not have a contract manager and does not realise it needs one.

Most organisations assume contract management responsibility sits with a line manager or director somewhere. It never gets explicitly assigned. On smaller engagements, that gap is manageable. On larger ones (panel arrangements, master services agreements, multiple concurrent vendors) the absence creates exactly the structural failure that lets vendors reframe quality enforcement as a personality problem.

Three roles, not two

The vendor management trap describes three authority domains that converge on the PM: delivery, technical, and commercial. The third, commercial authority, actually bundles two distinct functions: the mechanics (contract compliance, payments, variations) and the business relationship (strategic partnership, trust, future work). The PM experiences them as one undifferentiated hat. The fix is to assign three distinct roles:

The PM provides the delivery evidence. The contract manager translates it into contractual obligations and remedies. The executive authorises the commercial decision. The vendor sees three faces (delivery, contract, and relationship) and can't collapse them into a single personality narrative.

What a contract manager brings

A contract manager brings two things that a PM and an executive typically cannot. First, they operate a consistent system for managing vendors across the organisation. They know the contract framework levers (performance notices, remediation clauses, variation mechanisms) and they apply them the same way on every engagement.

That consistency is what makes enforcement defensible. When the contract manager raises a performance issue, it carries weight because the same process applies to every vendor, not just the one currently causing problems.

Second, they are structurally distant from the delivery. They are technocrats, not advocates. That distance is their value.

This distinction matters because of how vendors perceive the people enforcing quality. A PM can be perceived as too invested in the project outcome, even when they are doing exactly the right thing. The customer rarely understands the delivery detail well enough to see the difference.

A contract manager is seen as impartial because they manage across all vendors, not just this one. Their authority comes from the contract framework, not from a position on the delivery. That impartiality is hard for a vendor to reframe as personality.

Contract management is not relationship ownership

The critical distinction is psychological, not administrative. A relationship owner needs to build trust and think long-term. A contract manager needs to apply consequences consistently and think procedurally. These are opposing temperaments. When one person holds both, enforcing a remediation clause undermines the rapport they need for the next negotiation. That is the vendor management trap at the commercial level, one layer up.

The limits of contract management

Contract managers are not project managers. They don't own the delivery plan, manage the project team, or make day-to-day delivery decisions. They don't attend standups or manage sprint backlogs.

They are also not the business relationship owner. They don't make strategic decisions about vendor partnerships, future work, or organisational direction. They don't decide whether to renew a contract. They provide the performance evidence that informs that decision.

Their scope is the contract framework: compliance, performance measurement, variation management, and procedural enforcement. They are the independent voice that validates whether the PM's enforcement is proportionate and contractually sound.

When you do not have a contract manager

Where no contract manager exists, the PM absorbs that procedural function by default. It is exhausting, and it rarely works well.

In addition to delivery evidence, the PM must now provide the executive with clear, documented detail on the organisation's obligations under the contract. What does the contract actually say, and what has the vendor delivered against it? What remedies are available, and what are the consequences of not acting?

The executive still authorises the commercial decision, but the PM provides the contract literacy that most executives lack on delivery detail. This is harder than it sounds. The PM must operate simultaneously as the delivery enforcer and the contract interpreter, without a structurally independent voice to confirm that the enforcement is proportionate.

Push for a dedicated contract manager when the contract is large enough to create competing incentives, typically when milestone payments, formal performance notices, or contract variations are in play. You also need one when managing multiple concurrent vendors under different frameworks, or when performance disputes have already escalated above the delivery level.

A shared or part-time arrangement works when the contract value is low, the vendor relationship is straightforward, and the executive is genuinely engaged. Periodic contract reviews with procurement, or a part-time contract manager shared across projects, can introduce the independent perspective without the overhead.

Whatever arrangement you choose, make it explicit. The three functions described in this article (delivery, contract management, and business relationship) need to be mapped to named positions at project setup. When the mapping is implicit, the PM absorbs contract management by default, not by delegation. Nobody agreed to it. Nobody is accountable for the gap. And when the vendor exploits that gap, everybody points at the PM.

A role-to-position mapping does not need to be complicated. The value is in forcing the conversation at project setup, not in the format. Who holds each function? What decisions can they make? When do they escalate? Three functions, three models:

The "PM Alone" model only works if the executive sponsor is genuinely engaged and willing to act when escalation thresholds are reached. If the executive is disengaged, the PM is holding all three functions without backup, which is the gap this article describes.

Functions that should not be co-located without explicit safeguards:

• Contract enforcement + business relationship ownership. The person issuing performance notices cannot also be the person maintaining strategic rapport. This recreates the vendor management trap at the commercial level.
• Contract enforcement + delivery management with no independent voice. The PM's enforcement looks self-serving without a structurally independent perspective validating that it is proportionate and contractually sound.
• All three functions in one person. This is the default when contract management is absent. If genuinely unavoidable, document it as a risk and escalate it to the steering committee.

The mapping forces the conversation. When someone has to write down "the PM holds contract management authority on this engagement," they start asking whether that is actually a good idea. That question is the point.

If you are in this position, the strongest move is to make the gap visible. Document that commercial decisions are being made without contract management support, and present the risk to the steering committee. You are not asking for help. You are identifying a governance gap and proposing a fix.

Make the gap visible. Document that commercial decisions are being made without contract management support, and present the risk to the steering committee.

The principle

Contract management and business relationship ownership are different functions with different objectives. Contract management enforces the mechanics: obligations, remedies, compliance. Relationship ownership maintains the strategic partnership: trust, rapport, future work. Conflating them creates the same structural impossibility as asking the PM to enforce quality while maintaining the vendor relationship.

If your organisation manages vendor delivery without a dedicated contract management function, you have a governance gap. The PM can compensate temporarily by providing contract literacy to the executive. But that compensation is a workaround, not a solution. The structural fix is an independent contract management function (even part-time, even shared) that provides the impartial, procedural authority that makes quality enforcement defensible.

This article contributes risks V5-V8, G5-G7, G10, K5, and CO1-CO3 to the practitioner's risk taxonomy.