Security and Guarding Technical Proposal: How to Win Public Surveillance Contracts
Private security and guarding contracts in the public sector (government buildings, museums, sensitive sites, events) are heavily regulated. Beyond standard technical proposal requirements, the buyer verifies that your company complies with the Internal Security Code and that your staff hold all required authorisations. Reliability, responsiveness, and intervention traceability are the differentiating criteria.
Specific requirements for security contracts
The buyer evaluates: your CNAPS operating licence (mandatory), individual professional cards for all agents, your site-specific security plan (patrol routes, access control, incident procedures), your staffing organisation (shifts, replacements, supervision), technical equipment (CCTV, access control, radio communications), and your coordination protocol with emergency services.
Without a valid CNAPS licence, your application is automatically rejected — this is a mandatory eligibility criterion.
Recommended structure for a security proposal
A strong security proposal covers:
Security plan and procedures
Present a detailed security plan: patrol routes with checkpoints and frequencies, access control procedures, alarm response protocols, incident reporting system. Include a site plan showing coverage zones and critical points.
Staffing and qualifications
Detail your team: number of agents per shift, supervisor roles, CNAPS professional cards, SSIAP fire safety qualifications if required. Address your replacement policy for absences and your staff vetting process.
Technical equipment
Describe the technology deployed: CCTV systems, access control, patrol verification systems (NFC/GPS), radio communications, reporting software. Explain how technology enhances your human security operations.
Coordination and reporting
Detail your coordination protocol with the client and emergency services. Describe your reporting system: daily logs, incident reports, monthly statistics. The buyer needs visibility on your operations.
Common mistakes in security proposals
Missing CNAPS documentation — Not providing valid CNAPS operating licence and agent professional cards upfront is an immediate rejection.
Generic security plan — A plan that doesn't reference the specific site layout, access points, and threat assessment is unconvincing.
No replacement strategy — Security is 24/7 — failing to explain how you cover absences, holidays, and emergencies is a critical gap.
Ignoring SSIAP requirements — If the site requires fire safety staff, not detailing SSIAP qualifications and integration with the security team is a serious omission.
Maître AO: your security technical proposal in minutes
Maître AO analyses your security tender documents and generates a structured proposal: security plan, staffing organisation, technical equipment, coordination protocols. Add your CNAPS documentation, staff qualifications, and site references, then export a professional document ready for submission.
Analyse your security tender free
1 free analysis — No commitment
Frequently asked questions
Related guides
Ready to win more public contracts?
Join SMEs that respond 3x faster to public tenders.
Start for free →1 free project • No commitment • Setup in 2 minutes