How to Answer Tender Quality Questions When You Have No Direct Experience

The question reads: Describe your experience of delivering a similar service to a public sector body. Provide two examples. You have delivered the service for years. You have never delivered it to a council, a trust or a department. The cursor sits there, and the bid quietly turns into a no-bid.

This is one of the most common reasons small firms stop before they start. It is also, more often than people think, the wrong reason. Quality questions score evidence of capability, and capability is not the same thing as a matching contract title. The skill is in showing the evaluator what you have done, why it transfers, and how you will close the gap you do have, without claiming anything you cannot prove.

This guide works through that skill question by question. It also covers the practical part that usually decides whether you manage it under a deadline: having your evidence organised before the tender lands, so you are matching it to questions rather than hunting for it.

What a Quality Question Is Actually Scoring

Before writing anything, read the question the way an evaluator will read your answer. Most quality questions sit inside a published scoring scheme, and the scheme tells you what earns marks. Typical descriptors talk about confidence: a top score shows the buyer has high confidence you will deliver, a low score shows limited confidence or significant gaps.

Notice what that wording does and does not say. It rarely says "must have delivered this exact contract before". It asks whether the evaluator believes you can deliver. A matching past contract is the quickest route to that belief. It is not the only one.

Split the question into its parts before you look at your evidence:

• The outcome the buyer wants. Reduced response times, safe handover of records, a stable service through mobilisation.
• The conditions it happens in. Regulated environment, multiple sites, vulnerable service users, a fixed budget.
• The proof they ask for. Named examples, methods, people, accreditations, policies.
• Any hard requirement. A minimum number of years, a specific certification, a pass or fail threshold.

The last item matters most. If the tender sets a pass or fail requirement for directly comparable experience and you do not have it, no amount of good writing changes the outcome. That is a no-bid signal, and it is better found on day one than on the evening before submission. Everything else in this guide applies to the much more common case: the question is scored, not gated, and the gap is about context rather than ability.

Practical rule: If the question is pass or fail and you fail it, stop. If it is scored, your job is to raise the evaluator's confidence with evidence that is true.

Why "No Direct Experience" Is Usually Narrower Than It Feels

When owners say they have no experience, they usually mean one of four narrower things. Naming which one you have changes the answer you write.

A genuinely new service, something your business has never done in any form, is a different situation. You can still sometimes bid, through a partner or subcontractor, but the honest answer is that you are building capability rather than evidencing it. Most firms reading this are not in that position. They are in one of the four rows above, and each row has a recognisable answer shape.

Wrong sector

A cleaning firm that services private offices, a software house that builds for retailers, a training provider that works with corporate clients. The service is the same. What changes is the environment: procurement rules, governance, reporting, data protection obligations, safeguarding, and the way a public body measures performance.

The answer should spend little time proving you can do the core work, because your private examples already do that. It should spend more time on the environmental differences and how you handle them. That is where an evaluator's doubt sits.

Wrong scale

You have done ten sites, the buyer has forty. You have supported two hundred users, the buyer has two thousand. Evaluators are right to ask what changes when the volume rises, so answer it before they ask. Which parts of the method stay the same, which parts need more people or a different structure, and how will you resource them. If you plan to recruit or subcontract, say so plainly.

Wrong combination

The lot bundles facilities services, or asks for design and build, or combines delivery with training. You have done every part, just never in one contract. Evidence each part with its own example, then describe how you would coordinate them: who owns the whole, how handoffs between components work, how one reporting line is kept.

Wrong entity

A new or recently restructured business often has people with years of relevant experience gained elsewhere. That experience is real, but it belongs to the people, not the company. Attribute it accurately. "Our operations director managed a comparable contract at a previous employer" is honest and useful. Presenting that contract as your company's own is not, and a reference check will expose it.

The Evidence You Already Have

Firms without direct public sector experience tend to underestimate their evidence because they look for one thing, a public sector case study, and stop when they do not find it. Widen the search. Each of the following can carry marks on a quality question when it is relevant and current.

• Private sector case studies. The strongest transferable evidence, especially where the client had regulatory or governance demands similar to the buyer's.
• Subcontract work. If you delivered part of a public contract under a main contractor, that is public sector delivery. Describe your part accurately, not the whole contract.
• Method statements and procedures. How you actually run the work: mobilisation steps, quality checks, escalation routes.
• Policies. Quality, health and safety, safeguarding, data protection, environmental, equality. Many quality questions are partly answered by showing a working policy and how it is applied.
• Accreditations and certifications. Independent evidence that a system exists and is audited. Check the dates before you cite them.
• Team CVs. Relevant qualifications and experience of the people who will deliver.
• Performance records. Response times, complaint logs, audit outcomes, client feedback you are permitted to use. Use only figures you can stand behind.
• Past bid answers. Even unsuccessful bids contain worked answers to questions that come up repeatedly, and the feedback tells you which parts scored.

