Section 1: What Are RFPs?
Introduction
An RFP (Request for Proposal) is a formal document issued by an organization seeking vendors to provide services for a specific project or ongoing need.
RFPs are commonly used by:
- Government agencies
- Corporations
- Construction firms
- Event organizers
They outline:
- Scope of work
- Timeline
- Requirements
- Submission process
Key Understanding
Not all RFPs will clearly state “security services.”
In many cases:
- Security is embedded within a larger project
- Or implied through operational requirements
Your Role
You are not responsible for bidding on RFPs.
You are responsible for:
- Identifying potential opportunities
- Determining relevance
- Capturing key information
- Flagging opportunities for internal review
Key Principle
RFPs are a source of opportunities—not instructions to act.
Section 2: Where You’ll Find RFPs and Public Opportunities
Common Platforms
You may encounter opportunities on:
- ConstructConnect
- BidNet
- R.A.M.P.
- Procurement.opengov.com
Additional Sources
- Event listing platforms (Eventbrite, venue calendars)
- City and county procurement websites, such as Anaheim.net
- Convention center schedules
- Industry-specific directories
Key Insight
Different sources provide different types of opportunities:
- Construction platforms → long-term, asset-focused
- Government platforms → structured contracts
- Event listings → short-term, high-volume needs
Your Responsibility
- Monitor approved sources
- Identify potential opportunities
- Capture relevant information
Do NOT:
- Reach out to clients
- Submit bids
- Initiate sales conversations
Section 3: How to Scan an RFP Quickly
Purpose
You are not expected to read every RFP in full detail. You must be able to quickly determine relevance.
The 30–60 Second Scan Method
When reviewing an RFP, answer:
1. What is the project?
- Construction
- Event
- Facility operations
- Infrastructure
2. Where is it located?
- Within service area?
- Requires travel?
3. What is the timeline?
- Start date
- Duration
- Urgency
4. Is security:
- Explicitly stated?
- Implied?
- Not relevant?
Decision Outcome
After scanning, determine:
- Relevant → proceed to capture
- Possibly relevant → flag for review
- Not relevant → discard
Key Principle
Do not overanalyze—identify relevance quickly and move on.
Section 4: Identifying Hidden Security Opportunities
Introduction
Many RFPs will not explicitly request “security guards,” but may still require security services.
Keywords That Indicate Security Needs
Look for terms such as:
- “Site monitoring”
- “Access control”
- “Public safety”
- “Asset protection”
- “Crowd management”
- “Overnight presence”
- “Controlled entry”
Common Scenarios
Construction Projects
- Equipment on-site
- Open access areas
- Long timelines
Likely need for:
- Patrols
- Overnight security
- Access control
Events
- Large attendance
- Public interaction
- VIP presence
Likely need for:
- Crowd control
- Entry management
Infrastructure Projects
- Public exposure
- Traffic control
- Extended timelines
Likely need for:
- Monitoring
- Safety presence
Key Principle
Security is often implied through risk—not stated directly.
Section 5: Classification Framework
Step 1: Opportunity Type
Classify each RFP as:
Direct Security Opportunity
- Security services clearly requested
Implied Security Opportunity
- Security not stated, but risk factors indicate need
Not Relevant
- No connection to security services
Step 2: Quality Assessment
High-Quality
- Clear scope
- Defined timeline
- Realistic scale
- Strong alignment
Medium-Quality
- Partial information
- Some uncertainty
- Requires clarification
Low-Quality
- Missing key details
- Weak alignment
Red Flag
- Unrealistic timeline
- Vague scope
- High risk
Key Principle
Classification determines action—not assumptions.
Section 6: Action Framework
What to Do After Classification
Scenario 1: Direct + High-Quality
✔ Action:
- Complete intake
- Log lead
- Mark:
Ready for Qualification
Scenario 2: Implied Opportunity
✔ Action:
- Capture available details
- Add notes on why security may be needed
- Mark:
Needs Internal Review
Scenario 3: Incomplete or Medium Quality
✔ Action:
- Log as incomplete
- Flag missing details
- Do NOT escalate
Scenario 4: Not Relevant
✔ Action:
- Do not log as a lead
- Discard
Escalation Rule
Only escalate when the opportunity is clear, relevant, and properly documented.
Critical Rule
Do not interpret beyond the information provided.
Common Mistakes to Avoid
- Treating all RFPs as opportunities
- Assuming security is required without evidence
- Escalating incomplete or unclear projects
- Attempting to act outside your role
Section 6 Key Takeaway
RFP evaluation is about:
- Identifying relevance
- Recognizing risk
- Capturing accurate information
- Supporting informed decision-making
RFP Case Studies
This Lesson Prevents:
- Chasing irrelevant RFPs
- Missing hidden opportunities
- Wasting time on low-value projects
- Escalating unclear opportunities
1. Construction RFP
RFP Summary
Platform: ConstructConnect
Project: New commercial retail development
Location: Ontario, CA
Timeline: 8 months
Scope includes:
- Site fencing
- Equipment storage
- “Site monitoring and safety compliance required”
Classification
⚠️ Potential Lead (Hidden Opportunity)
Why
- Security not explicitly stated
- BUT:
- Equipment on-site
- Long duration
- Monitoring requirement
Key Insight
Construction projects often:
- Do not say “security guards”
- But require:
- Theft prevention
- Overnight presence
- Access control
What the Admin Should Do
- Flag as Potential Construction Security Opportunity
- Capture:
- Location
- Timeline
- Scope notes
- Mark as:
Needs Internal Review (Not Ready Yet)
2. Government RFP
RFP Summary
Platform: BidNet
Agency: City Parks Department
Request:
- Security services for public parks
- Evening + weekend coverage
- 1-year contract
Classification
✅ High-Quality Lead
Why
- Security explicitly requested
- Defined scope
- Long-term contract
- Government entity
Highlights
- Recurring revenue
- Structured contract
What the Admin Should Do
- Complete intake
- Mark:
Ready for Qualification - Prepare Opportunity Brief
3. Event RFP
RFP Summary
Platform: R.A.M.P.
Event: City-sponsored festival
Location: Downtown Los Angeles
Timeline: 3 weeks away
Details:
- Crowd expected: 5,000+
- Mentions:
- “Public safety coordination”
- “Crowd management support”
Classification
⚠️ Medium-Quality (Time Risk)
Why
- Clear event
- Security implied
- BUT:
- Short timeline
- Large staffing requirement
Red Flags
- High volume + short notice
What the Admin Should Do
- Capture all details
- Flag:
Time-Sensitive / Feasibility Risk - Escalate with caution (after intake)
4. Construction RFP
RFP Summary
Platform: ConstructConnect
Project: Interior office renovation
Location: San Diego
Scope:
- Electrical
- Plumbing
- Interior finishes only
- No mention of site security, storage, or access control
Classification
❌ Low-Quality / Not a Lead
Why
- No external exposure
- No asset risk
- No access control needed
What the Admin Should Do
- Do NOT log as a lead
- Discard
5. Large Infrastructure Project
RFP Summary
Platform: BidNet
Project: Highway expansion
Location: Riverside County
Timeline: 18 months
Scope includes:
- Equipment staging areas
- Traffic control zones
- “Site safety and monitoring required”
Classification
✅ High-Value Potential Lead
Why
- Long-term project
- High asset exposure
- Public interaction
Insight
Even if security isn’t stated:
Large infrastructure = high likelihood of security needs
What the Admin Should Do
- Capture full details
- Flag:
High-Value Opportunity (Needs Review) - Prepare a summary for leadership
6. Vague RFP
RFP Summary
Platform: BidNet
Request:
- “Support services for upcoming project”
- No location
- No timeline
- No scope
Classification
⚠️ Red Flag / Low-Quality
Why
- No usable information
- Cannot evaluate
What the Admin Should Do
- Do NOT escalate
- Do NOT assume
- Only proceed if more info is available
7. Private Sector Event Listing
RFP Summary
Platform: Event listing site
Event: Private corporate gala
Location: Newport Beach
Details:
- 800 attendees
- VIP guests
- Alcohol service
Classification
⚠️ Potential Lead (Security Implied)
Why
- High-risk environment
- Crowd + VIP presence
What the Admin Should Do
- Capture details
- Flag:
- Event Security Opportunity
- Do NOT initiate outreach without approval
RFP Evaluation Framework
Every RFP should go through:
Step 1: Classification
- Direct Security Request
- Implied Security Need
- Not Relevant
Step 2: Quality Assessment
- High-quality
- Medium
- Low
- Red flag
Step 3: Action
| Scenario | Action |
|---|---|
| Clear + relevant | Intake + track |
| Implied opportunity | Flag for review |
| Incomplete | Hold / gather info |
| Not relevant | Discard |
Key Patterns
1. Security Is Often Implied, Not Stated
Especially in:
- Construction
- Infrastructure
- Events
2. Bigger Projects ≠ Better Opportunities
Must still evaluate:
- Timeline
- Feasibility
- Scope clarity
3. Do NOT Chase Every RFP
Focus on:
- Alignment
- Clarity
- Viability
Key Takeaway
RFP platforms are a powerful source of opportunities—but only if evaluated correctly.
Your role is to:
- Identify relevant opportunities
- Recognize implied security needs
- Capture accurate information
- Flag opportunities appropriately
Not to:
- Interpret beyond available data
- Initiate outreach
- Make assumptions
What This Leads Into
After completing this lesson, you are now prepared for:
Capstone Scenario Assessment
Where you will:
Demonstrate readiness for live opportunities
Evaluate real-world scenarios
Apply classification and intake