Writing a tender response that scores

What is actually happening to your words

An evaluator has your answer, the question, and a marking guide that describes what a high score looks like. They read, they look for the things the guide lists, and they award a mark. Often several evaluators score independently and then moderate.

Two consequences follow, and they explain most losing bids.

• They score what is written, not what is true. They cannot credit experience you did not describe, even if they know you have it.
• They are looking for specific things. Anything that makes those harder to find costs marks, however well written it is.

The GOV.UK guidance for SMEs lists the common reasons bids fail: failing to answer the specific question, failing to address the full specification, and insufficient detail. All three are writing failures rather than capability failures.

Use the question as the structure

The single highest-return habit in bid writing. If the question has four bullet points, your answer has four subheadings, in the same order, using the buyer's words.

It feels mechanical. That is the point. The evaluator can find each element without hunting, and cannot accidentally miss one. GOV.UK guidance says the same: adopt the bullet points as subheadings and address each point in the order it appears.

A structure that works for most quality questions

1. The requirement. One sentence restating what is needed, in the buyer's terms. Shows you understood before you start telling them things.
2. The method. What you will actually do, in sequence. Tools, governance, who does what. This is the “how”, and it is where most answers go thin.
3. The people. Named roles, real experience, honest capacity. Not the whole company, the team for this contract.
4. The controls. What you do when it goes wrong: risks, escalation, quality assurance, reporting, contingency. Buyers are pricing risk as much as service.
5. The evidence. One concrete example. Client, date, your role, what you did, what changed, with a number.
6. The outcome. Tie it back to what the buyer said they wanted.

Words to delete

Evidence beats adjectives

The strongest single upgrade to most answers is replacing claims with examples that carry numbers. Not because numbers are impressive, but because they are checkable, and checkable statements are what a marking scheme rewards.

Keep an evidence library: projects with client, date, scope, your role, what changed, and the measure. Reuse that. Do not reuse whole answers, which never quite fit the next question and read like they do not.

Respect the mechanics

• Word limits are enforced by portals that truncate. Write to the limit, not past it.
• Answer only what is asked. Material about services not in the specification spends your word count and earns nothing.
• Define acronyms once. The evaluator may not be from the department that wrote the spec.
• Make each answer stand alone. Cross-references to another answer often are not followed.
• Short sentences, real headings, white space. A dense block of text is harder to score and scores worse.

Get someone else to mark it

Before submission, have someone who did not write it score it against the published criteria, pretending to be the evaluator. Not proofread: score. Ask them where each mark is being earned.

If they cannot find the evidence for a criterion in under a minute, neither will the evaluator. That review finds more marks than another day of drafting.