Case Study Format for Security Tenders (UK Guide 2026)

Last updated: 3 October 2026

The case study format for security tenders that scores well follows a fixed structure — client context, challenge, solution, quantified outcome — kept to roughly 300-500 words per example. Most PQQs and Selection Questionnaires ask for two to three case studies from the past three to five years, matched to the contract's service type and scale (Tender Consultants, 2026).

Key Takeaways

• Most PQQs ask for two to three comparable case studies from the past three to five years, matched on service type, scale and client type, per Tender Consultants (2026).
• Under the Selection Questionnaire format, contract examples no longer need a 500-word narrative cap, per EM LawShare (2016), though most buyers still expect concise, evidence-led entries.
• Social value carries a minimum 10% evaluation weighting in central government contracts and often more in local authority and NHS procurement, per Tender Consultants (2026) — a case study should show it, not just claim it.
• Thornton & Lowe report a strong win rate on public sector bids they support with structured case studies and marketing, per Thornton & Lowe (2026).
• Across Pulse Operations's live estate, 96.2% of patrol checkpoints carried a watermarked photo in the trailing 90 days to July 2026 — the kind of evidence a case study can cite directly rather than assert (see /benchmark).

What is a case study in a security tender?

A case study in a security tender is a structured written account of a past or current contract that a bidder submits as evidence of relevant experience, usually within a Pre-Qualification Questionnaire (PQQ) or the Standard Selection Questionnaire (SQ) that replaced it in England from 2016. It exists to answer one evaluator question: has this supplier actually done this before, at this scale, for a comparable client?

The SQ format was introduced by the Crown Commercial Service (CCS) via Procurement Policy Note 08/15, following the 2015 Public Contracts Regulations. Under it, tenderers still provide three previous contract examples that evidence their experience and technical ability, but the old requirement for a 500-word-or-less description per example was dropped (EM LawShare, 2016). CCS was clear this "should not be seen as a major shift in the fundamental approach of supplier selection" — the substance evaluators want hasn't changed, only the word-count straitjacket.

Which sections must a security tender case study include?

A security tender case study must include five fixed sections: client context, the challenge, the solution deployed, the outcome, and named metrics. Skipping any one of these is the single most common reason evaluators mark a case study down as "generic" rather than "evidenced."

The five-part structure, in order:

1. Client and site context — sector, size, location type (e.g. mixed-use retail/residential, NHS estate, logistics hub), and the service scope (manned guarding, mobile patrol, keyholding, CCTV monitoring).
2. The challenge — what specifically was going wrong or at risk: incident volumes, a compliance gap, an incumbent's poor performance, a mobilisation deadline.
3. The solution — what was actually deployed, by when, with which accreditation or standard applied (BS 7858 screening, SIA-licensed personnel, ACS status where held).
4. The outcome — the measurable change, stated as a before/after figure wherever possible.
5. A named or anonymised reference — a contact willing to be approached, or a clear statement of why the client is anonymised.

Tender Consultants sets out a comparable six-part framework in its own guide to tender case studies, reinforcing that structure — not length — is what evaluators are scoring against.

How long should a security case study be for a tender?

Pulse Operations guides that a security tender case study should typically run to 300-500 words, unless the invitation to tender (ITT) sets an explicit word or character limit — and Pulse Operations notes that most do. Public sector buyers using Find a Tender or a CCS framework almost always cap quality answers at a stated word count per question, and a case study embedded within an answer inherits that limit.

Since the SQ replaced the PQQ, there is no longer a mandated 500-word ceiling per contract example (EM LawShare, 2016) — but removing the cap doesn't mean padding is rewarded. Evaluators scoring dozens of submissions favour density over length: a tight 350-word case study with three hard numbers beats an 800-word account with none.

Check the ITT for:

• A stated word or character limit per question or appendix.
• Whether case studies sit inside the quality answer or as a separate appendix.
• Any instruction on font size, page count, or embedded-image restrictions.

How do you select the most relevant past projects for a security tender?

