How to Write a Janitorial RFP That Gets Comparable Bids Instead of Guesses

Most janitorial RFPs fail before a single vendor responds. They ask for "nightly cleaning" without defining square footage breakdowns, list "restrooms as needed" without a frequency, and leave quality standards to "industry best practice" — a phrase every vendor interprets differently. The result is five proposals that can't be lined up next to each other, because each vendor quietly filled in the blanks with their own assumptions. A better RFP removes the guesswork before it starts.

Why Most Janitorial RFPs Get Useless Responses

When an RFP is vague, vendors respond in one of two ways: they either pad the bid to cover every assumption they can't rule out, driving the price up, or they bid the bare minimum interpretation to stay competitive, planning to renegotiate scope later. Neither response gives you a real comparison. The fix isn't a longer document for its own sake — it's specificity in the sections that actually drive labor hours and cost.

This matters more than it seems on first read, because the cost of a bad RFP doesn't show up during the bidding process — it shows up eighteen months into a three-year contract, when scope disagreements start turning into change orders and the facility realizes the winning bid was never actually pricing the same job as the other bidders. A well-built RFP is cheap insurance against that outcome, and it costs nothing but the time to write it properly the first time.

The Scope Section: Be Specific or Get Burned

The scope of work is the single most important section in the entire RFP, and it's the one most commonly left generic. Instead of "clean all common areas," list every space type by name — lobbies, corridors, elevators, stairwells, break rooms, conference rooms, restrooms — and specify what "clean" means for each: trash removal, surface wiping, floor care by floor type, glass and mirror cleaning, restocking consumables. A vendor pricing a defined scope prices accurately; a vendor pricing "clean the building" prices defensively.

Square-footage and surface breakdowns

Provide total square footage broken down by space type and floor surface — carpet, VCT, ceramic tile, polished concrete — because labor time and equipment needs vary significantly by surface. If you have a recent floor plan or space utilization report, attach it. Vendors who have to estimate square footage from a site visit alone will build in a pricing buffer for the uncertainty, and that buffer becomes a permanent part of your contract cost.

It also helps to note occupancy patterns alongside square footage — a floor that runs three shifts a day generates more trash and higher restroom traffic than one that's empty by 6pm, even at identical square footage. If your facility has meaningfully different occupancy by floor or wing, say so in the RFP rather than assuming a vendor will ask, because most won't ask before submitting a bid; they'll just price against a generic assumption and adjust later.

Frequencies, Square Footage, and Special Requirements

State exact frequency for every task category: nightly, 3x/week, weekly, monthly, quarterly. "As needed" is not a frequency — it's an invitation for a vendor to do it less than you expect. Call out any special requirements up front: security clearance or background-check standards, chemical restrictions (LEED or Green Seal requirements, for example), access-hour windows, and any areas requiring escorted access. These requirements change staffing and cost, and burying them in an appendix guarantees a change order later.

Break out periodic tasks (floor stripping and waxing, carpet extraction, high-dusting, window washing) into their own line items with a stated frequency rather than lumping them into a vague "deep cleaning as scheduled" clause. These tasks carry real material and labor costs that vary widely by vendor, and burying them inside the base scope makes it impossible to tell whether a lower bid actually included them or just left them out.

Defining KPIs and How You'll Measure Them

"Industry best practice" is not a measurable standard. Define the inspection method you'll use — a numeric scoring rubric, a percentage-pass threshold, a specific standard like ISSA's Cleaning Industry Management Standard (CIMS) — and state how often inspections will occur and who conducts them. A vendor who knows exactly how they'll be graded will staff to meet that standard from day one instead of discovering it reactively.

Inspection and quality standards

If you don't already have an inspection framework, borrow structure from an established one — CIMS or a simple weighted checklist by area type — rather than inventing an informal one mid-contract. Include the inspection form itself as an RFP attachment so vendors can see exactly what they're being measured against before they price the job, not after.

Define what happens when an inspection fails, too — not just how scoring works. A contract with a scoring rubric but no consequence for repeated failures is measuring quality without enforcing it. Spell out a remediation timeline (re-clean within 24 hours, for example) and, for a term contract, a threshold of consecutive failures that triggers a formal performance review or termination clause.

Evaluation Criteria That Aren't Just Price

State your evaluation weighting up front — for example, 50% price, 20% scope compliance and staffing plan, 15% references and past performance, 15% certifications and compliance documentation. Publishing the weighting does two things: it discourages vendors from lowballing price alone to win, and it gives your procurement team defensible grounds for choosing a bid that isn't the cheapest one, which matters if the decision is ever reviewed or audited.

Require a staffing plan as a scored line item, not just an attachment — how many cleaners per shift, what supervision looks like, and how the vendor plans to cover call-outs and vacations without dropping service. A vendor that can't produce a specific staffing plan at the proposal stage is unlikely to produce one once the contract is running, and a scoring rubric that rewards specificity here filters those vendors out before award instead of after.

Transition and onboarding expectations

Ask every bidder to include a transition plan: how they'll staff the account in the first 30 days, how supplies and equipment get onboarded, and how they'll handle a change in incumbent vendor if one exists. A vendor who can't describe a transition plan in the proposal usually doesn't have a repeatable one, which is a preview of how rough your actual onboarding will be.

Site Visits and Pre-Bid Questions

Offer a mandatory or optional pre-bid walkthrough and a formal window for written questions, then publish the answers to every bidder rather than answering questions one-off by phone. This does two things: it surfaces scope ambiguities before bids are submitted instead of after, and it prevents one bidder from getting information another didn't. A site visit also lets vendors see real conditions — a facility that looks straightforward on a floor plan may have restroom counts, floor conditions, or access constraints that only become obvious in person, and a vendor who skips the walkthrough is pricing on assumptions.

Attachments That Save You From Ambiguity Later

Attach everything that removes a vendor's need to guess: current floor plans, a restroom count by floor, current cleaning frequency (if this is a re-bid), the inspection form you'll use, and a sample invoice format if you require a specific one for your accounting system. Every attachment you include is one less assumption a vendor has to price defensively, and one less area where an awarded vendor can later claim the scope wasn't clear.

An RFP built this way takes longer to write than a one-page request, but it converts a guessing exercise into a real comparison. When every bidder is pricing the same defined scope, the same frequencies, and the same KPIs, the proposals that come back are finally telling you something you can act on — and the vendor you select is bound to specifics you wrote down, not to a verbal understanding from a walkthrough six months earlier.