An internal review finds a problem two days before submission. The supplier's lead time is two weeks past what the tender requires, and no alternative source has confirmed.
There are three things a team can do with that, and only one of them is defensible.
You can fix it, if there is time. You can decline to bid. Or you can bid, knowing, with the gap stated in the offer and priced into the position. What you cannot do, and what happens constantly, is submit while quietly hoping nobody checks that line.
The bid that hides a known gap is not a bid with a risk. It is a bid with a lie in it, and the lie is the part that ends relationships.
Why the hiding happens
Rarely from dishonesty. Usually from the shape of the process.
The gap is found late, by someone junior, at a moment when raising it means visibly delaying a submission that senior people are expecting. There is no clean mechanism for saying we are proceeding with this known problem, so the only available options feel like block it or say nothing. Most people say nothing and resolve to sort it out at contract stage.
That is a process failure being paid for with someone's judgement. If accepting a known risk is a legitimate commercial decision, and it usually is, then the system has to have a way to record it that is faster than hiding it.
What an internal review should produce
Not a pass or fail. A list, with each item in one of three states, and nothing allowed to be silent.
| State | Meaning | What it requires |
|---|---|---|
| Blocker | The package cannot go as it stands. A false statement, a missing mandatory document, an unsigned certification. | Fix it. There is no accept option. |
| Accepted risk | A real gap, knowingly carried, with a commercial reason. | A named person accepts it, and it appears in the package as a disclosure. |
| Cleared | Checked and sound. | Nothing. |
Sample states. The middle row is the one most processes have no room for.
The distinction that matters is between the first two. Something dishonest is never acceptable, and no seniority makes it so. A stated inability to meet a requirement is not dishonest at all, it is information the buyer is entitled to and often not disqualifying.
Disclosure usually costs less than people fear
The instinct is that naming a gap loses the bid. Sometimes it does. More often the evaluator already knows the market, and a bid claiming full compliance on a lead time nobody in the industry can meet reads as either careless or optimistic. Neither is the impression you want on a technical evaluation.
A stated exception with a reason and a mitigation reads as a supplier who understands their own supply chain. On a long relationship, that is worth more than the line item.
And it protects the person who signed
The practical benefit is at contract stage, months later, when the lead time becomes a live issue. If it was disclosed, it is a known condition and the conversation is about managing it. If it was hidden, the same fact is now a performance failure and possibly a misrepresentation.
Same underlying reality, completely different position, decided entirely by whether someone wrote it down at bid time.