Selecting the right case study for a security tender means matching the contract type, scale and client sector as closely as possible — not simply choosing your biggest or newest job. Evaluators score relevance explicitly; a manned guarding tender for an NHS trust is not well served by a case study about event stewarding, even if the event was larger.

Use this filter, in order:

1. Service match first — manned guarding, mobile patrol, keyholding, CCTV/alarm response, or FM-integrated security. Match like for like.
2. Scale match second — officer numbers, site count, checkpoint volume. A single-site contract doesn't need a 40-site case study; it needs a comparable-sized one.
3. Client-type match third — public sector buyers often weight comparable-sector delivery (NHS, local authority, education) more heavily than private commercial experience.
4. Recency last — most buyers want examples from the past three to five years (Tender Consultants, 2026), so a strong seven-year-old contract is weaker evidence than a mediocre one from last year.

Where no exact-match contract exists, frame transferable experience explicitly — name the overlapping element (screening standard, site type, incident category) rather than hoping the evaluator infers it.

What KPIs and quantifiable results strengthen a security case study?

The KPIs that strengthen a security tender case study are the ones tied directly to the buyer's stated priorities: incident reduction, response times, patrol completion rates, and cost or hours saved. A case study without a number reads as an assertion; a case study with one reads as evidence.

Strong KPI categories for security and FM contracts:

An illustrative worked example: mytender.io reports that Professional Security saved over 250 hours and achieved a 65% time reduction across nine tenders, with £18,750 of value saved, using its AI bid-writing platform (mytender.io, 2026) — a reminder that the efficiency of producing case studies is itself a metric worth tracking if you bid frequently.

Where a contract genuinely lacks a headline number, describe the delivery mechanism concretely instead. At a landmark mixed-use development in West London, Priority First — the founding operation behind Pulse Operations, disclosed here as Pulse's own case study rather than an arm's-length customer win — inherited a site where nobody could prove which plant room had actually been checked at 3am across 152 checkpoints and 11 officers. Every checkpoint was made photo-mandatory inside Pulse; a missed area now shows as a gap in the record rather than a dispute six weeks later. Since going live in February 2026, the site has logged over 540 patrols in its first five months, each with photo evidence attached. That's a case study built on a mechanism, not a guess — and it's exactly the kind of concrete, checkable detail that survives evaluator scrutiny better than a vague "excellent service" claim.

"An event is a whole operation stood up in an afternoon and torn down three days later. The mistake is running it on radio memory. Map the footprint, drop the checkpoints, brief the vigilance requirements — then the client gets the whole night, every ejection with a photo, before they leave the car park." — Mo Hassan, Founder, Pulse

How do you get client permission to use their details in a tender?

Getting client permission to name them in a tender submission requires explicit, documented sign-off — never assume a verbal nod covers you. UK data protection law under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018 governs how personal data is used, and while a company name and a site address are not usually personal data, quotes attributed to a named individual are.

Practical steps:

• Confirm what's shared publicly. Tender submissions to public bodies can become disclosable under the Freedom of Information Act 2000 once awarded, so a client who's fine with a private reference call may object to their name appearing in a document that could later be requested.
• Get sign-off in writing, even a short email, covering: use of company name, use of logo, use of any quoted testimonial, and whether the client agrees to be contacted as a reference.
• Default to anonymisation where sensitive. For close protection, government sites, or any contract with a confidentiality clause, describe the client by type and location only — "a prestige central-London residential estate" rather than a name.
• Keep a permissions log per case study so bid writers aren't chasing sign-off under deadline pressure on every submission.

Which mistakes do evaluators flag in security tender case studies?

Evaluators most commonly flag three weaknesses in security case studies: genericness, missing metrics, and irrelevance to the specific lot being tendered. Each one is avoidable with the same discipline that avoiding all three requires.

• Generic language with no evidence. Phrases like "excellent service" or "highly trained officers" score nothing on their own — every bidder claims this. Pulse Operations's own guide on how to win your next security tender makes the point directly: evaluators can't score assertions, only proof.
• No quantified outcome. A case study that describes a deployment but never states what changed reads as marketing copy, not evidence.
• Wrong-scale or wrong-sector example. Submitting your largest contract regardless of fit, rather than your closest match, signals a lack of understanding of the buyer's actual requirement.
• Ignoring the compliance gates. Facilities Tenders notes that its sister company Hudson Succeed has run bid writing for over 60 years with an 87% success rate — built on clearing pass/fail gates (SIA licensing, BS 7858 screening records, insurance) before quality content is even assessed.
• Stale references. Using a contract that ended four years ago when a fresher, smaller example exists undermines credibility on recency.

