Every bid team has had this conversation. A response goes out that the team is genuinely proud of - well-organised, professionally presented, written by people who know the service inside out - and it comes back with a score that doesn't reflect any of that. The provider is capable. The response says otherwise.
This is the most common and least understood failure in tendering: most losing responses aren't unqualified - they're miscommunicated. The gap isn't between what you can deliver and what the buyer needs. It's between what you know and what you wrote down. Evaluators can only score the second one.
Here are four patterns we see marked down, quietly and repeatedly, in bids from perfectly capable organisations.
Pattern one: confidence standing in for evidence
There's a particular tone that capable organisations fall into - assured, fluent, slightly general. "We have a strong track record of safe, person-centred delivery." It's true. It's also unscoreable. An evaluator reading that sentence has nothing to check it against: no named example, no measure, no date. Confidence reads well. It doesn't score well. The fix isn't to sound less sure of yourselves - it's to replace the assurance with the thing that earned it: the audit result, the named example, the number.
Pattern two: the framework named but not shown
Bidders often reference the right things - a recognised model, a named methodology, a regulatory framework - as if citing it were the same as applying it. It isn't. Evaluators are specifically looking for the difference between "we use a trauma-informed approach" and a description of what that approach actually looked like in a real, dated situation, with a real person, and what changed as a result. Naming the framework tells the evaluator you've heard of it. Showing the application tells them you can be trusted with it.
Pattern three: answering the spirit of the question, not its structure
Many tender questions are compound - they ask about three or four things inside a single sentence. "Describe your approach to recruitment, training, retention and supervision." A capable, well-written answer can respond to the spirit of that question beautifully and still lose three-quarters of the marks, because the scoring is often structured around each named element separately. If supervision isn't visibly, distinctly addressed, it may not exist as far as the mark scheme is concerned - no matter how well the paragraph reads.
Pattern four: writing for a human reader instead of a scoring document
The tender response you'd hand a new client to reassure them is not the same document as the one that scores well with an evaluation panel. A reassuring narrative flows; a scoring document is structured, headed, and legible in isolation, sentence by sentence, against a rubric. Capable organisations often default to the first instinct - because it's how they'd naturally explain their service - and lose marks to a structure they never considered, because nobody warned them the two documents aren't the same thing.
The uncomfortable conclusion
None of these four patterns is about capability. They're about translation - turning what you know and do into something a stranger, working under time pressure, against a rigid framework, with no context beyond your written page, can award marks for. That translation is a distinct skill from delivering the service well, and it's one that's rarely taught, rarely audited, and almost never diagnosed until after the result comes back.
The good news is that it's entirely learnable. Once you know the four patterns, you can read your own draft looking for them - and close the gap between what you can do and what you've actually written down.