Study guide

12.2 RFP, RFQ, IFB & Sole Source

ASIS Physical Security Professional PSP

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current PSP Exam Facts 1.2 Eligibility, Fees, Scheduling & Recertification 1.3 Experience-Based Testing, References & Study Approach

2 Assessment Planning & Methods

2.1 Assessment Plan, Stakeholders, Budget & Resources 2.2 Inside-Out, Outside-In, Site-Specific & Functional Models 2.3 Qualitative vs Quantitative Assessment Methods 2.4 Standards, Regulations, Codes & Where to Find Them

3 Asset Identification & Valuation

3.1 Asset Types, Terminology, Value, Criticality & Loss Impact 3.2 Valuing Tangible and Intangible Assets for Operations 3.3 Criticality, Key Areas & Loss-Impact Prioritization

4 Threats, Hazards & Operating Environment

4.1 Criminal, Terrorist, Insider & Sociopolitical Threats 4.2 Natural Disasters, Accidental & Cyber-Physical Hazards 4.3 Geography, Crime, Socioeconomics & Existing Countermeasures 4.4 Neighbors, Competitors, Legal, Reputation & Supply Chain

5 Vulnerability Assessment & Surveys

5.1 Surveys, Interviews, Incident Data, Crime Stats & Benchmarking 5.2 Evaluating Technology, Personnel & Procedures 5.3 Plans, Schematics & Environmental/Site Factors

6 Risk Analysis & Countermeasure Selection

6.1 Risk Analysis Strategies, Principles & Data Interpretation 6.2 Threat/Hazard–Vulnerability Pairing & Loss Event Profiles 6.3 Matching Countermeasures to Specific Risks 6.4 ROI, Total Cost of Ownership, Privacy, PII & Life Safety

7 Performance Requirements & Security Concepts

7.1 Design Constraints & Incorporating Risk Analysis 7.2 CPTED, Defense-in-Depth, 4 Ds & Security Terminology 7.3 Operational, Functional, Performance Requirements, Codes & Metrics

8 Structural Measures & CPTED Application

8.1 Fences, Gates & Perimeter Barriers 8.2 Blast Mitigation, Ballistic Protection & Hostile Vehicle Mitigation 8.3 Lighting, Locks, Doors, Windows & Glazing 8.4 Applying CPTED to Site Planning & Landscaping

9 Electronic Security Systems

9.1 Electronic Access Control Architecture & Credentials 9.2 Biometrics, Electrified Locks, Anti-Passback & Mantraps 9.3 Video Surveillance Design, Storage & Analytics 9.4 Intrusion Detection Sensors & Alarm Communications

10 Screening, Communications, Power & Networks

10.1 Personnel, Package & Vehicle Screening and Visitor/Vendor Policy 10.2 Mass Notification, Audio Comms, Consoles & Central Stations 10.3 Data Storage, Retention, PII & Physical Network Security 10.4 Primary/Backup Power and Copper, Fiber & Wireless Transmission

11 System Design & Project Documentation

11.1 Pre-Design, Schematic, Construction Docs, Calculations & Drawings 11.2 CSI MasterFormat, Owner Standards & AIA MasterSpec 11.3 Systems Integration, Scheduling, Cost Estimation & Value Engineering

12 Pre-Bid Meetings & Solicitation Packages

12.1 Site Visits, RFIs, Substitution Requests & Pre-Bid Meetings 12.2 RFP, RFQ, IFB & Sole Source 12.3 SOW, Timelines, Costs, Personnel & Documentation 12.4 Evaluation Criteria, Technical Compliance & Contracting Ethics

13 Procurement Planning & Vendor Selection

13.1 Procurement Process for Security Goods & Services 13.2 Interviews, Due Diligence, References & Selection 13.3 Project Management Functions in Procurement

14 Installation, Commissioning & Acceptance

14.1 Installation & Inspection Techniques 14.2 Commissioning & Implementation-Phase Integration 14.3 FAT, SAT & Final Acceptance Testing Criteria 14.4 Punch Lists, As-Builts, Config Management & End-User Training

15 Security Personnel Requirements

15.1 Roles, Limits, Proprietary vs Contract Staffing 15.2 Recruiting, KPIs, Discipline & Professional Development 15.3 Post Orders, Uniforms/Equipment & Non-Security Awareness