The point of listing these is not to pad the answer with everything. It is to give you enough material that you can pick the two or three pieces that best match the question, rather than reaching for whatever is to hand at eleven at night.

An answer built from three pieces of well-chosen evidence beats one built from ten pieces of loosely related evidence. Evaluators score relevance, not volume.

A Structure for Answering Without Direct Experience

Answers in this situation fail in two predictable ways. Some apologise, spending a paragraph explaining why the firm has not worked for a public body before. Others bluff, describing private work in language that implies it was public. Neither helps the evaluator. A plain structure keeps you between the two.

1. Open with the capability, stated against the buyer's outcome. One or two sentences that say what you do and how it achieves what the buyer wants. Use the buyer's terms, not your marketing terms.
2. Give the closest evidence, described accurately. Name the type of client honestly, the scope, what you did and what happened. If a client cannot be named, say it is a confidential client in a stated sector.
3. Draw the line to the buyer's context. Explain specifically why that example is relevant: the same method, the same risks, similar governance, comparable users. This is the sentence most answers leave out, and it is the one that does the work.
4. Address the difference directly. Name what is new in this contract and how you will handle it. Reporting to a public body, a different data regime, a larger footprint. Give the method, the person responsible and any support you will bring in.
5. Close with how the buyer will see it working. Reporting, review points, the metrics you will track. This turns a claim into something the buyer can check during the contract.

A worked example

Take a hypothetical facilities firm answering: Describe your experience of providing reactive maintenance to multi-site public buildings. The firm has provided reactive maintenance to a private retail estate and a group of private schools, but never to a council.

A weak answer begins, "Although we have not yet worked with a local authority, we are confident..." and then lists services. A stronger answer, following the structure above, would cover:

• What the firm does and how its reactive model works across sites, with the target the buyer cares about named.
• The private multi-site contract, described as private, with its scope and how calls were triaged and tracked.
• Why the schools work is relevant: occupied buildings, safeguarding requirements for staff on site, work scheduled around users.
• What is different for the council: reporting format, a helpdesk integration or particular compliance records, and who in the firm owns each.
• How the council would see performance: the reports, how often, and what happens when a target is missed.

Nothing in that answer claims public sector experience the firm does not have. Every sentence is either evidence or a method. That is what raises confidence.

Handling the Questions That Bite Hardest

Some question types are especially uncomfortable for firms new to the public sector. Each has a sensible approach.

"Provide examples of similar contracts"

Read the instructions for what counts as similar. Some tenders define it by value, scope or sector. If the definition excludes your work, the question may be pass or fail for you, so check. If it is open, choose the examples that are similar in the ways that matter for delivery and explain those similarities explicitly. Do not let the evaluator work out the relevance for you.

Mobilisation questions

These worry first-time bidders more than they should. A buyer wants to know the service will start safely. You can answer that with your actual mobilisation method from private contracts, adjusted for the buyer's requirements: who leads it, what you do before the start date, how you handle staff or data transferring, how you check readiness. Our article on what a mobilisation plan is sets out the usual components if you have never written one formally.

Social value questions

These often have little to do with prior public sector work, which makes them a fair place for a newer bidder to score well. What matters is a credible, measurable commitment tied to the contract. See social value tender questions for how they are usually framed.

References

If the tender asks for referees, private clients are generally acceptable unless the instructions say otherwise. Ask permission first, tell the referee what the contract involves, and make sure what they will say matches what you wrote. A reference that contradicts the answer is worse than a modest answer.

Certifications you do not hold yet

If a certification is mandatory, it is a gate. If it is scored or desirable, describe the system you run and, only if it is true, where you are in working towards certification. Do not suggest a certificate is held or imminent when it is not. Our guide to Cyber Essentials certification covers one that appears in many technology and data-related tenders.

What You Must Not Do

The pressure to score can push a good firm into wording it would never use in a client meeting. These are the lines that should not be crossed, because they turn a weak answer into a risky one.

• Do not relabel private work as public. Calling a private school trust "an education authority" or a housing management company "a housing association" when it is not will come apart at clarification or reference stage.
• Do not borrow a partner's experience without saying so. If you are bidding with a subcontractor whose experience you are relying on, name them and their role. Many tenders have specific rules about relying on others' capability.
• Do not invent figures. If you do not track a metric, do not quote one. Describe how you will track it on this contract instead.
• Do not promise what operations has not agreed. Response times, staffing levels and reporting frequencies all become contract obligations. The person who will deliver them should approve them.
• Do not reuse an answer without reading it. An answer that scored well for one buyer can carry another buyer's name, an expired certificate or a leaver's CV.

That last point is where tools come in, for better or worse.

How a Reusable Content Library Bridges the Gap Honestly

The firms that handle this well are rarely better writers. They are better organised. When the tender arrives, their transferable evidence is already in one place, current, and labelled by the kinds of questions it answers. The work becomes matching and adapting, not searching and inventing.

