What colleges should include in a campus security services RFP

Selecting a campus security provider is more than purchasing officer hours. The decision affects daily operations, emergency coordination, student interactions, and institutional reputation.

A well-constructed campus security services RFP gives qualified providers enough information to propose a realistic operating model. It also creates a consistent basis for comparing capabilities, pricing, assumptions, and accountability.

Begin with the campus environment and desired outcomes

The RFP should explain how the institution operates, not simply list buildings and posts. Include the campus footprint, residential and commuter populations, major events, seasonal changes, and relationships with campus police or public safety.

Then define what the program should accomplish. Desired outcomes might include dependable coverage, stronger incident documentation, better coordination, improved visibility, or a more consistent student experience. Distinguish required duties from broader outcomes so bidders understand both the work and its purpose.

Define scope, authority, and operational boundaries

Specify the locations, schedules, posts, patrol areas, and service periods included in the contract. Identify responsibilities such as access support, mobile patrols, residence hall coverage, safety escorts, event security, incident reporting, or dispatch support where applicable.

The RFP should also clarify reporting lines, limits of authority, escalation procedures, and the relationship between contracted officers and internal departments. Clear boundaries reduce assumptions that can create service gaps or unexpected costs.

Require a complete staffing and supervision plan

Ask each bidder to show how it will recruit, deploy, supervise, and retain personnel. The response should address:

• The proposed account leadership and supervisory structure
• Candidate screening, onboarding, and campus orientation
• Relief coverage for vacancies, absences, and demand surges
• Scheduling controls and procedures for unfilled posts
• Contingency staffing for events or emergencies
• Communication between field leadership and college stakeholders

The evaluation should look beyond proposed headcount. Colleges should understand how the provider will sustain staffing after launch and correct performance issues.

Evaluate training and campus fit

The RFP should separate foundational officer training from campus-specific preparation. Ask bidders to describe instruction in de-escalation, emergency procedures, professional communication, incident reporting, institutional policies, and respectful interaction with diverse campus communities.

Require details on training frequency, documentation, refresher requirements, and remediation. Colleges can use these questions alongside broader guidance on how to evaluate a campus security partner to distinguish routine guard coverage from a program designed around higher education operations.

Address technology, data, and performance reporting

Identify the systems the selected provider must supply, access, or integrate with, including incident reporting, patrol verification, communications, access control, video, or dispatch platforms. Define data ownership, access permissions, retention expectations, privacy requirements, and cybersecurity responsibilities.

Ask for sample operational reports and proposed performance measures. Useful categories may include staffing fulfillment, response activity, patrol completion, training status, incident trends, corrective actions, and stakeholder concerns. The RFP should state how often performance reviews will occur and who will participate.

Make transition readiness a scored requirement

A proposal should include an implementation schedule covering recruiting, incumbent communication, post orders, uniforms and equipment, system access, training, stakeholder introductions, and go-live contingencies.

The RFP should also address continuous improvement after transition. Require bidders to describe quality assurance, account reviews, corrective actions, seasonal planning, and change control before the contract begins.

Structure pricing and responses for accurate comparison

Provide a standard template so bidders use the same pricing assumptions. Request separate rates for regular hours, overtime, holidays, supervision, special events, training, equipment, technology, and transition. Require bidders to identify exclusions and conditions that could change pricing.

This structure helps the team compare total program value instead of relying on one hourly rate.

Weight criteria such as staffing, training, campus integration, technology, reporting, transition, pricing, references, and contract exceptions. Require a common response format, page limits, attachments, and assumptions.

Campus-specific scenarios can also reveal how bidders think. Ask how they would address an unfilled overnight post, a major event, a recurring reporting problem, or a sudden increase in service demand. Structured questions make generic sales responses easier to identify.

Build the RFP around long-term partnership

The strongest campus security services RFP translates institutional needs into clear service requirements and measurable expectations. When colleges define their environment, operating relationships, performance standards, and decision criteria upfront, they are better positioned to select a provider that can support both immediate coverage and long-term program improvement.

Ready to prepare an RFP or review your current campus security contract? 

Talk to a GardaWorld Security campus security expert about defining requirements for a coordinated, accountable security program. 

Speak with a Campus Security expert