Your case study format for security tenders checklist

• Confirm the ITT's word or character limit for case studies before you start writing.
• Select two to three examples matched on service type, scale and client sector, ideally from the last three to five years.
• Structure each case study as: context, challenge, solution, outcome, reference.
• Attach at least one quantified metric per case study — patrol completion, response time, incident reduction, or cost saving.
• Get written sign-off from the client before naming them, their logo, or quoting them.
• Anonymise by client type and location where confidentiality or GDPR sensitivity applies.
• Cross-check each case study against the specific lot's stated priorities, including social value weighting.
• Have someone outside the writing team proofread for genericness before submission.

FAQ

What is the standard case study format for a UK security tender?

The standard format is client context, challenge, solution, outcome and reference, typically kept to 300-500 words unless the ITT sets its own limit. This five-part structure lets evaluators quickly locate the evidence they're scoring against.

How many case studies should I include in a security tender submission?

Most PQQs and SQs ask for two to three case studies demonstrating comparable delivery from the past three to five years (Tender Consultants, 2026). Check the specific ITT, as requirements vary by framework and contracting authority.

What's the difference between a PQQ and an SQ case study requirement?

Pulse Operations explains that the Standard Selection Questionnaire replaced the PQQ in England from September 2016 and still requires three contract examples, but no longer mandates a 500-word-or-less description for each (EM LawShare, 2016). The substance required is largely unchanged; only the rigid word cap was removed.

Do I need client permission to name them in a public tender?

Yes. Get written sign-off covering company name, logo and any quoted testimonial before submission, particularly since tender documents can become disclosable under the Freedom of Information Act 2000 once a contract is awarded to a public body.

What KPIs matter most in a security case study?

Patrol or checkpoint completion rates, incident response times, compliance metrics such as BS 7858 screening currency, and cost or hours saved are the categories evaluators respond to best. Social value metrics matter too, given the minimum 10% weighting common in central government procurement (Tender Consultants, 2026).

Who should write the case study inside a security company?

A bid writer typically drafts the narrative, but the operations manager or account manager who ran the contract should supply the facts, metrics and client contact — a case study written without operational input is where genericness creeps in.

Can I use the same case study for every tender I submit?

No — reuse the underlying project but rewrite the emphasis for each ITT's stated priorities. A case study angled toward incident response for one buyer may need re-angling toward social value or mobilisation speed for another.

Building case studies you can actually stand behind

Every point above assumes you have real evidence to draw on — and that's the part most security firms struggle with, not the writing. A case study claiming "100% patrol completion" only survives evaluator scrutiny if there's a photo, timestamp and GPS record behind every checkpoint it references, which is exactly what Pulse Operations's photo-verified patrols capture as standard: no tag scans, just a mandatory watermarked photo per checkpoint.

At a 16-building central-London residential estate served by Priority First, Pulse's founding operation, the client had previously had no way to see delivered-vs-contracted patrols without ringing the office. Since going live on Pulse in March 2026, that estate has logged over 4,100 patrols across its buildings — roughly 250-280 per building — with 100% of checkpoint completions photo-verified, visible to the client through its own client portal. That's the kind of number a bid writer can put straight into a case study, because it's already sitting in the platform, not reconstructed from memory under deadline pressure.

If your next tender needs a case study built on evidence rather than recollection, get in touch with Pulse Operations to see how the client portal and photo-verified patrol record can turn your live contracts into ready-made proof for your next submission.

Related Reading

• Security Guard Handover Template UK | Free Guide 2026
• Security RAMS Template: UK Guide + Free Framework 2026
• Security Site Induction Checklist UK: Full 2026 Guide

★ Add pulse-operations.co.uk as a preferred source on Google