How to Write a Winning Tender Response: Structure, Common Mistakes, and What Evaluators Look For

Most tender bids are decided before anyone reads your pricing. Evaluators score your technical response first — your understanding of the problem, your proposed approach, and the evidence you provide. Here’s how to structure a response that scores well, and the mistakes that cost businesses contracts they should have won.

Before you write a word: read the tender document properly

This sounds obvious, but it’s where most failed bids go wrong. A tender document (whether it’s called an RFP, ITT, RFQ, or solicitation) tells you exactly what the buyer wants and exactly how they’ll score your response. Every word of your bid should be written to match those scoring criteria.

Here’s what to extract before you start writing:

• Evaluation criteria and weightings. These are usually published in the tender document. If technical quality is weighted 60% and price is 40%, your technical response matters more than being the cheapest. Some tenders use pass/fail on price and score only on quality.
• Mandatory requirements. These are non-negotiable. If the tender says “must hold ISO 27001 certification,” and you don’t, stop here. A missing mandatory requirement means automatic disqualification in most jurisdictions.
• Word or page limits. Government evaluators read dozens of bids. Exceeding the word limit usually means your extra content won’t be read, or worse, your bid is rejected outright.
• Submission format. PDF or Word? Online portal or email? Separate technical and financial envelopes? Getting the format wrong can disqualify you before your bid is even opened.

The single most valuable thing you can do is build a compliance matrix — a spreadsheet that maps every requirement in the tender document to where you’ve addressed it in your response. If there’s a gap, you’ll spot it before submission, not after rejection.

The anatomy of a tender response

Every tender is different, but most government bids follow a similar structure. Here’s what evaluators expect to see, in roughly the order they expect to see it.

1. Executive summary

One to two pages. This is your pitch to the person who reads 30 bids in a week and remembers three. State who you are, what you’re proposing, why your approach is the right one, and one or two headline differentiators. Don’t waste this section on your company history — the evaluator doesn’t care about your founding year. They care about why you’re the safest choice for this contract.

2. Understanding of requirements

This is where you prove you actually read the brief. Restate the buyer’s problem in your own words, demonstrating that you understand not just what they’ve asked for, but why they’re asking for it. The best responses go beyond the written requirements and show awareness of the broader context — regulatory changes, stakeholder pressures, or operational constraints that the buyer is dealing with.

3. Technical approach / methodology

This is usually the highest-weighted section. Describe how you’ll deliver what the buyer needs, step by step. Be specific: name the tools, frameworks, standards, and processes you’ll use. Include timelines, milestones, and deliverables.

What separates a 3/5 response from a 5/5:

• 3/5: “We will implement a project management methodology to ensure timely delivery.”
• 5/5: “We use PRINCE2 with fortnightly sprint reviews. Each sprint produces a deliverable summary shared via your preferred project portal. Our PM assigns a RAG status to every workstream; any amber or red item triggers a remediation plan within 48 hours, escalated to [named role] if unresolved within one sprint cycle.”

The difference is specificity. The first answer could appear in any bid for any contract. The second tells the evaluator exactly what will happen, when, and what their safety net looks like.

4. Team and key personnel

Name the people who will do the work. Include their qualifications, relevant experience, and their specific role on this contract. Evaluators score named individuals higher than “we will assign a suitably qualified team member.”

If your team includes subcontractors or consortium partners, be transparent about who does what. Hiding subcontractor involvement and having it discovered during evaluation is far worse than disclosing it upfront.

5. Relevant experience and case studies

This is your evidence section. Provide two to four case studies of similar work you’ve delivered, structured as: situation (what the client needed), approach (what you did), outcome (measurable results). Government evaluators look for three things in case studies: similar scale, similar sector, and recent delivery (ideally within the last three to five years).

6. Risk management

Identify the top risks to successful delivery and explain how you’ll mitigate each one. This shows the evaluator that you’ve thought beyond the happy path. Common risks to address: key-person dependency (what happens if your lead engineer leaves), supply chain disruption, technology failure, and scope creep.

A risk register formatted as a table — risk, likelihood, impact, mitigation, owner — scores better than prose alone, because it shows you have a systematic approach rather than an ad hoc one.

7. Social value and sustainability

This is increasingly weighted in government procurement, especially in the UK (where social value can carry 10–20% of the total score under the Social Value Model), the EU, and Australia. Common social value commitments include: local hiring, apprenticeships, environmental impact reduction, SME subcontracting, and community engagement.

Be specific and measurable. “We are committed to sustainability” scores zero. “We will source 30% of materials from local SMEs within 50km, reducing transport emissions by an estimated 15%, and offer two paid apprenticeship positions for the duration of the contract” scores well.

8. Pricing schedule

Most government tenders separate the technical response from the pricing response — often in sealed envelopes or separate portal uploads. This prevents evaluators from being influenced by price when scoring quality.

Pricing rules to follow:

