How to Review a Tender Before You Submit It
- Claire Hilton
- 4 days ago
- 11 min read
A tender review should do far more than spot spelling mistakes.
Done properly, it should test whether your submission answers the question, meets the requirements, reflects the buyer’s priorities and gives evaluators enough confidence to award you the marks.
Done badly, it becomes a frantic group proofreading exercise shortly before the submission portal closes.
At that point, someone is changing the opening paragraph, someone else is questioning the font and nobody has checked whether the additional staffing promised in the method statement has actually been included in the price.
A good review process brings structure, challenge and judgement to the submission. It helps you identify weak answers while there is still time to improve them, rather than simply making poor answers look tidier.
Why tender reviews matter
Even experienced teams can become too close to their own submission.
Writers know what they meant. Operational colleagues understand the service. Senior leaders know the organisation’s history. Unfortunately, the evaluator only knows what appears on the page.
A robust review helps you check whether the tender:
Answers every part of the question
Meets all mandatory requirements
Reflects the buyer’s stated priorities
Provides credible evidence
Explains how the service will be delivered
Demonstrates clear benefits and outcomes
Is affordable and commercially sustainable
Reinforces the key reasons the buyer should choose you
Is easy for an evaluator to understand and score
The purpose is not to make the writing sound more impressive. It is to make the response clearer, stronger and easier to award marks to.
Do not leave the review until the end
One of the biggest mistakes organisations make is waiting until every answer is complete before reviewing the submission.
By then, deadlines are tight and people are tired. There may be little time to address gaps in the delivery model, obtain missing evidence, resolve conflicting information or amend a price that no longer reflects what has been promised.
Reviews should take place throughout the tender process.
Review the response plan
Before drafting begins, check the proposed structure for each answer.
Does it address every part of the question? Does it reflect the evaluation criteria? Have the golden threads and win themes been identified? Have you agreed what evidence, examples and data will be needed?
This early review can prevent a writer spending hours producing an answer that was heading in the wrong direction from the start.
It also gives the team an opportunity to test whether the proposed solution is deliverable and whether the likely cost implications have been understood before commitments start appearing in the narrative.
Review the first draft
The first draft review should focus on substance rather than sentence-level editing.
Ask:
Has the question been answered fully?
Is the proposed approach credible?
Are roles, responsibilities and timescales clear?
Are claims supported by evidence?
Does the answer explain the benefit to the buyer and service users?
Does anything promised create a new cost or resource requirement?
Are the agreed win themes visible and supported?
Is anything important missing?
This is the point to challenge the content. There is little value in polishing a beautifully written answer that lacks detail, cannot be delivered for the proposed price or fails to respond to the question.
Complete a final submission review
The final review should confirm that the tender is complete, consistent and ready to submit.
It should check compliance, attachments, word counts, formatting, naming conventions and portal requirements. It should also identify any remaining errors, contradictions or unclear statements.
Before approval, complete a cross-check between the written responses, delivery model and pricing schedule. Confirm that every material promise is affordable and that the agreed golden threads are visible, credible and consistent throughout the submission.
This final check matters, but it should not be expected to rescue fundamental weaknesses that should have been addressed earlier.
Use the right reviewers
More reviewers do not automatically produce a better tender.
Too many people can create conflicting feedback, unnecessary rewriting and lengthy discussions about personal preferences. Everyone has an opinion about wording. Not every opinion improves the score.
Choose reviewers according to what needs to be tested.
Subject specialists
Operational and technical colleagues can confirm whether the proposed approach is accurate, realistic and deliverable.
They should check the detail, not simply say that the answer ‘looks fine’.
Commercial and finance colleagues
Commercial and finance reviewers should examine pricing assumptions, financial risks, mobilisation costs and any commitments that could affect delivery.
They should also check whether changes made during drafting have introduced new costs. An additional meeting, reporting requirement, training commitment or service enhancement may seem minor in isolation, but these promises quickly add up.
A strong quality submission paired with an unsustainable price is not a successful tender.
Senior and strategic reviewers
A senior reviewer can test whether the submission presents a coherent offer and aligns with the organisation’s strategy, risk appetite and capacity.
Their role is not to rewrite every sentence. It is to identify major weaknesses, inconsistencies or risks.
A fresh reader
Someone who has not been heavily involved in writing the tender can be particularly valuable.
They are more likely to notice unexplained terminology, missing information or assumptions that the core team has stopped seeing.
Review against the scoring criteria
Do not review a tender according to whether you personally like the writing.
Review it against the question, evaluation criteria and scoring guidance.
A useful review should consider seven connected areas.
1. Compliance
Check that the submission meets every instruction.
This includes:
Mandatory requirements
Word or character limits
Required attachments
File formats
Formatting instructions
Declarations and signatures
Submission deadlines
Portal requirements
Compliance may not win the tender, but non-compliance can certainly lose it.
2. Relevance
Every paragraph should help answer the question.
Background information about your organisation may feel important, but it should only be included where it adds value to the response. Evaluators do not award marks for everything you know. They award marks against the published criteria.
Remove generic statements that could appear in any bidder’s response.
3. Evidence
Claims need proof.
If the tender says your organisation delivers excellent outcomes, the evaluator should not be expected to take your word for it.
Use relevant evidence such as:
Performance data
Contract results
Case studies
Customer or service user feedback
Audit findings
Quality standards
Independent evaluation
Examples from comparable services
Evidence should be specific enough to build confidence and relevant enough to support the point being made.
4. Delivery detail
Strong tender responses explain how the service will work in practice.
Look for clear information about:
Activities
Roles and responsibilities
Timescales
Resources
Governance
Performance management
Risk
Quality assurance
Escalation
Continuous improvement
Phrases such as ‘we will work collaboratively’ or ‘we will maintain regular communication’ are not enough on their own. The answer must explain what that means in practice.
5. Cost and commercial implications
Every promise made in a tender has the potential to carry a cost.
During the review, someone needs to test whether anything added to the narrative or delivery model creates an expense that has not been reflected in the price.
This is particularly important when responses are strengthened during the writing and review process. A helpful operational suggestion can quickly become a contractual commitment. Additional staff, enhanced reporting, new technology, more frequent meetings or an ambitious social value offer may sound compelling, but someone will need to pay for them.
Reviewers should look carefully at commitments relating to:
Staffing numbers, grades and working hours
Management and supervision
Training and professional development
Mobilisation activity
Technology, licences and equipment
Data collection and reporting
Travel and venue costs
Subcontractors and delivery partners
Quality assurance and audit activity
Communications and engagement
Social value commitments
Contingency and risk management
The question is not simply whether an idea would improve the tender. It is whether it is affordable, deliverable and included within the pricing model.
The quality submission, delivery model and financial submission should tell the same story. If the narrative promises a level of service that the price cannot support, the organisation may win a contract it cannot deliver sustainably.
That is not a successful bid. It is a future problem wearing a party hat.
Ask:
Has this activity been costed?
Is the necessary resource included?
Does it affect our assumptions, margin or cash flow?
Are we committing to something beyond the buyer’s requirements?
Could the wording create an unintended contractual obligation?
Can we deliver this throughout the full contract term, not just during mobilisation?
This check should happen whenever the delivery model changes, not only at the end of the process.
6. Buyer benefit
The tender should not only describe what you will do. It should show why your approach matters to the buyer, service users and wider stakeholders.
Reviewers should be able to identify the benefit of each major feature.
Will the approach reduce risk? Improve outcomes? Increase accessibility? Deliver savings? Strengthen reporting? Improve the experience of service users?
Do not make the evaluator work out the benefit for themselves.
7. Golden threads and win themes
A strong tender should have a small number of clear messages running through the entire submission.
These are often described as golden threads or win themes. They explain why your solution is particularly well suited to the buyer, the contract and the people the service is intended to support.
A win theme might focus on:
A strong understanding of the local area
A proven delivery model
Lower mobilisation risk
Better outcomes for service users
An experienced and stable workforce
Strong partnership arrangements
Better use of data and insight
Greater accessibility or inclusion
Added social value
Continuous improvement
These themes should be identified before drafting begins and tested throughout the review process.
They should not appear once in the executive summary and then disappear. They should be supported across the delivery model, mobilisation plan, workforce approach, quality arrangements, risk management, performance framework and social value offer.
The aim is not to repeat the same slogan in every answer. That quickly becomes obvious and irritating.
Instead, each theme should be evidenced in different ways.
For example, if one of your win themes is low-risk mobilisation, the submission might reinforce this through:
A named and experienced mobilisation lead
A detailed implementation timetable
Early engagement with stakeholders
Clear governance and escalation routes
Tested data transfer arrangements
Workforce continuity planning
Evidence from similar contract transitions
The review team should check whether the golden threads are:
Relevant to the buyer’s priorities
Distinctive enough to differentiate your offer
Supported by credible evidence
Reflected consistently throughout the submission
Reinforced through the delivery model and pricing
Clear without becoming repetitive
A useful final review question is:
If the evaluator remembered only three things about our submission, what would we want those three things to be?
Then check whether the tender actually makes those messages clear.
Give feedback that improves the answer
Comments such as ‘needs more detail’, ‘not strong enough’ or ‘make this more persuasive’ are not especially helpful.
Good review feedback should explain:
What is missing
Why it matters
What needs to change
Where supporting information might be found
For example:
The answer states that staff will receive training, but it does not explain who will deliver it, when it will happen or how competence will be assessed. Add the training timetable, delivery method and quality assurance process. Confirm that the cost and staff time are included in the financial model.
That gives the writer something clear to act on.
Reviewers should also distinguish between essential changes and personal preferences.
A tender does not need to sound as though every reviewer wrote it.
Protect the writer from conflicting feedback
Where several people are reviewing a submission, appoint one person to manage the comments and make final editorial decisions.
Otherwise, the writer may receive contradictory instructions from different colleagues, each of whom believes their change is urgent.
The review lead should:
Resolve conflicting comments
Prioritise changes
Protect the agreed response strategy
Maintain the golden threads
Prevent unnecessary rewriting
Check that changes do not create uncosted commitments
Confirm when an answer is complete
Clear ownership keeps the process moving and avoids death by committee.
Use technology carefully
Shared documents, tracked changes and project management systems can make collaboration easier.
They can also create chaos when ten people are editing the same answer at once.
Set clear rules about:
Who can edit
Who should comment
How feedback will be resolved
Which document is the master version
When editing will close
Who approves the final response
Technology supports the review process. It does not replace good management.
Common tender review mistakes
Reviewing too late
A final proofread cannot fix a weak delivery model, missing evidence, an unanswered question or a price that no longer reflects the offer.
Focusing only on grammar
Good grammar matters, but a polished response can still score poorly if it lacks substance.
Failing to test the cost of new ideas
An impressive new commitment may improve an answer, but it may also require more people, time, technology or management resource.
Every material change should be checked against the price.
Losing the golden threads
Answers written by different people can become individually competent but collectively forgettable.
The final review should ensure that the tender still communicates a small number of clear, consistent and evidenced reasons to choose your organisation.
Allowing seniority to override the question
A late comment from a senior colleague should not automatically trigger a complete rewrite. Test every proposed change against the question, scoring criteria, delivery model and price.
Rewriting in different voices
Repeated editing by several people can leave the tender sounding disjointed. One person should complete the final edit to create a consistent voice.
Adding content without removing anything
Reviews often make answers longer. When word counts are tight, every addition should prompt a decision about what can be cut.
Assuming the evaluator understands
Avoid unexplained acronyms, internal terminology and vague references to existing systems. Write for an informed reader who knows nothing about your organisation.
A seven-part tender review test
A robust tender review should examine seven connected areas:
Compliance: Have we followed every instruction?
Relevance: Have we answered the question asked?
Evidence: Have we proved our claims?
Delivery: Have we explained how it will work?
Commercial viability: Have we costed everything we have promised?
Buyer benefit: Have we made the value of our approach clear?
Golden threads: Have we consistently reinforced the reasons the buyer should choose us?
These elements cannot be reviewed in isolation.
The most persuasive delivery model in the world is no use if it is unaffordable. A beautifully costed proposal will not win if the evaluator cannot see what makes it distinctive. Strong win themes will not rescue an answer that lacks evidence.
The review must test whether the entire submission works as one coherent, credible and commercially deliverable offer.
Learn from every submission
The review process should not end when the tender is submitted.
Record what worked, what caused delays and what information was difficult to obtain.
When evaluator feedback arrives, compare it with your own review comments.
Did the evaluator identify a weakness your team had missed? Was a strength recognised? Were marks lost because the answer lacked evidence, detail or clarity? Did your stated win themes register with the buyer?
These lessons should feed into future submissions, your bid library and your wider business development process.
A strong review is an act of judgement
Tender reviews are not about making every sentence perfect.
They are about deciding whether the submission gives the evaluator what they need to award the score and whether your organisation can afford to deliver what it has promised.
That requires structure, honesty and a willingness to challenge weak content before it reaches the buyer.
The best question a reviewer can ask is not:
‘Do I like this answer?’
It is:
‘Could an evaluator award full marks based on what we have written and could we deliver it sustainably for the price submitted?’
If the answer is no, the review has done its job. The next step is to make the response stronger.
Need an experienced pair of eyes?
When you have been living and breathing a tender, it can be difficult to see what is missing.
The Bid Edit provides independent tender reviews that test compliance, clarity, evidence, delivery detail, commercial viability and evaluator appeal. We will identify where the submission is strong, where it is vulnerable and what needs to change before you press submit.
Because reassurance is pleasant. A stronger score is better.
Comments