A security contract can look sound on paper and still fail at the point of delivery. This guide to security tender evaluation is about avoiding that outcome. It focuses on the questions, evidence and judgement needed to appoint a provider that can manage people, risk and changing conditions, rather than simply produce a persuasive bid.
Tender evaluation is often treated as a procurement exercise with a security section attached. That approach creates predictable problems. The lowest compliant price wins, mobilisation is rushed, site knowledge is thin and the client discovers that contract management is carrying risks that should have been dealt with before appointment.
A better process tests whether a provider can turn stated requirements into consistent operational performance.
Start with the security outcome, not the staffing number
Before issuing a tender, be clear about what the service must achieve. A requirement for two officers at a reception point says little about the risks they are expected to manage, the decisions they may need to make or the standard of interaction required.
For example, a corporate site may need access control, visitor management and a reassuring presence. A busy venue may need staff who can identify concerning behaviour, communicate well under pressure and support proportionate incident management. A construction project may need reliable control of people, vehicles and materials while its layout and risk profile change regularly.
Those are different operating environments. They should not be assessed using identical questions or a generic manned guarding specification.
Define the outcome in practical terms. Consider the threats, vulnerabilities, operating hours, public contact, critical assets, likely pressure points and the decisions expected from front line staff. If counter terrorism preparedness is relevant, specify the capability required without turning the tender into a paperwork exercise. Ask how the provider will develop awareness, reporting, escalation and command arrangements in the real environment.
A tender cannot compensate for an unclear client requirement. If the scope is vague, suppliers will make assumptions. Those assumptions will later appear as variations, disputes or service gaps.
Build an evaluation model that reflects real risk
Price matters. It is also one of the easiest areas to compare and one of the least useful indicators of future security performance when used alone. A bid that is substantially cheaper than credible competitors needs examination, not automatic praise.
The question is simple: what has been removed, underestimated or transferred elsewhere to make that price possible? It may be supervision, relief cover, training time, pay rates, management presence, technology support or the capacity to deal with unforeseen demands.
A sensible scoring model gives meaningful weight to quality and separates the things that must be present from the things that differentiate one provider from another. Mandatory requirements should be pass or fail. A supplier without the necessary licences, insurance, safeguarding arrangements where relevant, or financial standing should not be rescued by an attractive presentation.
Quality scoring should focus on the elements that affect delivery. These normally include:
- understanding of the site and its operating context
- recruitment, vetting, retention and relief arrangements
- supervision and contract management
- training, competence and behavioural standards
- mobilisation planning and service continuity
- reporting, assurance and improvement
The weighting will depend on the environment. A high consequence site, a public facing venue or a complex multi site operation should place greater emphasis on competence, supervision and resilience than a stable, lower risk location. There is no universally correct percentage split between quality and cost. There is, however, a poor decision in assigning a high quality weighting then allowing vague claims to receive high marks.
Evaluate evidence, not promises
Security bids are full of familiar language: bespoke service, experienced teams, dedicated support and comprehensive training. None of it means much until it is connected to evidence.
Ask bidders to explain how they will deliver a specific requirement, who will do it and how the client will know it is happening. The strongest submissions tend to be clear about accountabilities, routines, escalation points and limits. They do not pretend that every issue can be solved by a control room, an app or a monthly report.
Request relevant examples, but assess them carefully. A provider may have worked at a large event or major corporate campus without demonstrating that the proposed contract team delivered that work. Look for the role played, the conditions faced, the decisions made and the measurable outcome. Generic case studies prove marketing capability more than operational capability.
Training deserves particular scrutiny. Asking whether officers receive training produces an easy yes. The more useful question is how the provider establishes whether people can apply learning in the workplace. Attendance records and certificates show exposure to training. They do not show judgement, observation, communication or confidence under pressure.
This matters particularly where organisations are developing their protective security arrangements in response to Martyn’s Law. Compliance evidence will have a place, but it must not become the endpoint. A provider should be able to explain how its people recognise concerns, communicate them properly and support an effective response within the boundaries of their role.
Test the people who will actually run the contract
The sales team is rarely the team that will manage a difficult shift, a staffing shortfall or a serious incident. Tender evaluation should therefore include structured meetings with the proposed contract manager and, where appropriate, operational supervisors.
Use scenario questions based on the site. Keep them proportionate and avoid seeking sensitive operational detail. The aim is to test thinking, not obtain a rehearsed script. Ask how they would deal with repeated failures to fill shifts, an officer whose conduct is causing concern, a change in site risk, or a breakdown in communication between security and operations.
Listen for ownership. Weak answers move quickly towards blaming recruitment markets, clients, subcontractors or circumstances. Strong answers acknowledge constraints but explain the controls, decisions and communication that will be used to keep the service safe and stable.
Site visits are also valuable. They reveal whether a bidder has taken time to understand access routes, workflow, public interaction, handover arrangements and practical constraints. A generic proposal submitted after a superficial visit is a warning sign. It usually remains generic after award.
Examine mobilisation as a risk period
Many security contracts fail early because mobilisation is treated as an administrative handover. It is a period of elevated risk. New staff, new procedures, unfamiliar stakeholders and incomplete information can create gaps even where the intended operating model is sound.
Ask for a mobilisation plan that identifies named responsibilities, recruitment milestones, site familiarisation, induction, equipment, communications, contingency cover and acceptance criteria. It should explain what happens if recruitment falls behind plan or incumbent staff do not transfer as expected.
Do not accept a colourful project chart as proof of readiness. Test dependencies. If officers cannot be confirmed until close to the start date, when will they learn the site? If training is scheduled after deployment, what is the interim control? If a key system is delayed, how will access control or reporting be managed safely?
The best providers are candid about mobilisation risk. Overconfidence is not reassurance. It is often a sign that the supplier has not thought through the practical work.
Score consistently, then challenge the result
Evaluators need clear guidance before reading bids. Agree what a high, adequate and poor response looks like for each criterion. Score independently first, then discuss differences against the published standard. This reduces the risk that the most confident voice in the room determines the outcome.
Keep an audit trail, but do not confuse documentation with sound judgement. Written reasons should identify the evidence that supported the score and the consequence of any weakness. “Good response” is not a defensible explanation. “The proposed supervision model did not state frequency of night visits or cover arrangements for absence” is.
Clarification can resolve genuine ambiguity, but it should not allow a bidder to rewrite a weak submission after seeing the requirement more clearly. Treat all suppliers fairly and record the process. If a point is material enough to change a bid, consider whether the tender documents were clear enough in the first place.
Make appointment the start of assurance
The tender decision should produce a contract that can be managed, not a folder that is filed away. Convert key commitments into mobilisation checks, service measures and regular contract review points. Focus assurance on what affects performance: staffing stability, supervisor contact, incident quality, training application, corrective action and recurring weaknesses.
Mildot Group’s experience is that capability becomes visible when conditions are imperfect. The useful test is not whether a provider can describe a security service at a bid meeting. It is whether its people can make sound decisions, communicate clearly and maintain standards when the plan meets a difficult day.
Choose the provider whose evidence gives you confidence in that moment. That is where the value of a well run tender is realised.
