Federal RFP

Writing the Technical Volume of a Cleaning Company RFP

Answer

Federal cleaning RFPs under FAR Part 15 require five technical sections: Technical Approach, Staffing Plan, Quality Control Plan, Phase-In Plan, and Past Performance. Weak technical volumes are the most common reason price-competitive cleaning companies lose.

  • Quality Control Plans must name who inspects (not the worker doing the job), inspection frequency, corrective action, and COR communication.
  • Past performance section needs 3 comparable contracts from the past 5 years with POC info; most agencies accept commercial work.
  • GSA Schedule 23V provides the most accessible entry point for first-time federal contractors, with a 3-6 month application.

$22.0M SBA small business size standard for NAICS 561720

Opora Editorial team Published Updated 6 min read 1345 words Sourced & fact-checked
HomeOperator BlueprintFederal & State Cleaning RFPsWriting the Technical Volume of a Cleaning Company RFP

Writing the Technical Volume of a Cleaning Company RFP

By Opora Editorial Team9 min readUpdated continuously · In Federal & State Cleaning RFPs

Free tool

Scope-of-Work Generator

Federal-grade SOW in minutes, RFP-ready format.

Open tool →

Under FAR Part 15, negotiated federal procurement, the technical volume is scored independently from price on most cleaning RFPs, often on a pass/fail or adjectival scale (outstanding, good, acceptable, marginal, unacceptable) before the contracting officer ever opens your price. A marginal technical score can knock you out of the competitive range regardless of how sharp your rate is. The document exists to answer one question for the evaluator: can this company actually run this building at this scope without the government having to manage it for them.

5 Core sections evaluators expect in a federal janitorial technical volume: Technical Approach, Staffing Plan, Quality Control Plan, Transition/Phase-In Plan, and Past Performance. Source: FAR Part 15, Contracting by Negotiation.

Technical Approach: show the method, not the mission statement

This section fails most often because contractors write about their company philosophy instead of the building. A strong Technical Approach walks the evaluator through the actual scope: cleaning frequencies by area type (restrooms daily, lobbies daily, offices per cycle, high-dusting quarterly), the equipment assigned to each task, the chemicals and their dilution ratios or EPA registration numbers, and how the schedule adapts around the facility's occupied hours. If the solicitation names a specific standard, such as ISSA's Cleaning Industry Management Standard (CIMS) or a green-cleaning requirement referencing EPA Safer Choice products, cite it explicitly and show how your SOPs meet it line by line rather than asserting compliance in general terms.

Staffing Plan: ratios evaluators can verify

Government evaluators read staffing plans looking for internal math that holds up: total square footage divided by your stated production rate should roughly match the labor hours you propose in the staffing table, which should roughly match the FTE count in your org chart. A plan that shows 40,000 square feet, a production rate of 4,000 square feet per hour, and 10 labor hours per night is claiming coverage that does not add up. Evaluators who do that arithmetic (and many do) will flag it. Include a named or role-based supervision ratio (one working supervisor per some number of cleaners), a backup staffing methodology for call-offs, and how you handle mid-contract staffing changes without the government having to intervene.

Typical Federal Cleaning Technical Volume Structure
Section What Evaluators Check Common Failure Point
Technical Approach SOPs mapped to scope, chemical/equipment specificity Generic marketing language instead of building-specific detail
Staffing Plan Hours vs. sq ft vs. production rate consistency Math that does not reconcile across sections
Quality Control Plan Independent inspector, documented corrective action loop Same person cleaning and inspecting
Phase-In Plan 30/60/90-day milestones, incumbent transition risk No plan for retaining incumbent staff or key knowledge
Past Performance 3+ similar-scope contracts, verifiable POC, CPARS history References that can't be reached or don't match scope size

Quality Control Plan: the section that separates operators from applicants

A QCP needs five specific elements to read as credible to a federal evaluator: the inspection method and frequency (daily walk-through checklist, weekly formal inspection, whatever cadence fits the facility), who performs inspections (structurally separate from who performs the cleaning), how results get documented and stored, the corrective action timeline when a deficiency is found, and how you report to the government's Contracting Officer's Representative. Vague language like "we maintain high standards" reads as filler. A QCP that names the inspection form, the number of inspection points per area type, and the number of hours allowed to correct a documented deficiency reads as a company that has run government contracts before.

Phase-in and past performance: risk reduction on paper

The Phase-In Plan exists to convince the evaluator that switching from the incumbent contractor to you will not create a service gap the building occupants notice. Lay out concrete milestones: personnel hired and badged by a certain day before start, supply inventory staged, incumbent staff retention outreach if applicable, and a defined go-live walkthrough with the COR. For Past Performance, three comparable contracts is the practical floor most solicitations expect, comparable meaning similar square footage, similar facility type, and recent (typically within the last five years), each with a point of contact who will actually take the evaluator's call and a documented dollar value and scope. If you are new to government work, commercial contracts of comparable scope are generally acceptable past performance; a strong reference letter carries real weight even without a CPARS record behind it.

Writing to the evaluation criteria, not to your company

Every FAR Part 15 solicitation includes a Section M or equivalent evaluation criteria section that tells you exactly what the government is scoring and, often, the relative weight of each factor. A technical volume that mirrors the structure and language of Section M, addressing each sub-factor in the order the government listed it, scores measurably better than one organized around how the contractor prefers to present its own capabilities. If Section M lists Technical Approach, Management Approach, and Past Performance in that order with Technical Approach weighted most heavily, your response should lead with Technical Approach and give it proportionally more page space, not bury it behind a company history section the solicitation never asked for.

Evaluators score against a checklist derived from Section M, and a proposal organized so that checklist items are easy to locate cuts evaluation time and reduces the odds a compliant answer gets missed because it was buried in the wrong section. Cross-reference each paragraph back to the specific solicitation requirement it answers using the RFP's own paragraph numbering where possible.

Common mistakes that cost points on evaluation

Reviewers who score federal janitorial proposals repeatedly flag the same handful of issues: staffing numbers in the technical narrative that do not match the staffing table in the pricing volume, past performance references listed without a working phone number or current point of contact, quality control language copied from a different industry's template that references irrelevant standards, and phase-in timelines that assume more calendar time than the solicitation's transition period actually allows. Each of these is a documentation discipline problem, not a capability problem. A company fully capable of performing the contract can still score poorly because the proposal itself does not hold together internally.

Frequently asked questions

How long should a federal cleaning technical volume be? Page limits are set by the specific solicitation, but a typical structure runs roughly 10 to 15 pages for Technical Approach, 5 to 8 for Staffing, 5 to 8 for the QCP, and shorter sections for Phase-In and Past Performance. Follow the RFP's stated limits exactly, since exceeding them is often grounds for rejection.

Can I use the same technical volume for every RFP? No. Reusing a generic technical volume across solicitations is the fastest way to score "acceptable" instead of "outstanding." Evaluators can tell when a proposal was not tailored to the specific building, scope, and evaluation criteria in front of them.

What if I don't have three past performance references yet? Use the most comparable commercial or subcontract experience you have, document it fully with square footage and contract value, and be transparent about scale differences rather than omitting the section.

Does the technical volume ever get scored against price? On many negotiated procurements, technical merit and price are traded off in a best-value determination, but the technical evaluation itself is typically conducted without knowledge of your price to avoid bias.

How we built this guide

Opora editorial sources from BLS OEWS wage tables, ISSA production rate standards, FAR Part 15 negotiated procurement guidance, and primary agency proposal instructions. We don't recycle blog posts — we audit primary documents.

Methodology · Editorial standards · Corrections policy · About Opora

Rfp