How to Write a Security Guard RFP in India: Template and Evaluation Guide

A security guard RFP is not a procurement formality. It is the document that defines what you expect, creates accountability for what you receive, and gives you the contractual basis to enforce performance standards. Most RFPs in India are three pages long and evaluate on price. Most security contracts in India underperform from day one.

The connection is not coincidental. A well-designed RFP forces vendors to commit to specifics — staffing models, compliance standards, supervisory ratios, technology tools, incident response timelines. A thin RFP creates space for every vendor to promise quality and deliver minimum viable service.

Section 1: Company Overview and Scope of Work

Open the RFP with a precise description of your facility: location, size (square footage or acreage), number of buildings, hours of operation, number of employees and daily visitors, and any special zones (data centres, cash handling areas, hazardous materials storage). This is the baseline from which vendors design their proposals.

Define the scope explicitly: which entry and exit points require coverage, which shifts must be staffed, whether armed guards are required at specific posts, whether patrol vehicles are needed, and whether the scope includes CCTV monitoring or only guard deployment. Ambiguity in scope is the root cause of most post-contract disputes.

Section 2: Mandatory Compliance Requirements

State non-negotiable requirements as disqualifiers, not evaluation criteria. If a vendor does not meet these, their bid should be rejected without further review. This is the section most RFPs skip — and the reason non-compliant vendors routinely win on price.

• Valid PSARA license for every state in the scope of deployment — attach a certification requirement
• Minimum 3 years of documented operation in the relevant sector (IT, manufacturing, retail, etc.)
• 100% statutory compliance across PF, ESIC, minimum wage — require submission of last 6 months EPF challans
• Police verification certificates for all guards — state turnaround time requirement
• Public liability insurance with minimum coverage of ₹1 crore per incident
• ISO 9001 certification or equivalent quality management system documentation (preferred, or mandatory if your standards require it)

Section 3: Staffing Proposal Requirements

Require vendors to submit a staffing model, not just a headcount. The model must include: guard positions with specific post assignments, shift structure (timings and rotation), relief guard provision (typically 25% above core deployment to cover weekly offs and leave), supervisor-to-guard ratio, and the qualifications profile for each post (armed, unarmed, ex-serviceman, specific training certifications).

Section 4: Technology and Reporting Standards

Specify exactly what technology infrastructure you require and what reporting you expect. Vague requirements ("we use modern technology") produce vague commitments. Precise requirements produce verifiable commitments.

1. 1.GPS-enabled patrol tracking with client-accessible dashboard and patrol completion reports on request
2. 2.Digital daily occurrence reports submitted to the client by 09:00 each morning
3. 3.Incident reports: preliminary within 4 hours, final within 24 hours, using a structured format (who, what, when, where, action taken, outcome)
4. 4.Monthly performance review data: patrol compliance rate, incident count by category, personnel attendance rate
5. 5.Visitor management integration capability (if applicable to your site)

Section 5: Service Level Agreement Parameters

The SLA section of the RFP defines the performance standards you will hold the vendor to. Include measurable thresholds and associated penalties for non-compliance. Without penalties, SLA commitments are aspirational, not contractual.

• Guard absenteeism: maximum 5% per month; replacement within 2 hours of reported absence
• QRT response: on-site within 30 minutes of dispatch call
• Incident reporting timeliness: 95% of reports submitted within contracted window
• Supervisory visit frequency: minimum twice per site per week, logged and verifiable
• Training currency: all guards complete annual refresher training; records available on request
• Penalty structure: define credit amounts for each SLA breach (e.g., 1% of monthly invoice per unfulfilled replacement guarantee)

Section 6: Commercial Bid Structure

Require vendors to submit a fully loaded commercial bid that breaks out: basic wages per guard category, statutory contributions (PF, ESIC, gratuity provision, bonus), agency service charge, and any additional costs (uniforms, equipment, transport). A bid that bundles all costs into a single per-guard rate is hiding the compliance structure.

Require vendors to certify that the commercial bid is compliant with the minimum wage notification of the relevant state. Any bid that appears to fall below minimum wage after subtracting statutory contributions should be queried formally before disqualification.

Common Mistakes in Security RFPs

• Evaluating all bids on price per guard without verifying the compliance structure underneath
• Accepting vague technology claims ("we use GPS tracking") without requiring a product demonstration
• Not requiring references from clients in the same industry sector
• Failing to specify the penalty structure for SLA non-compliance
• Not visiting the vendor's training facility or operations centre before award
• Setting an award timeline so short that compliance verification is impossible

Evaluation Scoring Framework

A professional evaluation scores vendors across multiple dimensions, not price alone. A suggested weighting for a mid-sized deployment: compliance credentials (25%), staffing model and workforce quality (20%), technology and reporting capability (20%), references and track record in sector (15%), SLA terms and penalty acceptance (10%), commercial bid (10%). Price at 10% weight forces quality to the front of the evaluation.