How to win your next security tender

Ask any evaluator what makes tender scoring miserable and they'll tell you: every submission reads the same. Professional. Vetted. Committed to excellence. The bids that win aren't the ones that claim more — they're the ones that prove more. In a sector where everyone holds the same licences and quotes within a few percent of each other, the scored difference is evidence.

This guide walks through how UK security and FM tenders are actually evaluated, the gates you must clear before quality even gets read, the questions where contracts are genuinely won, and how to turn the way you already run your operation into the proof that sets a bid apart.

How tenders are actually scored

Most formal tenders — public sector especially — are decided on a published price/quality split, commonly somewhere between 60/40 and 30/70. Two things follow from that, and most bidders act on neither:

• Quality is usually worth more than price. On a 40/60 price-quality split, a bid priced 5% higher that scores one grade better on quality wins comfortably. Chasing the bottom line while writing boilerplate answers is optimising the smaller number.
• Evaluators score the answer, not the company. The person marking question 4b has a scoring matrix and twenty submissions. They cannot award marks for anything you didn't put in the answer to 4b — however good your brochure was.

Public-sector buyers now operate under the Procurement Act 2023 regime, with its emphasis on transparency and the "most advantageous tender" — which in practice sharpens the same point: show your working, evidence your claims, and make the evaluator's job easy.

The gates: clear them or nothing else matters

Before quality is read, the selection questionnaire weeds out bids on pass/fail grounds. None of these win you the contract; any of them can lose it. Have them current, filed and producible on demand:

• SIA licensing and ACS status — increasingly a hard requirement or heavily weighted. If you hold Approved Contractor status, your self-assessment evidence should already be in one place.
• Screening to BS 7858 — with records that show it, per person, not a policy that asserts it.
• Insurance — employer's liability, public liability and (where relevant) professional indemnity at the levels the buyer specifies.
• Financial standing — accounts, and a story for any wobble; buyers read them.
• Health & safety and GDPR — current policies, a named responsible person, and a data-processing position you can defend.
• References — warmed up in advance, not surprised by a call.
• Martyn's Law readiness — for publicly accessible venues, expect questions about the Terrorism (Protection of Premises) Act 2025. A per-site answer beats a generic paragraph; our readiness guide covers it.

Where bids are actually won

With the gates cleared, four or five quality questions typically decide the contract. The same ones come up in almost every security and FM tender:

1. Service delivery — and how you'll prove it

The question behind the question is "how will we know we're getting what we pay for?" Most bidders answer with supervision structures and QA visits. The stronger answer is verifiable evidence: photo-verified patrols, delivered-vs-contract reporting, and a portal the client can open themselves. If you can offer the evaluation panel a live login rather than a promise — a portal showing a real (anonymised or demo) operation — you've turned an assertion into a demonstration, and that difference is scoreable. This is proving patrols, applied commercially.

2. Mobilisation

Buyers have been burned by chaotic transitions, so a credible mobilisation plan carries real marks. Credible means dated: week-by-week, with named owners — site surveys, assignment instructions, vetting pipeline, kit, induction, a parallel-run period, and the go-live decision point. A generic "we will work closely with stakeholders" paragraph scores the mark it deserves.

3. TUPE

On most re-tenders the incumbent's staff transfer to you under TUPE. Evaluators look for bidders who plainly understand this: that you've priced for the transferring terms, planned the consultation, and thought about retention and morale in the first ninety days. Getting TUPE wrong is expensive; visibly understanding it is a differentiator precisely because so many bids hand-wave it.

4. Management information and reporting

Every bid promises "regular reporting". Specify yours: what the client sees, how often, and show a sample. A monthly pack built from live operational data — patrols delivered, incidents with response times, compliance status — with an honest gaps column, beats a glossy template with invented numbers. Honesty reads as confidence.

5. Social value

In public-sector tenders, social value carries explicit weighting — often 10% or more. It rewards specifics: local recruitment numbers, apprenticeships, guaranteed-hours contracts, mental-health support for lone workers. Real commitments you can evidence at review beat grand themes you can't.

Writing answers that score

• Answer the question asked — mirror its structure and its language. If it asks for three things, give three headed things.
• Evidence every claim. Numbers, named tools, screenshots, references. An unevidenced superlative is filler the evaluator has read nineteen times today.
• Write for a tired marker. Front-load the point, keep paragraphs short, make the marks easy to award.
• Kill the boilerplate. If a sentence could appear in a rival's bid unchanged, it isn't earning marks.
• Be honest about limits. A plan that acknowledges risk and shows the mitigation reads as competence, not weakness.

A pre-tender checklist

The best time to prepare a bid is before there is one. Keep these warm and every tender becomes an assembly job instead of a scramble:

1. Bid/no-bid discipline — score every opportunity for fit before committing; a focused pipeline beats a busy one.
2. An evidence library — patrol records, KPI packs, compliance registers and screening stats, exportable on demand.
3. A written case study — one page, real numbers, client-approved.
4. A demo portal — branded, loaded with a representative site, ready to show a panel.
5. A mobilisation plan template — week-by-week with owners, tailored per bid rather than written from scratch.
6. A TUPE playbook — measurement questions for the incumbent's workforce data, pricing approach, consultation plan.
7. Social value commitments — three or four you actually deliver, with last year's numbers.
8. References briefed — current clients who know a call may come.
9. A red-team review — someone outside the bid team marks the draft against the questions, coldly.
10. Feedback on every loss — request the debrief, log the scores, fix the weakest section before the next one.

The unfair advantage: an operation that proves itself

Almost everything above gets easier when the evidence assembles itself. If your patrols are photo-verified, your compliance sits on one runway, your incidents carry response times and your clients already use a live portal, then the evidence library, the sample reports and the demonstration login aren't bid-preparation tasks — they're screenshots of Tuesday. That's the ground Pulse was built on: the operation generates the proof, and the proof wins the work. No software wins a tender by itself — but walking in with evidence the incumbent can't match changes the conversation.

This guide is general commercial guidance based on common practice in UK security and FM procurement. Tender rules, evaluation models and legal obligations (including TUPE and the Procurement Act 2023) vary by buyer and contract — always follow the instructions in the specific tender pack and take professional advice where the stakes warrant it.