This conversation often goes wrong in two ways. It may be too soft, like "we had some concerns about the delivery," so the vendor may not know that anything must change. Or the message may be too blunt, and a useful relationship may not survive the next project.
The answer is not a softer word for "bad." Be clear about what fell short and state its cost in plain terms. Then explain what must happen next without making a claim you cannot prove.
Be candid about the gap, not vague about your feelings
Candid means direct and honest, with a tone that can be calibrated rather than blunt. It helps you describe a fact instead of a vague feeling, which keeps the message from sounding empty or like an attack.
An example that is too soft:
"We had some concerns about how the project went."
A candid version:
"I want to be candid: the second milestone didn't meet the accessibility requirements we specified in the scope."
The candid version names what happened. The soft version makes the vendor guess what "some concerns" means.
Read more: how to use "candid" naturally in professional English.
Want to get better at distinctions like this?
Lyra Practice helps you learn the nuance of high-value workplace expressions, then practice using them in realistic situations.
See how Lyra Practice works →Name the trade-off they made without telling you
Work may fall short because one goal was traded for another, often under time or budget pressure. A team may cut steps to meet a deadline or price. Trade-off names this clearly without accusing the vendor of acting in bad faith.
"It looks like the trade-off here was QA coverage for speed — 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 names what may have happened. It also lets the vendor confirm or correct your view instead of focusing only on a defense.
Read more: how to use "trade-off" naturally in professional English.
Flag the pattern, not just the incident
One miss may be a single mistake, but the vendor needs to know how you view it. Is it a one-off, or a pattern you now watch? Flag means giving an issue the right level of attention without hiding it or calling it a crisis.
"I want to flag this as the second delivery this quarter that's needed significant rework after handoff."
That sentence does more than a broad complaint because it tells the vendor exactly what you are tracking. Clear facts can help their team change its process.
Read more: how to use "flag" naturally in professional English.
Say what you need them to do to mitigate it
After naming the gap and pattern, make a clear request instead of ending with an open complaint. Mitigate means reducing a problem's harm or impact. It frames the request as a fix, not 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 ends the conversation with a clear action.
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 QA coverage for speed. 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."
This message is specific and fair, so it is hard to mistake for either an attack or a minor note. That clear balance matters more than merely 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.