16 Lifecycle Maintenance & Program Evaluation

16.1 Preventive/Corrective Maintenance, Calibration, Service Agreements & Warranties 16.2 Upgrade Training, System Evaluation & Replacement

12.2 RFP, RFQ, IFB & Sole Source

Key Takeaways Explain This Topic AI

An RFP seeks best value and may include negotiation; it fits integrated security systems and many professional services where method matters

An RFQ collects qualifications and is a gate or shortlist step, not an award of a full install by itself

An IFB or ITB is sealed low bid among responsive, responsible bidders and fits a fully defined scope

Sole source requires written justification and extra ethics scrutiny; popularity of an OEM is not a justification

Match the package to the purchase: systems with integration risk, officer contracts with specified posts, and consulting assessments do not all use the same vehicle

Last updated: September 2026

RFP, RFQ, IFB, and Sole Source

Independent ExamFinch teaching for published PSP Domain 3 Task 1 knowledge is that the solicitation type is a design decision about how you will choose a seller, not a synonym for “send an email for prices.” Four labels show up on PSP-style items: request for proposal (RFP) , request for qualifications (RFQ) , invitation for bid / invitation to bid (IFB/ITB) , and sole source . Each one is appropriate for some security purchases and a poor fit for others. Section 12.1’s walks, RFIs, and addenda sit inside whichever label you pick.

Exam focus: RFP is best-value and often negotiated. IFB/ITB is sealed low bid on a complete spec. RFQ asks who is qualified. Sole source needs a written justification and extra ethics care.

Request for proposal: best value, method, and negotiation

An RFP asks offerors to propose how they will meet a statement of work, not only how little they will charge. Evaluation typically uses published criteria (cost, experience, schedule, certifications, resources) and may include discussion, interviews, demonstrations, and a best-and-final offer. Public owners who use RFP still have to follow their statute; “negotiated” does not mean “secret lunch.” Private owners who use RFP still owe the file a documented reason for the winner.

RFP is the workhorse when the integration method matters . A campus access-control and video upgrade with a live database, a required identification plane at the badge desk, phasing around occupied clinics, and a need for manufacturer-certified technicians is not a pile of identical cameras. Two firms can meet the shall-language with different architectures, different cutover plans, and different residual risk during construction. Best value lets you score that instead of pretending the lowest camera-body price is the same job.

RFP is also the usual vehicle for professional services that are not a sealed commodity: a physical security assessment, a design package, or a commissioning agent. You are buying judgment. Lowest hourly rate without a work plan is how you get a three-page survey that never walked the dock. Ask for a method, a sample residual-risk sentence, and named assessors—not a brochure cover.

Guard and officer services can go RFP when you care about supervision ratios, training, relief, transition from an incumbent, and how posts will actually be filled on a holiday weekend—not only the wage multiplied by hours. If you have already written complete post orders, hours, and wage rules, some owners still use IFB. The exam distinction is whether method and quality remain open. A “security services RFP” that is only a price sheet is an IFB wearing the wrong label.

Worked system example: two proposers offer the same device count. Firm A includes a weekend pharmacy cutover plan, factory-certified technicians, and a documented HR termination feed. Firm B is cheaper and assumes weekday access to the anteroom. An IFB would award Firm B if the paperwork is clean. An RFP can score Firm A’s method as better value if you published that criterion. The package type decided the outcome before anyone opened a box.

Request for qualifications: who may play, not yet the price

An RFQ (sometimes a request for qualifications or a prequalification questionnaire) collects experience, licenses, bonding capacity, manufacturer certifications, safety record, and key personnel . It does not , by itself, award a two-million-dollar install. Typical uses:

Shortlist design consultants or assessment firms before an RFP for the study.

Prequalify integrators who are allowed to submit an IFB or RFP for the system, so you do not open a sealed bid from a firm that cannot get the factory certification or a bond.

On-call or indefinite-quantity lists for small security work.

The trap is treating RFQ as a disguised award: picking a friend on qualifications, then negotiating a full campus system with no competition and no documented sole-source. Qualifications are a gate . The purchase still needs an RFP, IFB, or a justified sole source.

