A practical operating system for winning public contracts.
Tender evaluators score the evidence submitted against the published criterion. Strong responses provide complete coverage, a credible delivery method, relevant evidence, measurable controls and clear assurance.
Tender evaluators are not looking for the most impressive-sounding company. They are looking for the submission that best answers the published question, satisfies the stated requirements and gives credible confidence that the contract will be delivered. This playbook explains what evaluators usually examine, why strong businesses still lose marks, how scoring decisions are formed and how SMEs can make every response easier to understand, verify and score.
Evaluators score the submitted evidence, not your reputation
An evaluator may know that your business has a good reputation, has worked locally for years or has capable staff. None of that automatically earns marks. The evaluator must assess the content submitted against the published criterion and scoring methodology. Where a claim is missing, vague or unsupported, the evaluator cannot safely fill the gap using assumption.
This is one of the most important lessons for SMEs. Owners often carry a large amount of operational knowledge in their heads and assume the buyer will understand how delivery works. A tender response must make that knowledge visible. It should explain what will happen, who will do it, when it will happen, which controls will apply, how performance will be measured and what evidence supports the approach.
The five tests behind most quality scores
Although wording differs between procurements, many evaluation decisions can be understood through five practical tests:
| Test | Evaluator question | What strong evidence looks like |
|---|---|---|
| Coverage | Has every part of the question been answered? | Headings mirror the question and no sub-part is omitted. |
| Method | Is the delivery approach clear and workable? | Sequence, ownership, systems, controls and escalation are explained. |
| Evidence | Is there proof the supplier can deliver? | Relevant examples, outcomes, data, qualifications and lessons learned. |
| Relevance | Is the answer tailored to this contract? | Buyer requirements, service context, risks and outcomes are addressed directly. |
| Assurance | Does the response reduce delivery risk? | KPIs, governance, contingency, audit and corrective action are credible. |
A polished answer can still score poorly if one of these tests is weak. Conversely, a clear and well-evidenced response from a smaller supplier can outperform a more sophisticated but generic submission.
Complete coverage is the first requirement
Tender questions often contain several embedded requirements. A single paragraph may ask for mobilisation, staffing, supply-chain controls, risk management and reporting. Suppliers frequently answer the main theme but miss one or more sub-questions.
Before drafting, break the question into a response plan. Highlight command words such as describe, explain, demonstrate, provide and confirm. Each verb signals what the evaluator expects. “Describe” normally requires detail about the approach. “Demonstrate” requires evidence. “Provide” may require a document, example or measurable commitment.
Question deconstruction example
Question: Explain how you will mobilise the contract, including governance, staffing, systems, risk controls and communication with the authority.
Required answer structure: mobilisation timetable; governance; named roles; recruitment or transfer arrangements; systems setup; risk register; communication plan; readiness testing; approval and go-live.
Use headings that follow this structure. It helps the evaluator confirm that all required elements are present.
Evaluators need a credible delivery method
A strong response does more than promise an outcome. It explains how the outcome will be achieved. Generic phrases such as “we will ensure high standards” or “we have robust processes” provide little scoring value unless the process is described.
A credible method should normally cover:
- The sequence of activities.
- The people or roles responsible.
- The systems, templates or equipment used.
- Approvals and quality controls.
- Timescales and dependencies.
- Reporting and escalation routes.
- Contingency where the plan does not perform as expected.
Think of the response as a controlled operating procedure rather than a marketing statement. The evaluator should be able to imagine the service being delivered and understand how failures would be identified and corrected.
Specificity creates confidence
Specificity distinguishes a planned response from a generic promise. Compare “we will monitor performance regularly” with “the Contract Manager will review response-time, completion, first-time-fix, complaints and tenant-satisfaction data each week; a monthly dashboard will be issued by the fifth working day and any KPI below target will receive a corrective-action owner and deadline.”
The second statement is stronger because it identifies ownership, frequency, measures, output and action. It is also easier to verify during contract management.
Relevant evidence is more valuable than impressive evidence
Evaluators normally prefer evidence that closely matches the contract requirement. A £20 million national project may sound impressive, but it may be less relevant than a smaller contract involving the same service, customer group, geography and risk profile.
Good evidence explains:
- The client or sector context.
- The scope, scale and complexity.
- Your organisation’s exact role.
- The challenge or risk.
- The action taken.
- The measured outcome.
- The lesson applied to the current procurement.
Evidence statement
On a 1,200-property responsive repairs contract, our scheduling team introduced daily exception reports for overdue and no-access jobs. The Contract Manager reviewed the report at 09:00 each day and allocated recovery actions. Within three months, jobs completed within target increased from 91% to 97.4%, while repeat visits reduced by 12%. We will use the same control from mobilisation on this contract, configured to the authority’s response categories.
Tailoring shows that you understand the requirement
Copy-and-paste answers are easy to recognise. They refer broadly to “the client”, repeat corporate policy and fail to address the actual operating environment. Tailoring does not mean inserting the authority’s name throughout the response. It means adapting the method to the specification, contract terms, geography, service users, risks, volumes and required outcomes.
Before drafting, extract the buyer’s priorities. These may include tenant communication, safeguarding, decarbonisation, local employment, response times, business continuity, data quality or collaboration. Connect your method directly to those priorities.
A useful test is to remove the authority’s name. If the response could be submitted unchanged to ten different procurements, it is not sufficiently tailored.
Evaluators look for ownership
Responses that repeatedly say “we will” often hide who is responsible. Evaluators gain more confidence when named roles, decision rights and escalation paths are clear.
For each important activity, identify:
- The accountable role.
- The operational owner.
- The review or approval role.
- The reporting recipient.
- The escalation point.
A simple responsibility model can be more persuasive than a long narrative. For example, the Bid Director may be accountable for mobilisation, the Mobilisation Manager responsible for the plan, workstream leads responsible for actions, and the Contract Director responsible for final readiness approval.
Risk awareness is a positive, not a weakness
Some suppliers avoid discussing risk because they fear it makes delivery appear uncertain. In reality, evaluators often gain confidence when foreseeable risks are identified and controlled. A response that claims there will be no problems may appear unrealistic.
For each material risk, explain the trigger, likelihood or impact, preventive control, contingency, owner and escalation route. Contract-specific risks might include labour shortages, long-lead materials, access refusals, data migration, seasonal demand, safeguarding incidents or subcontractor failure.
| Risk | Preventive control | Contingency | Owner |
|---|---|---|---|
| Critical material delay | Approved alternatives, supplier lead-time checks and minimum stock levels. | Use pre-approved substitute or re-sequence works with buyer agreement. | Supply Chain Manager |
| High no-access rate | Multi-channel appointments, reminders and tenant liaison. | Escalation list, targeted contact and coordinated access plan. | Resident Liaison Manager |
Measurable controls separate assurance from aspiration
Evaluators want to know how promises will be monitored. A response should identify the measures that show whether delivery is on track. Relevant controls may include response time, completion within target, first-time fix, defects, customer satisfaction, complaints, safety observations, audit results, social value outputs and invoice accuracy.
Do not list KPIs without explaining the management process. State who reviews them, how often, what threshold triggers action, how recovery is recorded and when the authority is informed.
Strong answers connect process to outcomes
Technical detail is important, but evaluators also need to understand why the method benefits the authority and service users. After explaining a process, state the intended outcome. For example, automated appointment reminders are not merely a system feature; they are intended to reduce missed appointments, improve productivity and minimise inconvenience to residents.
Use a simple chain:
This structure prevents responses becoming a catalogue of internal procedures with no clear value to the buyer.
Word limits reward disciplined writing
A word limit is not an invitation to fill every available word with background information. Evaluators value relevant content. Begin with a response plan, allocate space according to the question’s sub-parts and reserve room for evidence and measurable controls.
Remove generic introductions, repeated claims, corporate history and policy descriptions that do not answer the criterion. Use concise headings, short paragraphs, tables where permitted and direct language. Every paragraph should add evidence, method or assurance.
Where attachments are not explicitly requested or permitted, do not assume the evaluator will read them. Put the scoring evidence in the response field.
Weak, acceptable and strong response example
Question
Explain how you will manage service performance and address underperformance.
Weak response
We have robust systems and an experienced management team. Performance will be monitored regularly and any issues will be dealt with quickly.
Why it loses marks: no measures, ownership, frequency, reporting, thresholds or corrective-action process.
Acceptable response
The Contract Manager will review KPIs monthly and report results to the authority. Where performance is below target, an action plan will be agreed and monitored.
Why it may receive a mid-range score: the basic process is present but lacks detail about data, timing, escalation and evidence.
Strong response
Our Contract Manager will review a live dashboard each week covering response time, completion, first-time fix, defects, complaints and satisfaction. A validated monthly report will be issued by the fifth working day. Any KPI below the contractual target will automatically open a corrective-action record stating the cause, action, owner and completion date. Repeated failure for two reporting periods will escalate to the Contract Director and be reviewed with the authority. We used this process on a comparable housing contract and improved completion within target from 92.1% to 97.0% within four months.
Why it scores better: the response provides method, ownership, measures, timescales, escalation, evidence and outcome.
How evaluators use scoring descriptors
Evaluators should apply the published descriptors rather than score according to personal preference. A descriptor may distinguish between a response that is adequate, detailed, comprehensive, evidenced or provides additional confidence. Suppliers should turn the highest descriptor into a review checklist.
Ask:
- Is the response complete?
- Is the method detailed and contract-specific?
- Are claims supported by relevant evidence?
- Are risks and controls credible?
- Are outcomes measurable?
- Does the answer provide the level of assurance described for the top score?
Do not simply insert the words used by the descriptor. The response must demonstrate the qualities, not repeat them.
Moderation and consensus
Many evaluations involve more than one evaluator. Individuals may score independently before meeting to discuss the evidence and agree a moderated or consensus score. The purpose is not to average personal opinions without discussion; it is to reach a defensible final assessment based on the published criterion.
During moderation, clear evidence survives scrutiny. Vague claims are harder to defend. One evaluator may have noticed a useful detail that another missed, but the response should not rely on hidden or difficult-to-find evidence. Strong structure reduces the risk that key content is overlooked.
Where interviews or presentations form part of the published process, the same principle applies: answer the question, provide evidence and avoid introducing unsupported commitments that conflict with the written tender.
Common reasons evaluators limit scores
- A sub-question is not answered.
- The response repeats the specification without explaining delivery.
- Claims are unsupported.
- Examples are old, irrelevant or do not state outcomes.
- Roles and responsibilities are unclear.
- Controls are described as “regular” or “appropriate” without detail.
- Risks are ignored or treated superficially.
- The answer relies on attachments not requested.
- Policies are described but not applied to the contract.
- Commitments conflict with the pricing, programme or contract.
- The response is generic and could belong to any procurement.
- Important evidence is buried in long paragraphs.
Use this list as a red-team review before submission.
What evaluators do not normally reward
Marketing language, awards, years in business and broad statements about quality may support context, but they do not replace a direct answer. Evaluators do not normally award extra marks because a document is visually elaborate, a supplier is locally well known or the response uses complex terminology.
Professional presentation matters because it improves usability, but substance comes first. A simple response with strong evidence will usually outperform an attractive brochure that fails to explain delivery.
Build an evaluator-friendly answer structure
A reliable structure for many method statements is:
- Commitment: state the outcome you will deliver.
- Method: explain the steps and sequence.
- Ownership: identify roles and governance.
- Controls: explain checks, systems and escalation.
- Evidence: provide relevant proof and outcomes.
- Benefit: connect the method to the buyer’s objective.
This structure is not a rigid template. Adapt it to the wording and scoring criteria. The question should determine the answer, not the other way around.
The WPP three-stage review
| Review | Purpose | Questions |
|---|---|---|
| Compliance review | Confirm every requirement is met. | Are all sub-parts answered? Are limits and attachments correct? |
| Evaluator review | Assess the response against the scoring descriptor. | What score is supported by the submitted evidence? What prevents the next score? |
| Commercial review | Confirm commitments are deliverable. | Are resources, targets, programme and pricing aligned? |
Use different reviewers where possible. The author is often too close to the draft to see missing assumptions or unclear wording.
30-day evaluator-readiness plan
- Days 1–5: collect scoring descriptors from previous tenders and build a standard review sheet.
- Days 6–10: create an evidence library with project examples, outcomes, KPIs and client references.
- Days 11–15: document core delivery methods for mobilisation, quality, risk, customer service and performance.
- Days 16–20: identify subject-matter experts and define response ownership.
- Days 21–25: run a mock evaluation on a previous tender response.
- Days 26–30: rewrite the weakest answer using the five evaluation tests and record lessons learned.
Master checklist
- Every question and sub-question has been mapped.
- Headings mirror the buyer’s requirements.
- The method explains sequence, ownership, systems and controls.
- Relevant evidence includes measurable outcomes.
- Contract-specific risks and priorities are addressed.
- KPIs include targets, data sources, owners and review frequency.
- Benefits to the authority and service users are explicit.
- The response meets the published scoring descriptor.
- Commitments align with the price, programme and contract.
- A compliance, evaluator and commercial review has been completed.
Frequently asked questions
Do evaluators read every word?
They should assess the complete response, but suppliers should still make evidence easy to locate. Dense, repetitive writing increases the risk that key information is misunderstood or overlooked.
Can evaluators use previous experience of my company?
Evaluation should follow the published criteria and submitted evidence. Do not rely on prior relationships or reputation unless the procurement expressly assesses past performance through a stated method.
Should I repeat the specification?
No. Confirm understanding where useful, then explain how you will meet the requirement. Repetition consumes space without adding method or evidence.
How much evidence is enough?
Use enough relevant evidence to support the claim. One detailed, comparable example with measured outcomes can be stronger than several vague examples.
Do local suppliers receive extra marks?
Only where the published criteria lawfully evaluate relevant outcomes. Local presence alone should not be assumed to attract marks.
Can attractive design improve the score?
Good presentation can improve clarity, but it cannot replace substantive evidence. Follow all formatting rules and prioritise evaluator usability.
What if the question is ambiguous?
Raise a clarification before the deadline. Do not build a response around an assumption that materially affects the offer.
Should we promise more than the specification asks for?
Only where it creates relevant value and is deliverable. Unnecessary commitments can increase cost and contractual risk without improving the score.
What is the best way to predict a score?
Use the buyer’s exact descriptors and ask an independent reviewer to identify the evidence supporting each level. Treat the result as quality control, not a guarantee.
Why did a detailed answer still score poorly?
Length is not the same as relevance. The response may have omitted a sub-question, lacked evidence, remained generic or failed to meet the top descriptor.
Turn the guidance into action
Use the WPP Procurement Toolkit™ to test readiness, review response strength and make a structured bid decision.
Strengthen a live tender with a professional WPP review.
We review completed submissions for compliance, structure, evidence and alignment with the published evaluation criteria.
Discuss your tender