Back to blog

How to Tell a Vendor Their Work Fell Short, Diplomatically

2026-08-14

There are two ways this conversation usually goes wrong. Either it's too soft — "we had some concerns about the delivery" — and the vendor walks away not understanding that anything needs to change. Or it's too blunt, and a relationship you may still need survives the next project only barely.

The way through isn't finding a gentler synonym for "bad." It's being specific about what fell short, naming the cost of it plainly, and being clear about what happens next — all without implying bad faith you haven't established.

Be candid about the gap, not vague about your feelings

Candid means direct and honest, calibrated rather than blunt. It's the difference between describing a feeling and describing a fact, and it's what keeps this conversation from reading as either an attack or a non-statement.

Too soft:

"We had some concerns about how the project went."

Candid:

"I want to be candid: the second milestone didn't meet the accessibility requirements we specified in the scope."

The candid version names what actually happened. The soft version leaves the vendor to guess what "some concerns" even refers to.

Read more: how to use "candid" naturally in professional English.

Name the trade-off they made without telling you

Work usually falls short because something got traded against something else under time or budget pressure — corners were cut somewhere to hit a deadline or a rate. Trade-off names that plainly, without requiring you to accuse the vendor of cutting corners in bad faith.

New to Lyra Practice?

Lyra Practice helps advanced non-native professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios until it feels natural, so their English sounds precise and senior at work.

Start learning for free →

"It looks like the trade-off here was speed for QA coverage — the deadline held, but we're finding issues that testing should have caught."

This is more useful than "the quality wasn't there," because it identifies the actual mechanism, and it invites the vendor to confirm or correct your read of what happened rather than just defend themselves.

Read more: how to use "trade-off" naturally in professional English.

Flag the pattern, not just the incident

One miss is a mistake. A vendor needs to know whether you're treating this as a one-off or as something you're now watching for. Flag — raising something to the right level of attention, without either burying it or overstating it into a crisis — is how you make that distinction clear.

"I want to flag this as the second delivery this quarter that's needed significant rework after handoff."

That sentence does something a general complaint can't: it tells the vendor exactly what you're tracking, which is usually what actually changes behavior on their side.

Read more: how to use "flag" naturally in professional English.

Say what you need them to do to mitigate it

Once the gap and the pattern are named, the vendor needs a concrete ask, not an open-ended complaint. Mitigate — reducing the severity or impact of a problem — gives you language for the ask without turning it into a punishment.

"We'd like your team to mitigate this by redoing the QA pass at your cost and sending us the coverage report before Friday — that's what would let us close this out clean."

This closes the conversation on an action, which is usually what determines whether the relationship survives the miss — a vendor who hears a clear, fair ask is far more likely to deliver than one who's only heard that you're unhappy.

Read more: how to use "mitigate" naturally in professional English.

Putting it together

"I want to be candid: the second milestone didn't meet the accessibility requirements in scope. It looks like the trade-off was speed for QA coverage. I want to flag this as the second delivery this quarter needing rework after handoff. We'd like your team to mitigate this by redoing the QA pass at your cost and sending us the coverage report before Friday."

That's specific, fair, and hard to misread as either an overreaction or a non-event — which is the actual goal of this conversation, more than sounding polite.

Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.

Think you know this expression?

Take the free 2-minute High-value Workplace Expression Gap Test and see which expressions you should practice.

Take the free challenge