RFQ is a strong fit for a consulting assessment . You want people who have done hospital pharmacies or logistics yards, who can write residual-risk language, and who will not sell you their integrator’s catalog as a survey. Price of the study can follow in a second step or in a combined qualifications-and-proposal package. What RFQ is not: a way to skip a scope of work for an installation contractor.

Two-step patterns are common and legitimate: RFQ to a shortlist, then RFP or IFB to that shortlist. Publish both steps. Do not add a secret third step that only the incumbent hears about.

Invitation for bid / invitation to bid: sealed low bid

An IFB or ITB is the classic sealed low bid . The owner issues complete drawings and specifications. Bidders submit a price (and required forms) by a deadline. The public owner typically awards to the lowest responsive, responsible bidder. Responsive means the bid follows the instructions (addenda acknowledged, bid bond attached, mandatory walk attended). Responsible means the firm can actually perform (license, bond, factory authorization, not debarred). A rock-bottom number from an unlicensed firm is not a bargain. It is a reject.

IFB is appropriate when the scope is fully defined and the remaining difference is price: a well-specified run of matching readers on an existing panel, a fence that is already designed, a quantity of identical locks. It is a poor fit when the owner is still deciding architecture, when or-equal chaos is expected, or when the “spec” is a two-page wish list. Incomplete IFB documents are how low bidders win and then live on extras.

Security systems can be IFB when Domain 2 actually finished: door schedules, device counts, cable, software licenses, training hours, spare parts, and as-built requirements are all in the book. If those are missing, use RFP or finish the design. Do not IFB a “design-build security system” unless you have also written how design liability, performance, and acceptance will work. Many owners who want design-build use RFP for that reason.

Guard services can be IFB when posts, hours, prevailing or living-wage rules, licensing, and post orders are fully specified and you are truly buying hours. The lowest responsible bid still has to clear insurance and licensing screens. IFB is a weak fit when you have not decided whether the post is proprietary or contract, or when you need a proposer to invent a staffing model.

Sealed bid also means a communications freeze after issuance except through RFIs. A public bid opening may read prices aloud. That ritual does not replace a responsiveness check. The apparent low bidder can still die on a missing addendum acknowledgment.

Sole source: justification, not convenience

Sole source (or single source / noncompetitive) means only one seller will be asked to provide the goods or services. It is sometimes legitimate:

Proprietary software or a head-end that cannot take a second manufacturer without ripping out a live credential database the owner will not rebadge this year.

A manufacturer-only service contract required to keep a listing or a warranty.

True emergency (a failed vault lock on a Friday), documented, and limited to the emergency scope—not a campus redesign smuggled through the outage.

Compatibility with an installed standard the owner has formally adopted, with a file that says so.

It is not legitimate because the designer likes a demo, because an incumbent already has keys, because writing a competitive spec takes time, or because a gift relationship exists. “We have always used Brand X” is incumbency, not a sole-source fact, unless switching is technically impossible this cycle.

Public procurement typically demands a written justification , legal review, and sometimes a public notice that other firms may protest. Private owners have more flexibility but still have fiduciary and ethics exposure if a buyer steers work for personal benefit. Section 12.4 returns to designing a spec around one OEM without disclosure.

Sole source for guard services is rarely honest. Officer labor is widely available. An emergency weekend fill is a short sole-source; a five-year campus contract is not. Sole source for a consulting assessment is equally hard to defend unless a unique expert is required for a named, unusual occupancy and the file says why others cannot perform.

Worked contrasts:

Purchase Better default package Why

Integrated ACS plus VMS with phasing and identification performance RFP (best value) Method, certified techs, and cutover plan matter

Forty matching readers on a named existing panel, complete drawings IFB/ITB Scope is defined; remaining issue is price

Physical security assessment or design consultant RFQ then RFP, or qualifications-based RFP You are buying judgment

Officer contract with full post orders and hours IFB or RFP depending on how much quality scoring you need Hours can be IFB; supervision models often RFP

Unique head-end software with no workable alternative this year Sole source with a file Compatibility justification, not a brochure

If the owner wants “best camera” and “lowest price” and “no arguments,” they are asking for RFP and IFB at once. Pick the one that matches whether method is still open. Then build the package components in 12.3 so the chosen vehicle has something real to price.

Loading diagram... Choose the solicitation by what you are buying