The gap between having experience and proving it
Most professional-services firms that lose a technical evaluation did the work being asked about. What they could not do, inside the submission window, was locate the completion certificate, confirm the contract value, reach the colleague who ran the assignment, and cite all three in a form the committee accepts. The experience existed; the evidence was not retrievable in time.
An unsupported claim is not a strong claim. It is a claim the evaluator has to take on faith — and most will not.
What makes a claim supportable
A supportable claim can be traced, in one step, to a record someone in the organization has approved. Four properties make that possible.
- A source location — the document, and the page or clause inside it.
- An owner — the person accountable for keeping it accurate.
- An approval state — reviewed and current, not a draft someone left behind.
- A date — so a reader can judge whether it is still true.
An operating pattern that holds under deadline
The order matters. Teams that search first and decide later end up adapting whatever they found rather than answering what was asked.
- Read the requirement and name the decision it forces before opening any archive.
- Retrieve approved, current knowledge — and prefer a weaker claim you can prove to a stronger one you cannot.
- Adapt the evidence to this tender instead of pasting a previous response.
- Attach the source alongside the claim, so review is a check rather than an investigation.
- Record the outcome and the lesson while the reasoning is still fresh.
What to do about claims you cannot support
Delete them, or downgrade them to what the record actually shows. A percentage nobody can source, a guarantee nobody has authorised, and a superlative nobody has measured are the three that most often survive internal review and then cost marks. Naming them explicitly — before submission, in a compliance pass — is cheaper than defending them afterwards.