Seller Delay vs. Contract Performance Problem: What Should the Project Manager Do?

October 8, 2026 September 23, 2026

admino

A seller misses a delivery date.

Is that automatically a contract-performance failure?

Not necessarily.

A late delivery may result from:

seller underperformance,
a buyer-caused delay,
an approved change,
unclear requirements,
an external dependency,
another event recognized by the agreement.

That is why procurement scenarios on the PMP® exam can be deceptively difficult.

The visible symptom may be:

“The seller is late.”

But the better question is:

What was actually required, who controlled the cause, what impact does it create, and what response is authorized?

A useful Project Reasoning Lab principle is:

Seller delay is a fact. Contractual nonperformance is a conclusion.

Do not jump from one to the other without checking the current agreement and the surrounding facts.

1. Start With What Actually Happened

Consider:

A seller informs the project manager that a critical component will arrive five days late.

That tells you there is a schedule problem.

It does not yet tell you:

whether the seller failed to meet a contractual obligation,
whether the buyer contributed to the delay,
whether an approved change affected the date,
whether another contract provision covers the delay,
whether the project impact is significant.

The first step is to separate the observable event from the interpretation.

Ask:

What happened?

Then:

What obligation actually applied?

2. What Does the Current Agreement Require?

The contract or agreement is the reference point for understanding seller performance.

Relevant terms may include:

delivery dates,
milestones,
technical requirements,
quantities,
service levels,
acceptance conditions,
buyer responsibilities,
seller responsibilities,
change provisions,
notice requirements,
remedies,
decision authority.

Suppose the seller misses an internal project date that was never part of the agreement.

That may be primarily a project scheduling issue.

Now suppose the seller misses an explicitly agreed contractual milestone.

That is a different situation.

The project manager should always compare actual performance against the current authorized commitment, not an outdated expectation.

3. A Late Seller Is Not Automatically the Cause of the Delay

This is one of the most important procurement distinctions.

Consider:

The seller cannot begin fabrication because the buyer has not provided the final approved design package.

The seller may still deliver late.

But the seller may not be the party that created the delay.

Now compare that with:

The seller had all required information but failed to assign sufficient resources and missed the agreed milestone.

Those situations require different reasoning.

Possible causes may include:

seller performance,
buyer delay,
shared responsibility,
an approved change,
unclear requirements,
another vendor dependency,
an external event.

Ask:

Who controlled the condition that caused the delay?

A late delivery and responsibility for that late delivery are not automatically the same thing.

4. Approved Changes May Change the Commitment

Suppose:

The buyer approves a design change that increases fabrication time.

The seller later delivers after the original delivery date.

Before deciding that performance is deficient, the PM should verify:

whether the delivery date was also revised,
what change was formally authorized,
what commitment now applies.

A common reasoning error is comparing current performance against an old commitment that has already been changed.

The correct reference point is the current authorized agreement.

5. Contract Performance Is Broader Than Schedule

A seller can deliver on time and still fail to meet an important obligation.

Consider:

A supplier delivers components on the required date, but testing shows that they do not meet the agreed technical specifications.

The schedule requirement may have been satisfied.

But other contractual requirements may not have been.

Seller performance may involve:

timing,
quality,
quantity,
specifications,
documentation,
service levels,
compliance,
acceptance conditions.

So do not ask only:

“Was it late?”

Ask:

“Did the seller meet the obligations that apply?”

6. Contract Performance and Project Impact Are Different Questions

This distinction is especially useful on scenario questions.

Contract-performance question

Ask:

Was the applicable seller obligation met?

Project-impact question

Ask:

What does the situation do to the project?

A seller may miss a minor contractual milestone with little impact on project outcomes.

Or a relatively short delay may affect:

the critical path,
a regulatory milestone,
downstream work,
customer commitments,
cost,
resource availability.

So the PM should assess both:

What happened contractually?

and

What does it mean operationally for the project?

7. Scenario: The Seller Warns About a Future Delay

Consider:

A seller tells the project manager that a critical shipment may arrive one week late.

A weak response would be:

Immediately impose a penalty.

The delay has not necessarily occurred yet, and the applicable commercial response may not even be within the PM’s authority.

A better reasoning sequence is:

verify the contractual commitment,
understand the cause,
assess project impact,
explore mitigation or recovery,
follow the applicable procurement and governance process.

The warning is important information.

It is not automatically proof of contractual nonperformance.

8. Scenario: The Delay Is Shared

Consider:

A seller delivers late, but the project team provided final specifications two weeks later than planned.

The PM should not automatically attribute the entire delay to the seller.

The situation may involve:

buyer responsibility,
shared responsibility,
a change in assumptions,
revised schedule expectations.

The PM should review:

documented obligations,
timing of inputs,
approved changes,
notices,
resulting impact.

This is one of the strongest procurement reasoning habits:

A late seller does not automatically mean the seller caused the delay.

9. Scenario: Repeated Seller Underperformance

Now consider:

A seller repeatedly misses agreed milestones despite having the required information and resources.

This is more clearly a supplier-performance concern.

The PM may need to:

document the pattern,
review performance against the agreement,
discuss recovery with the seller,
request an appropriate recovery plan,
involve procurement or contract-administration functions,
use available contractual mechanisms where appropriate.

The response should reflect:

severity,
recurrence,
project impact,
contract terms,
delegated authority.

A recurring pattern is different from one isolated problem.

10. Collaboration and Contract Discipline Can Coexist

Procurement management is not simply:

be collaborative

or:

enforce the contract

Both may be appropriate.

Consider:

A seller experiences a temporary capacity problem but presents a credible recovery plan.

The project manager may work collaboratively with the seller while also:

documenting the issue,
monitoring recovery,
preserving the project’s position,
following applicable procurement processes.

A useful principle is:

Collaborate where possible. Govern where necessary.

Relationship management should not replace disciplined contract management.

And contract discipline does not require an adversarial relationship.

11. Know the Limits of PM Authority

The project manager may be able to:

monitor performance,
document issues,
coordinate recovery,
communicate with the seller,
assess impact.

But the PM may not have authority to:

amend pricing,
waive contractual rights,
terminate an agreement,
approve major commercial changes,
impose certain remedies.

Those decisions may belong to:

procurement,
contract administration,
legal,
sponsor,
authorized management.

This gives us another useful question:

Can the PM manage the issue—or does the commercial decision belong to another authority?

12. Quick Comparison

Situation	Reasoning Direction
Seller warns of possible delay	Verify commitment, cause, impact, and mitigation
Seller misses an internal date not stated in the agreement	Project schedule issue may be primary
Seller misses a contractual milestone	Verify obligation, cause, impact, and authorized response
Buyer contributed to the delay	Examine shared responsibility
Approved change altered delivery timing	Use the current authorized commitment
Seller delivers on time but fails specifications	Contract-performance issue may still exist
Seller repeatedly underperforms	Document, address recovery, and use appropriate procurement mechanisms
Commercial response exceeds PM authority	Involve the appropriate procurement/legal/management authority

This is a reasoning guide, not a legal determination.

13. Three Common Traps

Trap 1: Seller Is Late = Seller Failed Contractually

Not automatically.

First, check the actual obligation and cause.

Trap 2: Good Vendor Relationship = Ignore the Agreement

No.

Collaboration and contract discipline can coexist.

Trap 3: The PM Can Decide Every Commercial Response

Not necessarily.

Authority matters.

Final Takeaway

When a seller is late, do not jump immediately to:

“The seller failed.”

Ask:

What was actually required?

What caused the delay?

Who controlled that cause?

Was the commitment changed?

What impact does the situation create for the project?

What response is authorized?

A seller delay is the symptom. Contract-performance analysis asks what was required, who was responsible, what changed, and what response is appropriate.

The project manager should respond based on the current agreement, documented facts, project impact, and delegated authority—not simply on the fact that a date was missed.