How to Structure a Winning Tender Response

6 min readBy Kim FraterPublished 2026-07-27

Kim Frater
Written by Kim Frater
Former Public Sector Buyer • Founder of Bid Trawler • 40+ years' public sector experience
"I believe public procurement shouldn't be complicated. Every guide I write explains the process in plain English so you can bid with confidence."
9 minute read
Updated July 2026

If you've ever stared at a blank page wondering where to start, you're not alone. Writing a tender response can feel overwhelming, especially when you've got a 1,000-word limit and no idea how to use it. The good news is that you don't need to be a professional writer to produce a good response. You just need a clear structure. In this guide, I'll show you how I approach every tender question and why structure matters just as much as the content itself.

Don't Start Writing Straight Away

This might sound strange coming from a bid writer, but one of the biggest mistakes I see is people starting to write too quickly. They read the question. They open a blank document. Then they type whatever comes into their head. The problem is that tender responses rarely come out in the right order that way. Instead, spend a few minutes thinking about what the buyer has actually asked you and the points you want to cover. A few minutes of planning can save you a lot of rewriting later.

Know Who You're Writing For

This is one of the most important things to remember when writing a tender, and it's something I remind myself every time I sit down to write a bid. You're not writing for yourself. You're not writing for your Managing Director. You're writing for the evaluator. That person might have twenty, thirty or even fifty responses to score. The easier you make their job, the easier it is for them to find the marks. Don't make them hunt for your answers.

Read the Scoring Criteria Before You Write

This is something I do before I write a single word. Most tenders don't just give you the question. They also tell you how your answer will be scored.

Don't ignore that!!

If the buyer has included a scoring matrix, read it carefully before you start writing. It tells you exactly what they're looking for. For example, an average score might describe an answer that meets the requirement but provides limited evidence or detail. An excellent score, on the other hand, might require a comprehensive response, supported by relevant examples, clear evidence and a thorough understanding of the buyer's requirements. If you know what a top-scoring answer looks like, that's what you should be aiming to write. When I've finished a response, I always go back to the scoring criteria and ask myself:

  • Does my answer do enough to achieve the highest score?
  • Have I included evidence where it's expected?
  • Have I explained not just what we'll do, but why and how it benefits the buyer?
  • If I were the evaluator, could I honestly justify awarding full marks?

If the answer is no, I know there's still work to do. The scoring criteria is one of the most valuable documents in the tender. Use it.

Start by Actually Answering the Question

It sounds obvious, but it's amazing how many responses don't actually answer the question. Don't begin with three paragraphs about your company. Don't tell the buyer how long you've been trading unless it's relevant. Get straight to the point. If they've asked about mobilisation talk about mobilisation. If they've asked about complaints talk about complaints. Answer the actual question!! So many people don't. Everything else comes afterwards.

Use a Logical Order

Imagine you're explaining something to a new employee on their first day. You wouldn't jump backwards and forwards between different topics. You'd explain it step by step. Tender responses should work the same way. If you're describing a process, write it in the order it happens. If you're explaining your approach, group similar points together. A logical flow makes your response much easier to read.

Break Up Long Blocks of Text

We've all opened a document and been faced with a solid wall of writing. It's hard work. Evaluators feel exactly the same.

  • Use short paragraphs.
  • Use headings where they're allowed.
  • Use bullet points if they help explain something more clearly.
  • Make your response inviting to read.

Tell the Buyer What You'll Do

One thing I often see is suppliers spending most of their word count talking about themselves. What the evaluator really wants to know is:

What are you going to do for us?

Keep bringing your answer back to the contract you're bidding for. Show the buyer you've thought about their needs, not just your own experience.

Back Up Your Claims

If you say you're excellent at something, ask yourself:

How do I know that's true?

Then tell the buyer. That could be through:

  • customer feedback
  • KPIs
  • case studies
  • audit results
  • accreditations
  • performance data

Evidence builds confidence. Without it, you're simply asking the evaluator to take your word for it.

Explain the Benefit

This is probably the biggest difference I notice between average responses and excellent ones. Don't stop at telling the buyer what you'll do. Explain why it matters.

For example, instead of saying:

We carry out monthly audits.

Go one step further:

We carry out monthly audits to identify issues early, maintain consistent service standards and provide opportunities for continuous improvement throughout the contract.

That final sentence explains the benefit. And buyers score benefits.

Keep Checking the Question

When I'm writing a response, I keep going back to the original question. Why? Because it's surprisingly easy to drift off topic. If the buyer has asked three things, make sure you've answered all three. Before you move on, read the question one more time and ask yourself:

Have I actually answered everything they've asked?

Finish Strong

Don't let your response simply stop. Use your final paragraph to reinforce what you've said. Summarise your approach. Remind the buyer of the outcome they'll receive. Leave them with confidence that you've understood the requirement and have a clear plan for delivering it.

My Simple Checklist

Before I submit any response, I quickly ask myself:

  • Have I answered every part of the question?
  • Is the response easy to read?
  • Have I included evidence?
  • Have I explained the benefits?
  • Could an evaluator easily find the marks?

If the answer to all five is yes, I'm usually happy to submit it.

My Final Thoughts

Good tender responses aren't about using clever words or trying to sound impressive. They're about making life easy for the evaluator. A clear, well-structured answer helps the buyer understand exactly what you're proposing and gives them confidence that you know what you're doing.

Whenever you sit down to write a response, remember this:

Your job isn't just to write a good answer. It's to write an answer that's easy to score.

That one change in mindset can make a real difference to the quality of your bids.

Thanks for reading.

I hope this guide has made public procurement a little easier to understand.

Kim Frater
Founder, Bid Trawler

Related guides