Comparing two monthly security prices does not necessarily mean comparing the same service. One proposal may include cover for leave and absence while another covers only scheduled shifts. Equipment, maintenance, training and reporting may also rely on different assumptions.
A low price alone does not prove poor service, and a high price does not guarantee quality. Procurement should reveal which scope and cost assumptions explain the difference. This framework helps prepare a private service comparison; applicable public procurement requirements remain separate.
Establish a common service baseline
Define the posts, operating hours, duties, relationship between fixed positions and patrols, and expected reports. Give all candidates the same information and clarifications. Explain which parts of the proposal must be recalculated if the assignment changes.
A headcount is not the same as the number of posts that can remain continuously staffed. Ask how coverage continues through leave, breaks, training and absence. A plan requiring one person to be in two places simultaneously needs clarification regardless of its price.
Break the cost into comparable items
Identify labour, applicable benefits, relief, site induction, uniforms, equipment, software, maintenance and management services separately. Record whether each is included and when an extra charge applies. Compare tax, price-adjustment and contract-duration assumptions consistently.
Ask why a lower proposal differs rather than immediately alleging non-compliance or bad faith. Where a reduction is linked to a specified change in duties, time or equipment, assess that change's operational consequences.
Test technology savings against actual duties
Cameras and patrol software can support some activities without taking over every on-site function. Do not calculate a staffing reduction before deciding who assesses alarms, receives visitors and covers equipment failure. No universal ratio establishes how many officers a system can replace.
Ask the supplier to show how duties are covered under both the existing and proposed models. Acceptance criteria should address whether alerts are understandable and reach someone able to act, rather than merely whether a device switches on. Zero-error or zero-risk promises do not replace measurable service conditions.
Verify what a certificate actually covers
Operating permissions, officer identification and relevant insurance require separate checks. For a management-system certificate, examine the organisation, scope, covered sites, validity and certification body. ISO explains that it does not itself issue certificates; verify the actual body named on the document.
ISO 31000 provides risk management guidance and, according to ISO, cannot be used for certification purposes. Instead of imposing a generic ISO 31000 company certificate requirement, ask how the supplier assesses and monitors risk. A valid certificate to another standard also does not, by itself, demonstrate flawless performance on the ground.
Design the decision and mobilisation checks together
The decision file should show mandatory conditions, quality considerations, total cost and unresolved assumptions. Do not change criteria or weightings afterwards to fit a preferred outcome. Decide which staff, training, equipment and records will be checked when service begins. Plan workforce-compliance monitoring separately, without assuming that one contract clause transfers every statutory responsibility. A good comparison explains why the chosen service fits the need, rather than defending a price in isolation.
