Every year, UK design and digital agencies lose millions of pounds worth of public sector contracts not because their work isn't good enough — but because their tender responses aren't.
Procurement evaluators score responses against strict criteria. They're not looking for the most creative portfolio. They're looking for the clearest evidence that you can do what the buyer needs, within budget, on time, with minimal risk to them.
Most agencies apply the same instincts they use for private sector pitches — leading with personality, design philosophy, and case studies. These instincts rarely translate. This guide explains what evaluators actually want, and how to write responses that win.
What evaluators are looking for
Public sector tender evaluations are structured. Each section has a maximum score. Evaluators award marks based on evidence against the specification — not on the overall impression your submission creates.
The typical scoring framework looks like this:
- Technical capability / approach: How you'll deliver the work (30–40% of total score)
- Relevant experience: Evidence you've done comparable work (20–30%)
- Team and capacity: Who will do the work and whether they're available (15–20%)
- Price: Your fee against budget (20–30%)
- Social value: Your commitment to wider social impact (10–20%)
Some contracts weight price heavily. Others — particularly in design and digital — weight technical quality more. Always check the weighting in the tender documents before deciding how much effort to invest.
The key insight: your response needs to score well in each section individually. A brilliant technical proposal won't compensate for a weak social value section if social value is weighted at 20%.
Before you write a word: qualify the opportunity
Not every tender is worth responding to. The cost of writing a bid — including staff time — can easily reach £3,000–£8,000 for a complex response. You need to be selective.
Ask these questions before committing:
Can you deliver this?
Does the scope match your genuine capability? If you'd need to hire or partner to deliver, factor that in. Evaluators can tell when an agency is stretching to fit a brief.
Have you done similar work?
Evaluators want evidence. If you can't point to at least two comparable projects, your experience section will be weak regardless of how well you write it.
Is the budget realistic?
If the published budget is £80,000 and you know from experience this scope costs £150,000 to deliver properly, the maths don't work. Competing on an underfunded contract rarely ends well.
Do you know the buyer?
Buyers often have existing relationships and preferences. If an agency has delivered for a council for five years, they're likely to be re-appointed unless you offer something clearly differentiated.
If you pass this qualifying check, proceed. If not, pass on this one and invest that time in finding better-fit opportunities.
The five sections you need to get right
1. Technical approach
This is usually the highest-weighted section and the one agencies most often write poorly.
Evaluators want to understand how you'll deliver the work, not just that you can. The difference matters:
Weak: "We take a user-centred approach to all design projects, running discovery workshops to understand stakeholder needs before moving into prototyping and iteration."
Every year, UK design and digital agencies lose millions of pounds worth of public sector contracts not because their work isn't good enough — but because their tender responses aren't.
Procurement evaluators score responses against strict criteria. They're not looking for the most creative portfolio. They're looking for the clearest evidence that you can do what the buyer needs, within budget, on time, with minimal risk to them.
Most agencies apply the same instincts they use for private sector pitches — leading with personality, design philosophy, and case studies. These instincts rarely translate. This guide explains what evaluators actually want, and how to write responses that win.
What evaluators are looking for
Public sector tender evaluations are structured. Each section has a maximum score. Evaluators award marks based on evidence against the specification — not on the overall impression your submission creates.
The typical scoring framework looks like this:
- Technical capability / approach: How you'll deliver the work (30–40% of total score)
- Relevant experience: Evidence you've done comparable work (20–30%)
- Team and capacity: Who will do the work and whether they're available (15–20%)
- Price: Your fee against budget (20–30%)
- Social value: Your commitment to wider social impact (10–20%)
Some contracts weight price heavily. Others — particularly in design and digital — weight technical quality more. Always check the weighting in the tender documents before deciding how much effort to invest.
The key insight: your response needs to score well in each section individually. A brilliant technical proposal won't compensate for a weak social value section if social value is weighted at 20%.
Before you write a word: qualify the opportunity
Not every tender is worth responding to. The cost of writing a bid — including staff time — can easily reach £3,000–£8,000 for a complex response. You need to be selective.
Ask these questions before committing:
Can you deliver this?
Does the scope match your genuine capability? If you'd need to hire or partner to deliver, factor that in. Evaluators can tell when an agency is stretching to fit a brief.
Have you done similar work?
Evaluators want evidence. If you can't point to at least two comparable projects, your experience section will be weak regardless of how well you write it.
Is the budget realistic?
If the published budget is £80,000 and you know from experience this scope costs £150,000 to deliver properly, the maths don't work. Competing on an underfunded contract rarely ends well.
Do you know the buyer?
Buyers often have existing relationships and preferences. If an agency has delivered for a council for five years, they're likely to be re-appointed unless you offer something clearly differentiated.
If you pass this qualifying check, proceed. If not, pass on this one and invest that time in finding better-fit opportunities.
The five sections you need to get right
1. Technical approach
This is usually the highest-weighted section and the one agencies most often write poorly.
Evaluators want to understand how you'll deliver the work, not just that you can. The difference matters:
Weak: "We take a user-centred approach to all design projects, running discovery workshops to understand stakeholder needs before moving into prototyping and iteration."
Strong: "Our proposed approach for this contract is a 10-week discovery and alpha phase. Weeks 1–2: stakeholder interviews with [named roles from the spec]. Weeks 3–4: user research with [target user group from spec]. Weeks 5–7: three rounds of co-design workshops, producing prioritised problem statements. Weeks 8–10: low-fidelity prototypes tested with [number] users, with a recommendation report for the client."
The strong version is specific to this contract. It references details from the specification. It tells the evaluator exactly what will happen and when.
The rule: read the specification thoroughly, then write an approach that could only have been written for this buyer, this project, this brief.
2. Relevant experience
Most agencies attach PDF case studies and call it done. Evaluators score experience by looking for evidence that you've solved a comparable problem at comparable scale for comparable clients.
Structure each case study to answer three questions:
- What was the problem or brief?
- What did you specifically do (not "we" — what you contributed)?
- What was the measurable outcome?
Aim for 2–3 case studies that closely match the brief. If you have a direct public sector reference — ideally from a similar type of buyer (e.g., NHS, local government, central government) — lead with it.
If you don't have directly comparable experience, acknowledge it briefly and explain why your related experience transfers. Don't pretend you've done something you haven't — evaluators often request references.
3. Team and capacity
Name the people who will work on this contract. Provide brief CVs (1 paragraph per person) that highlight relevant experience. State their availability — as a percentage of their time — for each phase of the project.
Evaluators want to know that the people who win the work are the people who will do the work. Generic "our team" language raises red flags. If you're planning to subcontract any specialist element, name the subcontractor and explain the governance arrangements.
4. Price
Don't lead on price being your competitive advantage unless the contract is purely price-driven (rare in design and digital).
Break your pricing down clearly: day rates by role, number of days per phase, expenses policy, assumptions and exclusions. Clarity reduces perceived risk. Evaluators get nervous about vague lump sums.
If there's a published budget and your fee comes in under it, don't simply charge less — explain why. "Our approach requires fewer discovery days because we're proposing to use [specific methodology] rather than [standard alternative]." This is more credible than an unexplained low number.
5. Social value
Since PPN 06/20, social value is mandatory at 10% minimum weighting for most central government contracts, and many local authorities have adopted the same standard.
Evaluators score social value on specificity and local relevance. Generic commitments ("we support diverse suppliers") score poorly. Specific, measurable, locally anchored commitments score well.
Examples of strong social value commitments for design agencies:
- "We will offer two paid work placement weeks to students from [local school/college] during this contract"
- "We will pay the Real Living Wage to all staff and subcontractors working on this project (currently £13.15/hour)"
- "We will hire one apprentice in UX research during the contract period, supported by our Apprenticeship Levy account"
Match your commitments to what you can actually deliver. Evaluators often follow up post-award on social value commitments. Overpromising creates problems.
Common mistakes that cost agencies points
Answering a different question. Read each question carefully and answer what's actually being asked. "Describe your approach to user research" is not an invitation to explain your agency's philosophy — it's asking what you will do on this project.
Assuming the evaluator knows your work. Don't reference a case study without explaining what it demonstrates. Don't name a client without saying what you did for them. Assume the evaluator knows nothing about you.
Using passive voice. "Users will be engaged through a series of workshops" is weaker than "We will run six workshops with [specific users]." Active, specific language scores better.
Ignoring the word limit. If a section has a 1,000-word limit, submit exactly 1,000 well-chosen words. Shorter suggests insufficient detail; longer demonstrates inability to follow instructions.
Leaving submission to the last minute. Most UK public sector portals (Jaggaer, ProContract, Delta) have quirks. Files have size limits. Form fields don't paste well. Allow two days before deadline to handle technical issues.
The step you can't skip: finding the right opportunities
A well-written tender response wins nothing if you're applying to the wrong opportunities — or missing the right ones entirely.
The challenge for most agencies is the monitoring problem. UK public sector contracts are fragmented across Contracts Finder, Find a Tender Service, NHS Supply2Health, council procurement portals, CCS frameworks (DOS7, TS3, G-Cloud), and dozens of regional equivalents. Manually checking them daily isn't realistic for a busy BD function.
Agencies that consistently win public sector work solve the monitoring problem first. They know about relevant opportunities before competitors do, which gives them time to qualify properly, write strong responses, and build context about the buyer before submission.
That's the problem Tandara is built to solve. Our service monitors UK procurement portals daily, filters by relevance to design and digital agencies, and delivers the opportunities that match your profile directly to your inbox — so you can focus on writing winning bids rather than hunting for them.
Start your free 14-day trial at tandara.co.uk — no credit card required.
Summary
Winning public sector tenders as a design agency comes down to a small number of repeatable practices:
- Qualify rigorously — only bid on work you can genuinely win
- Write specifically — reference the brief, the buyer, the spec in every section
- Lead on approach — show exactly how you'll deliver, not just that you can
- Match your experience — find the closest comparable work and make the connection explicit
- Take social value seriously — it's worth 10–20% and most agencies still treat it as an afterthought
- Monitor systematically — you can't win what you don't know about
The agencies that build consistent public sector revenue treat tendering as a process, not an event. They invest in the monitoring infrastructure, the case study library, and the internal response templates that let them compete at scale.
Tandara monitors UK public procurement portals daily and delivers relevant tender opportunities to design and digital agencies. Start your free trial at tandara.co.uk.