Chronic vendor lateness is a pattern, not an incident — the same vendor missing dates repeatedly rather than one bad week. The distinction matters because a pattern has a cause, and the cause determines what actually fixes it. Most owners skip the diagnosis and go straight to the escalation path, which produces a tense phone call and no real change if the underlying cause was never identified.
There are three causes, and they call for different responses.
Diagnose before you respond
Capacity. They have taken on more work than they can deliver on time — more customers, not enough people, growth that outran their own operations. This shows up as lateness that's getting steadily worse, spread across their whole customer base, not just you.
Priority. They can deliver on time, but you're not who they deliver on time for. Bigger accounts, more profitable work, or whoever complained most recently gets the attention. This shows up as inconsistent lateness — fine for two months, late for one, fine again — that tracks suspiciously well with how much noise you made last time.
Scoping. The deadline was never realistic for what was actually ordered, and everyone agreed to it anyway because the alternative was an uncomfortable conversation at the time of the quote. This shows up as a vendor who is late by roughly the same amount every time, which is really a sign the timeline was wrong from the start, not that execution is failing.
Ask directly which one it is before you decide what to do. A capacity problem, pushed on harder, doesn't get fixed — it gets denied, because admitting it usually means admitting they're over-committed to everyone, not just you. A priority problem responds to leverage. A scoping problem responds to a harder, more honest conversation about the timeline itself, not the vendor's performance against it.
What the contract actually gives you
Before the conversation, know what you're actually entitled to — most owners have this backwards and go in assuming they have no leverage, when the contract usually says otherwise.
Notice and cure. Most vendor contracts require written notice of a performance failure and a defined period to fix it before you can terminate for cause. Check what that period is. It's usually shorter than people assume, and it's the clock that has to start before you have real leverage to threaten termination.
Service levels. If the contract has SLA language — response times, delivery windows, penalty terms for missing them — that's not boilerplate. It's a number you can point to in the conversation instead of arguing feelings, and often a penalty you're owed but haven't been invoking.
Termination rights. Whether you can exit for cause, what "cause" is defined as, and whether there's a termination-for-convenience option that gets you out even without proving fault. This is worth knowing before the conversation, not after you've decided you're done — it changes how much leverage you actually have going in, and it's worth checking against the auto-renewal terms too, since a contract that's about to silently renew changes your timeline for acting.
If you haven't read the contract closely since you signed it, do that first. Most of the leverage in a vendor problem is sitting in a document nobody has reopened since onboarding.
Escalate or dual-source
Escalate when: the relationship still has value, the cause is fixable (priority or scoping, not chronic capacity), and you have real leverage — meaningful spend, a contract with teeth, or a genuine alternative you're prepared to use. Escalation without leverage is just a stronger-worded version of the same complaint that didn't work the first time.
Dual-source when: the pattern is capacity-driven and getting worse, you've already escalated once without real change, or the cost of a miss is high enough that you can't afford to find out a third time whether they've fixed it. Dual-sourcing isn't disloyalty — it's insurance, and vendors who are confident in their own delivery are rarely bothered by a customer keeping a backup qualified.
The two aren't mutually exclusive. Escalating while quietly qualifying a backup is usually the right move when you're not yet sure which category you're in — it costs little and protects you either way.
The conversation itself
Bring specifics, not impressions. "You've missed three of the last four deadlines — March 12th by six days, April 2nd by four, May 20th by nine" is a conversation about facts. "You keep being late" is a conversation about tone, and it's the one that gets deflected fastest.
Ask the diagnosis question directly: "Is this a capacity issue, a priority issue on your end, or was the original timeline wrong?" Most vendors will tell you the truth if asked plainly, because the alternative — getting caught in a vague excuse later — is worse for them.
State the consequence concretely and follow through on it. "If this happens again this quarter, we're moving to a backup for the next order" is a real consequence. A vague "this needs to improve" is not, and vendors calibrate their urgency to how specific your consequences actually are.
The version that matters
Lateness that happens once is an incident. Lateness that keeps happening is information about how this vendor is actually run, and the fix depends entirely on which of the three problems you're looking at. Diagnose first. The conversation, the leverage, and the decision to dual-source all follow from getting that part right.
When you want a second opinion before the call
Knowing whether you have real contractual leverage, and how a specific pattern of misses compares to what the SLA actually promises, is exactly the kind of question worth checking before you make the call, not during it.
Helm's General Counsel advisor reads contracts uploaded to the Vault and can pull the notice-and-cure terms, the SLA language, and your termination rights before you have the conversation. Upload the agreement, describe the pattern, and ask what leverage you actually have.