• Use the buyer’s pricing template exactly. If they provide a spreadsheet with specific line items, fill in every cell. Don’t restructure it to match your internal cost model.
• Show your working. Break costs into components: labour (by role and day rate), materials, travel, overheads, and margin. A single lump sum with no breakdown looks opaque and makes evaluators nervous.
• Don’t lowball. An unrealistically low price raises a red flag. Evaluators in most jurisdictions are trained to check for “abnormally low tenders” and may ask you to justify your pricing. If you can’t, the bid can be rejected on the grounds that delivery at that price is not credible.
• Include all costs. Hidden costs discovered mid-contract damage the relationship and your reputation. If there are optional or contingency items, present them separately and clearly.

How evaluators actually score your bid

Government procurement evaluation follows a structured process designed to be fair, transparent, and auditable. Understanding this process changes how you write.

In a weighted criteria model (the most common worldwide), a typical scoring scale looks like this:

The jump from 3 to 5 is almost always about specificity and evidence. Generic claims (“we have extensive experience”) score 2–3. Specific, evidenced statements (“we delivered a similar contract for [named client] in 2024, completing three weeks ahead of schedule with 99.7% SLA compliance”) score 4–5.

Evaluators score what’s on the page. They cannot give you credit for experience they suspect you have but you haven’t written down. If it’s not in the response, it doesn’t exist.

The compliance matrix: your most important tool

A compliance matrix is a table that maps every requirement in the tender document to your response. It serves two purposes: it ensures you haven’t missed anything, and it makes the evaluator’s job easier (which earns goodwill, whether or not it’s officially scored).

A simple compliance matrix has four columns:

• Requirement reference — the clause number from the tender document
• Requirement summary — what the buyer is asking for
• Compliance status — Fully Compliant, Partially Compliant, or Non-Compliant (with explanation)
• Response reference — the page/section in your response where you address it

Some tender documents require you to submit a compliance matrix. Even when they don’t, building one internally catches gaps that would otherwise cost you points. In US federal procurement, the compliance matrix maps Section L (instructions) to Section M (evaluation criteria), ensuring every evaluation factor has a corresponding answer.

Seven mistakes that cost you the contract

1. Not answering the question asked. If the evaluator asks “describe your approach to quality assurance,” don’t describe your company’s history. Answer the specific question, in the order it’s asked, using their terminology.

2. Writing for your colleagues instead of the buyer. Your internal jargon and acronyms mean nothing to the evaluation panel. Write in plain language. If the buyer uses specific terms in the tender document, mirror those terms in your response.

3. Making claims without evidence. “We are an industry leader in …” — prove it. Every claim needs evidence: a case study, a statistic, a certification, a client reference. Unsupported claims actively harm your score because they signal that you don’t have evidence to offer.

4. Ignoring page or word limits. A 15-page response to a 10-page limit won’t get the extra 5 pages read. In many jurisdictions, the evaluator is required to stop reading at the stated limit. Exceeding it wastes your best content.

5. Submitting a generic response. Evaluators can tell when a response has been copied from a previous bid. References to the wrong buyer name, wrong contract title, or wrong country are embarrassingly common — and result in immediate low scores.

6. Pricing without strategy. Your price should reflect your costs plus a reasonable margin, not a number plucked from the air or calculated to undercut competitors. Abnormally low pricing triggers scrutiny in most jurisdictions (the EU Public Procurement Directive, for instance, requires contracting authorities to investigate tenders that are “abnormally low” relative to the estimated contract value).

7. Leaving submission to the last hour. Portal crashes, file upload errors, time zone confusion, and email delivery failures have all killed bids that would have won. Best practice is to submit 24–48 hours before the deadline, then verify confirmation of receipt.

A practical writing process

Once you’ve decided to bid (using a go/no-go framework), here’s a step-by-step writing process that works:

1. Day 1–2: Read and analyse. Read the entire tender document twice. Build your compliance matrix. List every question you need to answer and every document you need to provide.
2. Day 2–3: Plan your answers. For each scored criterion, outline what you’ll say, what evidence you’ll cite, and which team member will draft it. Assign ownership.
3. Day 3–10: Write drafts. Each section owner writes their part. Keep a shared document so everyone can see progress. Write to the word limit from the start — don’t write 5,000 words and try to cut to 2,000 later.
4. Day 10–12: Internal review. Someone who hasn’t written the response reads it as an evaluator would. Do they understand the approach? Is every claim evidenced? Does it answer every question? Check against the compliance matrix.
5. Day 12–13: Final polish. Formatting, consistency, proofreading. Make sure headers match the tender document structure. Check that all attachments and declarations are included.
6. Day 13: Submit. Upload or send with at least 24 hours to spare. Confirm receipt.

For a typical 2–3 week tender window, this timeline gives you enough room to write well without rushing. Shorter deadlines compress the middle stages but should never compress the analysis phase — a well-analysed tender document saves more time than it costs.

After submission: debriefs and continuous improvement

In most jurisdictions, unsuccessful bidders have the right to request a debrief. Take every debrief offered. The evaluator will tell you your scores, how you compared to the winner, and what would have improved your bid. This is free consultancy that directly improves your next submission.

Keep a bid library: a collection of your best answers, case studies, CVs, and compliance evidence, organised by topic. Over time, this library dramatically reduces the effort of each new bid. The first tender response takes 80+ hours. By your tenth, you’re reusing 60% of the content and spending your time on the bespoke parts that actually differentiate you.