A tight word count can make a tender response harder to write, particularly when the buyer expects you to explain a complex delivery model, address several sub-questions and provide evidence within only a few hundred words.
The answer is not simply to write everything you want to say and cut it down afterwards. Strong concise tender responses usually start with better prioritisation. Before drafting begins, you need to decide which points deserve space, what evidence will support them and which information the evaluator does not need.
Treat the word count as part of the requirement
If a buyer gives you 750 words, the objective is to produce the strongest possible answer within those 750 words. Trying to work around the limit with tiny fonts, squeezed formatting or unrequested attachments can make the response harder to evaluate and may create a compliance problem.
Start by checking exactly how the limit applies. Does it include headings? Are words inside tables counted? Can diagrams be used? Are appendices permitted, and if so, what information can they contain?
Where the tender documents do not answer an important question like this, it may be appropriate to raise a tender clarification question. It is much better to resolve the uncertainty early than discover shortly before submission that several responses need reformatting.
Once the rules are clear, treat them as fixed. The challenge is then deciding how to make the available space work harder.
Break the question down before allocating the words
A 1,000-word question is rarely asking for only one thing. It may contain several requirements, each of which contributes to the evaluator’s overall view of the response.
For example, an NHS mobilisation question might ask you to explain your mobilisation programme, governance arrangements, workforce readiness, risks and approach to maintaining continuity. If you use half the available words describing the programme before considering the other requirements, you immediately place the rest of the response under pressure.
Before writing, split the question into its component parts and decide what each section needs to achieve.
| Requirement | Priority | Approximate space | Evidence needed |
|---|---|---|---|
| Mobilisation approach | High | 250 words | Comparable mobilisation |
| Governance | Medium | 150 words | Roles and meeting structure |
| Workforce | High | 200 words | Resourcing evidence |
| Risk and continuity | High | 300 words | Controls and previous delivery |
| Closing assurance | Low | 100 words | Key outcomes |
Those figures are illustrative rather than a formula. The important point is that you are making decisions about space before the prose begins.
The scoring criteria should influence those decisions. If the buyer places particular emphasis on business continuity or requires specific evidence of workforce readiness, those areas need enough room to demonstrate a credible solution.
Storyboard the response before drafting
It’s good practice to plan out your answer before writing it in full. A simple storyboard can identify what the evaluator needs to see, which evidence supports each point and how the answer should flow.
Our existing storyboarding guidance explores this approach in more detail. For a tight word count, the basic principle is particularly useful: outline the response using short notes for the requirement, proposed solution, supporting evidence and buyer benefit.
This prevents an early draft from becoming disproportionately weighted towards the sections that happen to be easiest to write. It can also expose gaps while they are still easy to fix. If your plan contains several paragraphs of methodology but no measurable evidence, you know that before investing time in polished prose.
Start with the answer, not the background
Long introductions are one of the easiest places to lose valuable words. Suppose an NHS tender asks how you will maintain service continuity during transition. The buyer does not need a paragraph explaining why continuity is important in a healthcare environment. They already understand the risk. Use those words to explain what you will actually do.
A stronger opening might establish that transition will be managed through phased handover, agreed readiness criteria and enhanced monitoring during the initial go-live period. Within one sentence, the evaluator already understands several elements of the proposed solution.
The same principle applies across other sectors. If the question is about information security, do not spend 100 words explaining that data security is important. If it asks about social value, you do not need to define social value before describing your commitments. Start where the scoring opportunity starts.
Give space to information that can earn marks
When the word count is restrictive, every paragraph should have a clear purpose. In most tender responses, the highest-value content includes specific delivery detail, roles and responsibilities, controls, measurable outcomes, relevant evidence and clear benefits to the buyer. These are the areas where you normally want to protect space.
By contrast, generic statements often use words without adding much substance. Phrases such as “we understand the importance of quality”, “we are committed to excellent customer service” or “we have extensive experience” tell an evaluator very little unless they are followed by something concrete.
An NHS estates supplier does not need to tell the evaluator that maintaining safe access to clinical areas is important. The response is stronger if it explains how access will be planned, who will coordinate with clinical teams and what controls will prevent disruption. The same number of words can either describe an intention or demonstrate a solution.
Use evidence efficiently
A tight word limit is not a reason to remove evidence. Evidence is often what turns a plausible response into a credible one. The solution is to use it selectively and place it alongside the claim it supports.
Instead of inserting a lengthy standalone case study after a section on mobilisation, you might explain that the proposed six-week approach was used successfully on a comparable NHS contract, where the service went live on schedule with all critical readiness criteria achieved. That may be enough to substantiate the point without taking 150 words away from the methodology.
Our guide to using case studies and evidence in NHS tender responses looks more closely at choosing relevant examples and quantifying outcomes. When the word count is tight, the same principles apply, but the evidence needs to be distilled down to the element that directly supports the answer. Avoid telling the entire history of a previous contract when one result is all the evaluator needs.
Replace vague description with specifics
Specific writing can often be both shorter and more convincing. “Robust governance arrangements” sounds positive, but it does not explain anything. Saying that the Contract Director chairs a weekly mobilisation board gives the evaluator a clearer picture using very little additional space.
Likewise, “comprehensive training” is less useful than explaining that all users complete role-specific training before system access is activated. “Regular communication” can become a weekly performance report and monthly contract review.
This matters because vague wording often creates a need for more explanation later. Specifics carry more information in fewer words. Look particularly closely at adjectives such as robust, comprehensive, innovative, proactive and extensive. If the sentence relies on the adjective to make the approach sound good, ask whether you could replace it with evidence of what actually happens.
Use tables and bullets selectively
Tables can be excellent when you need to show parallel information such as risks, responsibilities, milestones or KPIs. For example, a three-column table showing risk, mitigation and owner can communicate a risk-management approach very efficiently. A mobilisation timetable can often show sequencing more clearly than several paragraphs of prose. But tables do not automatically save space. A table filled with long paragraphs simply makes the same amount of content harder to read.
Bullets are similar. They work well for genuinely parallel points, but if every bullet needs several sentences of explanation, normal prose may create a better flow. Always check the buyer’s rules before relying on formatting. If words inside tables count towards the limit, the aim should still be clarity rather than trying to hide extra content.
Avoid repeating the tender question
Repeating the specification can feel like a way to demonstrate understanding, but it often wastes space. If the buyer states that 24/7 support is required, there is little value in beginning with “We understand that the Authority requires 24/7 support.” Use the words to explain how that support will operate: staffing, monitoring, escalation and resilience.
The same applies to tailoring. Using the buyer’s name repeatedly or reproducing their objectives does not automatically make a response buyer-focused. Tailoring is stronger when the delivery model responds to the buyer’s particular circumstances.
If the Trust needs to maintain clinical operations during estates works, show how your programme will accommodate clinical access. If a local authority has identified high staff turnover as a contract risk, explain how your workforce model will address it. That demonstrates understanding without repeating what the buyer has already written.
Be ruthless with repetition
Repeated ideas often survive unnoticed because they appear in slightly different wording. A response might explain the Contract Manager’s role in the opening section, repeat it under governance and then mention the same responsibilities again in the conclusion. One well-written explanation may be enough.
Look for repeated references to:
- company experience
- named roles
- reporting arrangements
- key benefits
- case studies
- buyer objectives.
Where two sections make essentially the same point, combine them and use the recovered words somewhere more valuable. This is particularly important when several contributors have worked on the answer. Each person may independently explain the same process without realising it has already been covered elsewhere.
Don’t cut the useful words first
When a 1,000-word response reaches 1,250 words, the temptation is to start shortening whichever section looks longest. That can lead to evidence, controls and delivery detail being removed while generic introductory material remains untouched.
A better editing order is to start with repetition and unnecessary background. Then simplify long sentences and phrases, consolidate related points and remove weaker or less relevant differentiators. Only after those steps should you consider reducing material that directly addresses a scored requirement.
Sentence-level editing can help, but it should come later. Changing “in order to” to “to” saves two words, while removing a paragraph that tells the buyer something they already know might save 80. The biggest gains usually come from choosing better content, not hunting for individual words.
Leave some headroom during drafting
It can be useful to aim slightly below the maximum during the first controlled draft. If the limit is 1,000 words, reaching 950 rather than exactly 1,000 gives reviewers room to add a stronger example or clarify an important delivery point without forcing another round of major cuts.
There is also no benefit in filling the last 50 words simply because they are available. A concise 930-word response can be stronger than a repetitive 1,000-word one. The word count is a maximum, not a target.
Example: planning a 500-word NHS response
Imagine an NHS tender asks:
Explain how you will maintain continuity of service during mobilisation and transition, including governance, risks and contingency arrangements.
A weak response might use its first 120 words discussing the importance of uninterrupted healthcare services and another 80 describing the bidder’s overall experience. That leaves only 300 words to answer the substantive parts of the question.
A stronger allocation might look like this:
| Content | Approximate words |
|---|---|
| Transition approach and stages | 150 |
| Governance and responsibilities | 90 |
| Continuity controls | 110 |
| Risks and contingency | 100 |
| Relevant evidence and assurance | 50 |
The second approach gives almost the entire word count to material the evaluator can use.
The response could still demonstrate experience, but instead of including a company-history paragraph, it could use a concise piece of evidence within the continuity section. This is a good example of how planning allows you to include more useful information without exceeding the same 500-word limit.
Common mistakes with tight tender word counts
Several problems appear repeatedly when suppliers are under pressure to reduce an answer. These include writing the entire response before deciding what matters, giving every sub-question equal space regardless of weighting, repeating the specification, removing evidence before generic prose, using dense formatting to squeeze in additional text and sacrificing readability for compression.
Another common mistake is using unexplained acronyms simply to save words. An abbreviation may save a few characters, but if it slows the evaluator down or creates ambiguity, the trade-off is not worthwhile.
Review the response through the evaluator’s eyes
Before submission, read the answer once without thinking about the word count. Can you quickly identify the proposed solution? Does every part of the question have an answer? Are responsibilities clear? Can the evaluator see evidence that the approach has worked? Are the important outcomes measurable? Is there anything that sounds impressive but adds little to the score? Then review the word count again.
This order matters. The aim is not simply to produce a short response. It is to produce a response that remains clear, credible and complete despite being short.
Make every word support the score
A strong tender response is not the one that says the most. It is the one that uses the available space to give the evaluator the clearest possible reason to award marks.
That starts with planning. Break down the question, prioritise the scored requirements, select your evidence and decide what deserves space before the prose becomes difficult to cut.
At Bidding, this kind of answer planning forms part of our bid writing and management support. We help suppliers identify what matters most, bring together relevant evidence and turn complex operational information into focused responses that address the buyer’s criteria.
If you already have a draft that is over the limit, our Bid Review and Comment Service can also help identify where content can be tightened without removing the details that give evaluators confidence.
Whether you need help planning the response from the outset or reducing an existing draft, Bidding can help you make the available words work harder.