A reusable library, sometimes called a knowledge base or content library, holds the material listed earlier: case studies, policies, method statements, accreditations, CVs and past answers. Its value for a firm without direct experience is specific. It lets you see all your relevant evidence at once, so you can pick the closest match rather than the most recent one you remember.

It also changes what AI drafting can safely do. A general chat tool asked to describe your public sector experience will happily write fluent paragraphs about experience you do not have. That is the bluffing failure, produced faster. A tool that drafts only from your own documents has nothing to bluff with. If your library contains no public sector case study, a grounded draft cannot produce one; it can only draw on the private work you uploaded, which is exactly the honest starting point this guide recommends.

That is how Bidwell works. You upload past responses, accreditations, case studies, policies and team CVs, or point it at your website, and it builds a knowledge base of your own answers. When you drop in a tender, it drafts each answer from that material and shows the document each answer came from. The knowledge base itself is free; drafting tenders from it is £20 a month if you choose to switch it on. Bidwell drafts and you review: a person signs the bid before it goes out.

For a quality question where you lack direct experience, the citation is the useful part. You can open the private case study beside the drafted sentence and check two things: that the description matches what actually happened, and that the draft has not described the client as something it is not. Then you add the parts a library cannot supply, chiefly the line connecting your evidence to the buyer's context and your plan for the difference.

Rule for reviewers: If you cannot open the source document behind a sentence, delete the sentence or find the source.

Building the library with this problem in mind

If your worry is quality questions without direct experience, build the library so it helps with exactly that.

1. Write case studies with context, not just results. Record the client type, the conditions (regulated, multi-site, occupied buildings, vulnerable users), the method and the outcome. Context is what lets you draw the line to a new buyer.
2. Store how-we-do-it material separately from what-we-did material. Methods and procedures answer forward-looking questions; case studies prove them. You need both.
3. Keep subcontract work, with your role stated precisely. It is often your only true public sector evidence. Do not let it get lost because it was not your contract.
4. Attribute individual experience to individuals. CVs should say where experience was gained, so it is never accidentally presented as company history.
5. Date everything and check it. Expired accreditations and departed staff are the commonest errors in reused answers.
6. Feed back every result. Each submitted answer, and each piece of evaluator feedback, makes the next one easier. Your first public sector win becomes the direct experience you were missing.

Our guides on how to build a knowledge base and how to present case studies go into more detail on both steps.

Choosing Where to Bid While You Build a Track Record

Answering well is half the problem. The other half is picking tenders where transferable evidence is a fair fight. Some opportunities suit a firm building its first public sector record better than others.

• Lower-value, local opportunities. Smaller contracts often have lighter qualification requirements and scope that maps more closely to private work of similar size.
• Tenders that score method over history. Read the evaluation criteria. If most of the quality marks sit on approach, mobilisation and social value rather than past contracts, your position is stronger than it looks.
• Lots sized for smaller suppliers. Where a contract is split into lots, a single lot may match your scale.
• Subcontracting. Delivering part of a larger contract builds genuine public sector evidence for the next bid.

Avoid the opposite: large, complex contracts where comparable experience carries heavy weight or is a minimum requirement. These are the bids where honest transferable evidence will score modestly, and the cost of writing them is high.

If you are unsure where you stand, the free tender readiness checker points at what is stopping you, and the framework eligibility tool shows which frameworks you can realistically apply to. For the bid or no-bid call itself, see the bid/no-bid template.

A Checklist Before You Submit the Answer

Run each quality answer written without direct experience through these questions before it goes to the approver.

• Have I confirmed the question is scored, not pass or fail?
• Does the opening state our capability against the buyer's outcome, in their terms?
• Is every client described as what it actually is?
• Is there an explicit sentence explaining why each example is relevant to this buyer?
• Have I named the difference in this contract and said how we will handle it, and who owns that?
• Is experience gained by individuals elsewhere attributed to them, not to the company?
• Are any partners or subcontractors we rely on named, with their role?
• Does every figure trace to a record we hold?
• Are all certificates cited current?
• Has the person who will deliver agreed to every commitment?
• Will our referees say the same thing we have written?

If an answer passes all eleven, it is honest and as strong as your evidence allows. That may not be the top score. It is usually more than the firm expected when it nearly decided not to bid, and it is a sound base for the next bid, when the gap will be a little smaller.

The Gap Closes One Bid at a Time

No firm starts with public sector experience. Every supplier on every framework answered a quality question once without a matching contract to point to. The ones who got through did it with accurate, well-chosen evidence and a clear plan for what was new, not with clever wording.

The worry that stops SMEs is reasonable: they do not want to overclaim, and they do not want to waste forty hours on a bid that cannot score. Both concerns are answered by the same habit. Know exactly what evidence you hold, describe it truthfully, explain why it transfers, and be selective about where you bid. Organise that evidence once and each quality question becomes a matter of matching and adapting, and every submission you make adds to the record the next one draws on.