Procurement Dispute vs. Performance Issue: When Should the PM Involve the Contract?
admino
Manage the relationship or invoke contractual mechanisms?
A seller is underperforming.
A deliverable is disputed.
The buyer and seller disagree about scope, payment, or responsibility.
What should the project manager do?
Should the PM:
- work directly with the seller,
- manage performance informally,
- review the agreement,
- involve procurement,
- issue a formal notice,
- or escalate through a contractual mechanism?
The difficulty is that a seller problem does not automatically equal a procurement dispute.
The better question is:
Can this issue still be resolved through normal performance management, or does resolution now require clarification, modification, or enforcement of contractual obligations?
A useful Project Reasoning Lab principle is:
Review the contract early. Invoke formal contractual mechanisms only when the issue actually requires them.
1. Performance Issue vs. Procurement Dispute
The first distinction is simple.
Performance issue
A performance issue asks:
How do we get delivery back on track?
It may involve:
- delay,
- quality concerns,
- resource problems,
- weak communication,
- missed interim expectations.
These issues may still be manageable through:
- clarification,
- corrective action,
- recovery planning,
- monitoring,
- collaboration.
Procurement dispute
A procurement dispute asks:
What are the parties actually required, allowed, or entitled to do?
It may involve disagreement about:
- contracted scope,
- acceptance,
- payment,
- responsibility,
- authorization,
- change,
- remedies.
A strong distinction is:
A performance issue concerns whether delivery is going wrong. A procurement dispute concerns disagreement about what the parties are required, allowed, or entitled to do about it.
2. Use a Five-Question Test
When a seller problem appears in a PMP® scenario, ask:
1. What happened?
Identify the actual issue.
2. What does the agreement require?
Check the current authorized obligations.
3. Who is responsible?
Determine whether the cause sits with:
- seller,
- buyer,
- both,
- external condition.
4. Can normal performance management resolve it?
Would collaboration, corrective action, or recovery planning be enough?
5. Does the next step require contractual authority or a formal mechanism?
If yes, involve the appropriate procurement or contracting authority.
This helps avoid two opposite mistakes:
Escalating too early
and
waiting too long to formalize the issue.
3. Review the Contract Early
The contract is relevant from the beginning because it defines the relationship.
That may include:
- statement of work,
- deliverables,
- acceptance criteria,
- pricing,
- responsibilities,
- change procedures,
- notice requirements,
- dispute provisions,
- remedies.
But reviewing the contract is not the same as immediately invoking formal enforcement.
That distinction matters:
The contract helps you understand the problem before it becomes the mechanism for resolving the problem.
4. Manage Ordinary Performance Problems Collaboratively
Consider:
A seller identifies a temporary staffing problem, proposes a credible recovery plan, and still expects to meet the final required delivery date.
There may be no procurement dispute.
The PM can:
- verify impact,
- assess recovery,
- monitor progress,
- document the issue,
- maintain communication.
The seller has a performance problem, but the parties are not necessarily disputing rights or obligations.
A useful principle is:
Do not turn every operational problem into a contractual confrontation.
5. When Contractual Mechanisms Become More Important
Formal contractual action becomes more relevant when resolving the issue requires more than ordinary performance management.
Examples include:
- disagreement about scope,
- disputed acceptance,
- disputed payment,
- unauthorized work,
- repeated material nonperformance,
- formal notice requirements,
- claims or remedies,
- commercial decisions beyond PM authority.
The key question is:
Does solving this problem now require clarification or enforcement of contractual rights, obligations, or authority?
If yes, the issue has moved beyond simple performance management.
6. Scenario: Scope Disagreement
Consider:
The buyer expects the seller to perform additional testing. The seller says the testing is outside the agreed scope and requests additional payment.
This is not simply:
“The seller is refusing to cooperate.”
The real question is:
Does the existing agreement require the work?
The PM should review:
- scope,
- requirements,
- acceptance criteria,
- approved changes,
- relevant procurement records.
If the disagreement cannot be resolved through clarification, the applicable contract process may need to be used.
7. Scenario: Acceptance Dispute
Now consider:
The seller says a deliverable is complete. The buyer says it does not satisfy the agreed acceptance conditions.
This is different from a simple quality complaint.
The PM should determine:
- what the acceptance criteria actually require,
- what evidence exists,
- whether the deliverable conforms,
- who has acceptance authority,
- what process applies if the parties disagree.
The important question is:
Is the disagreement about performance quality — or about whether the contractual acceptance standard has been met?
Once formal acceptance is disputed, the contract becomes much more central.
8. Scenario: Additional Work and Payment Dispute
Consider:
The seller performed additional work after a project team member requested it and now seeks payment. Procurement says the change was never formally authorized.
This is no longer just a delivery issue.
The PM may need to determine:
- who requested the work,
- whether that person had authority,
- what the change process required,
- what the contract says about additional work,
- who can decide the commercial response.
This is a classic example of why:
A project request and a contract authorization are not automatically the same thing.
9. Scenario: Repeated Nonperformance
Consider:
The seller repeatedly misses agreed performance requirements despite several recovery discussions and corrective actions.
At some point, continued informal management may no longer be enough.
The PM may need to:
- document the pattern,
- involve procurement,
- review notice provisions,
- follow escalation procedures,
- use available contractual mechanisms where appropriate.
The threshold is not simply:
“Something went wrong again.”
It is:
Normal performance management is no longer resolving the problem.
10. Relationship Management and Contract Management Work Together
A common false choice is:
Protect the relationship
or
enforce the agreement
Strong procurement management may require both.
The PM can communicate constructively while also:
- documenting performance,
- following required processes,
- preserving clarity around obligations,
- involving the right authority.
So:
Relationship management and contract management are not competing choices.
A good relationship supports delivery.
It does not replace accountability.
11. Do Not Escalate Contractually Before the Facts Are Clear
The opposite mistake is to jump too quickly to formal language such as:
“The seller is in breach.”
That may be premature.
Before invoking a formal mechanism, clarify:
- what happened,
- what the agreement requires,
- who is responsible,
- whether corrective action is still feasible,
- whether formal action is actually required.
A useful sequence is:
Understand → Verify → Collaborate → Govern → Escalate when necessary
Not every scenario will follow those steps rigidly, but the logic is sound.
12. Know the Project Manager’s Authority
The PM may be able to:
- monitor performance,
- document issues,
- coordinate recovery,
- assess impact,
- communicate with the seller.
But the PM may not have authority to:
- settle a formal claim,
- approve disputed payment,
- waive contractual rights,
- modify commercial terms,
- terminate the agreement,
- impose certain remedies.
So ask:
Can the PM manage the performance issue, or does the next decision require procurement or contractual authority?
13. Quick Comparison
| Situation | Likely Focus |
|---|---|
| Seller identifies issue and presents credible recovery plan | Performance management |
| Seller misses interim milestone but recovery remains realistic | Assess and monitor |
| Parties disagree about contracted scope | Review agreement/contract process |
| Parties disagree whether acceptance criteria were met | Contractual acceptance requirements |
| Seller requests payment for disputed additional work | Change and payment provisions |
| Repeated nonperformance continues after corrective action | Procurement / contractual action may be needed |
| Formal notice or remedy is required | Follow contractual mechanism |
| Decision exceeds PM authority | Involve appropriate authority |
14. Three Common Traps
Trap 1: Seller Problem = Procurement Dispute
Not automatically.
Many seller problems remain performance-management issues.
Trap 2: Good Relationship = Avoid the Contract
No.
A good relationship does not eliminate contractual obligations or required processes.
Trap 3: Contract Exists = Invoke Formal Remedies Immediately
No.
Review the agreement early, but use formal mechanisms only when the situation requires them.
Final Takeaway
When a procurement problem appears, do not immediately choose between:
“work it out informally”
and
“enforce the contract.”
Ask:
What happened?
What does the agreement require?
Who is responsible?
Can normal performance management resolve it?
Does the next step require contractual authority or a formal mechanism?
Then choose the response that fits.
Review the contract early, manage performance collaboratively where possible, and invoke formal contractual mechanisms when resolving the issue requires clarification or enforcement of obligations, rights, authority, or remedies.
That is what the PMP scenario is really asking.
