The short answer
There are two credible ways to buy contract security, and the mistake most buyers make is applying one to a job that needs the other.
A request for proposal is a structured competition. You write a scope of work, publish it, take questions from bidders, receive sealed technical and cost proposals, score them against weighted criteria, negotiate, award, and then run a transition period before the first officer stands a post. Done properly it takes weeks to months, and it is genuinely the right instrument when the contract is large, spans many sites, will run for years, or is subject to a public-procurement rule that requires competition above a dollar threshold.
Instant booking is the opposite shape. You describe a defined post, see rates from vetted local agencies, and confirm coverage without a formal solicitation. It fits jobs where the scope is already clear, the horizon is short or uncertain, or the need is urgent enough that a two-month procurement cycle is not a real option.
Neither is a shortcut around the other. An RFP applied to a single overnight post at one warehouse buys you months of process to solve a problem that could have been staffed in days. Instant booking applied to a fifteen-site national program skips exactly the diligence that program needs.
Compare published guard rates before either path →
What an RFP actually involves
It helps to walk the process, because "we'll put it out to bid" hides a lot of labor.
1. Scoping and requirements definition
This is the part that determines whether the whole exercise produces anything useful, and the part buyers most often rush. You have to define post locations, hours and staffing levels by shift, guard duties (access control, roving patrol, screening, incident response), armed versus unarmed by post, supervision structure, reporting requirements, uniform and equipment expectations, and the licensing, insurance, and background-screening standards a bidder must meet. Vague scope produces vague proposals, and vague proposals cannot be scored against one another.
If you already know your scope in this much detail, note that: it is one of the strongest signals about which path you need, and we come back to it below.
2. Solicitation and the question period
Once published, bidders get a window to submit written questions, and the issuing organization answers all of them in a public addendum so no bidder gets private information. This is a real timeline cost, but it is also where genuine ambiguities in your scope surface before they become contract disputes.
3. Proposal submission
Serious security RFPs typically require two separately sealed submissions: a technical or business proposal covering qualifications, staffing plan, supervision model, training, and transition approach, and a separate cost proposal. Separating them is deliberate. It lets an evaluation committee score capability before price anchors the discussion.
4. Evaluation and scoring
Proposals are scored against weighted criteria published in the solicitation. Common categories include relevant experience and references, staffing and recruiting capability, supervision and quality-assurance structure, compliance and licensing, response and escalation capability, technology and reporting, transition plan, and price. The weighting is the buyer's real statement of priorities. An RFP that puts 70 percent of the weight on price will get you the lowest bidder, and in an industry that runs on thin margins and high turnover, that is often exactly the wrong outcome.
5. Award, negotiation, and contract
Scoring narrows the field; negotiation settles terms. This is where rate escalation caps, termination rights, indemnification, and insurance requirements get pinned down. Our guide on what belongs in a security guard contract covers the specific clauses worth fighting for, and an RFP gives you more leverage over them than a routine booking ever will.
6. Transition and mobilization
The step buyers forget. After award, the winning agency has to recruit or reassign officers, license and badge them for your site, write and distribute post orders, train on your systems, and phase in coverage without a gap. Transition plans in this industry commonly run 30 to 60 days, and on complex sites longer. If you are switching from an incumbent, the transition is where continuity is either preserved or lost.
Realistically, a straightforward services RFP runs a few weeks end to end; a complex multi-site one with a formal transition can run several months. Both numbers are before the first shift is worked.
Where the RFP process earns its cost
It would be dishonest to frame the RFP as pure overhead. It does specific work that no fast path does:
- •It forces scope discipline. Writing a real statement of work surfaces the questions you were going to discover six weeks in anyway, at a point where they are still cheap to answer.
- •It makes bids genuinely comparable. Everyone is answering the same document with the same assumptions, so a price difference means something.
- •It creates a defensible record. For public agencies, school districts, housing authorities, and anyone spending grant money, the paper trail is not optional. Competitive-bid thresholds are set by statute and local policy, and above them a formal solicitation is legally required, not a preference.
- •It gives you leverage on terms. Contract language is most negotiable before award. Once you are a live account, your leverage drops sharply.
- •It tests capability, not just price. A well-built evaluation matrix can rule out an agency that cannot actually staff your overnight shift, which a rate sheet never will.
If those five things matter to your job, run the RFP. It is the correct answer, and no marketplace pitch should talk you out of it.
Where the RFP process adds delay without adding value
The same machinery misfires when it is pointed at the wrong problem.
- •When your scope is already settled. If you know you need one unarmed officer, 2200 to 0600, five nights a week, at one address, there is nothing for a discovery-oriented process to discover. You are running a competition to answer a question you have already answered.
- •When the timeline is shorter than the procurement. A ninety-day construction phase does not survive a sixty-day solicitation. Neither does a court date, a terminated-employee escort, or a protest expected next weekend.
- •When the contract is too small to attract good bidders. Responding to an RFP costs an agency real money. Below a certain contract value, the strong local operators simply do not bid, and you end up scoring a thin field that does not represent the market.
- •When the need is genuinely uncertain. RFPs award multi-year terms. If you do not know whether you will still need the post in six months, you are buying an obligation, not coverage.
- •When you are already in the incident. Urgent coverage and formal procurement are incompatible on the face of it. See same-day and short-notice security for how that path works instead.
Head-to-head
| Factor | Formal RFP | Instant booking |
|---|---|---|
| Time to first shift | Weeks to months, plus 30–60 day transition | Days, sometimes same week |
| Buyer effort up front | High: scope, addenda, scoring committee | Low: define the post, compare rates |
| Best contract size | Large, multi-site, multi-year | Single site, defined post, short or open-ended |
| Price discovery | Sealed cost proposals, comparable line by line | Published rates visible before you commit |
| Negotiating leverage on terms | Strong, pre-award | Limited; terms are standardized |
| Handles urgent need | No | Yes |
| Handles scope you have not defined yet | Yes, the process forces definition | No, you must know the post |
| Public-procurement compliance | Required above bid thresholds | Not a substitute where a solicitation is mandated |
| Switching cost if it goes badly | High: contract term, notice period | Low: book a different agency next shift |
| Vetting burden | On your evaluation committee | Handled before agencies appear |
Read that table as a description of two different risk trades. The RFP spends time to reduce the risk of a bad multi-year commitment. Instant booking spends commitment to reduce the risk of a slow response. If your dominant risk is picking the wrong vendor for three years, buy the process. If your dominant risk is having no one at the post on Friday, do not.
A decision framework
Work through these in order. The first clear answer usually settles it.
1. Are you legally required to compete this? Public agencies, school districts, transit authorities, and organizations spending public or grant funds face competitive-bid thresholds set by statute and local policy. Above the threshold, a formal solicitation is mandatory. Check your procurement code before anything else; nothing downstream overrides it.
2. How many sites, and for how long? One site, one post, horizon under a year: book it. Multiple sites across a region or state, term measured in years: run the RFP. The crossover is not a dollar figure so much as the point where a single account manager can no longer hold the program in their head.
3. Do you already know the scope in writing? If you can state posts, hours, armed status, duties, and supervision without a meeting, the discovery value of an RFP is near zero for you. If you cannot, the RFP is doing genuine work even before a bid arrives.
4. When does coverage have to start? Count backward from the date you need an officer on site. Subtract 30 to 60 days of transition. Subtract the evaluation period. Subtract the question window. If that lands before today, you are not running an RFP, whatever you had planned.
5. How certain is the need? Stable, budgeted, permanent coverage rewards a negotiated long-term agreement. Seasonal, project-based, or contingent coverage does not, and a multi-year award turns uncertainty into a liability.
6. Do you have an evaluation committee? An RFP scored by one busy facilities manager at 6pm is an RFP in name only. If nobody owns the scoring, you get the ceremony of competition without the benefit.
A hybrid is legitimate and common: book coverage now for the post that is bleeding, and run the RFP on the full program in parallel. Nothing about the two paths is mutually exclusive, and having live coverage while you evaluate removes the time pressure that produces bad awards.
What instant booking looks like in practice
Calvis is a marketplace, not a security agency. You describe the post you need covered, and independently licensed local agencies that have already been vetted compete for it, so you compare qualified options on rate and credentials in one place rather than soliciting them one at a time. The officers are employed and licensed by those agencies, and each agency's license is attributed to it through its state regulator.
The practical differences from a solicitation are three:
Rates are visible before you commit. You are not waiting on sealed cost proposals to learn the market price. See what drives guard pricing for how unarmed, armed, patrol, and specialized posts differ.
Credential verification happens before agencies appear, not during your evaluation. In an RFP, confirming licensing, insurance, and guard registrations is committee work. Here it is a condition of being on the marketplace. If you are running the traditional path, our guide on how to vet a security guard company covers the checks your committee needs to make.
There is no term to escape. No annual minimum, no auto-renewal, no notice period. If an agency underperforms, you book a different one for the next shift rather than triggering a termination clause.
What it does not do: replace a mandated public solicitation, or manage a fifty-site national program under one master agreement. Those are real jobs and the traditional path is built for them.
Post the post you need covered → or start with the hiring guide →