Procurement First: 5 Must Have Items for a Facility Maintenance RFP

A complete facility maintenance RFP needs five deliverables: a scope-of-services matrix, a prescribed pricing workbook, defined SLAs and KPIs, published evaluation criteria, and clear submission instructions. Contracts typically run a multi-year base term with renewal options, or a task-order structure for on-call work. Contracts often run several years with renewal options, depending on the portfolio size and owner needs, and require a prescriptive pricing workbook and a detailed scope matrix to ensure comparable bids.

TL;DR:

• A detailed scope-of-services matrix with asset-specific appendices ensures bid comparability and prevents surprise change orders by clarifying task frequencies and responsible parties.
• Precise, auditable SLAs with fixed thresholds for response times and quality checks are essential, supported by standard reports with logs, evidence, and escalation procedures.
• Mandatory, standardized pricing workbooks with fixed formats and clear fields enable accurate comparison of bids and prevent unresponsive submissions caused by blank or N/A entries.
• Contract durations typically range from two to five years with renewal options, and escalation clauses should tie increases to published indices with caps to ensure budget stability.
• Evaluation criteria must be published upfront, favoring technical approach, staffing, and past performance over price alone, with non-responsive bids disqualified based on missing documentation or incomplete fields.

Table of Contents

• Building the scope-of-services matrix
• Specifying SLAs, KPIs, and the reporting to back them up
• Which pricing formats to force and what the workbook must collect
• Contract terms, typical durations, and renewal options
• A defensible evaluation criteria and scoring template
• Submission instructions, timeline, and required attachments
• A copy-ready checklist and sample clauses
• Common pitfalls and red flags to watch for
• Nationwide Maintenance: evidence behind this template
• A procurement lead’s lesson on precise RFPs
• How Nationwide Maintenance supports RFP response and mobilization
• Sources
• FAQ

Building the scope-of-services matrix

The single biggest cause of incomparable bids is vague scope language. A scope matrix fixes this by turning every task into a row with defined columns: included (yes or no), frequency, who performs it (vendor, owner, or excluded), and notes for exceptions. When a bidder cannot guess what counts as “routine,” they cannot underprice it, and the owner cannot get surprised by a change order six months in.

The matrix should cover every service line the building needs, not just the obvious ones:

• HVAC: preventive maintenance schedules and emergency repair coverage.
• Electrical and plumbing: routine inspections versus reactive repair calls.
• Janitorial and grounds: daily, weekly, and seasonal task frequencies.
• Pest control: inspection cadence and treatment response times.
• Snow and ice removal: trigger depths and response windows.
• Building management systems (BMS): monitoring, calibration, and reporting duties.
• Life-safety systems: fire alarm, sprinkler, and emergency lighting testing.
• Work-order management and emergency response: who dispatches, and within what window.

Grounds and exterior tasks are easy to underspecify. A sidewalk maintenance scope that just says “sidewalk cleaning included” invites wildly different bids depending on whether gum removal, graffiti treatment, and pressure washing frequency are spelled out.

Appendices matter as much as the matrix itself. Asset lists with equipment IDs, OEM manuals, and current floor plans let bidders price against real conditions instead of guessing at square footage or unit counts. A building systems RFP from NYC Health + Hospitals prescribes detailed preventive maintenance tasks tied to specific equipment, which is exactly the level of detail that keeps bid spreads tight.

Compare two versions of the same scope line. Vague: “Vendor to maintain HVAC systems as needed.” Precise: “Vendor performs quarterly PM on 14 rooftop units (see Appendix C for make, model, and serial numbers), with emergency repair response within four hours.” The first invites a lowball bid that assumes minimal service. The second forces every bidder to price the same actual workload, which is the only way a side-by-side comparison means anything.

Specifying SLAs, KPIs, and the reporting to back them up

Service levels only work if they are numeric and auditable. Vague language like “prompt response” or “regular maintenance” gives a vendor room to define “prompt” however is convenient after the contract is signed.

Set specific, testable thresholds instead:

• Emergency response: phone acknowledgment within 30 minutes, technician on-site within 4 hours.
• Routine work orders: closed within 5 business days of submission.
• Preventive maintenance completion: 95% or higher completed on schedule each month.
• Janitorial quality: inspection scores tracked against a QA standard, with re-clean turnaround specified separately.

A well-structured RFP requires CMMS access, photo evidence, and time-stamped work-order closure as standard exhibits. Building systems RFPs commonly require monthly reports listing preventive maintenance completed, tests and inspections performed, repair logs, and replacement recommendations, tied to a credit or penalty structure when service windows are missed. Without that paper trail, a missed SLA becomes a dispute about memory rather than a documented fact.

Reports need a fixed structure, not a fresh format every month. A monthly operations report should show asset-level costs, work-order counts by category, PM completion percentage, and any SLA breaches with resolution notes. Quarterly business reviews are the venue for trend discussion: recurring failure points, seasonal cost swings, and any scope adjustments needed for the next quarter.

Credit mechanics should be spelled out in the contract, not left implicit. A workable structure ties a specific dollar credit or percentage reduction to each SLA category, escalating for repeated breaches within a rolling period, and defines an escalation path (site manager, then account manager, then a formal performance review) before termination becomes the only remedy on the table.

Frameworks like ISO 41001 reinforce this: the standard expects documented operational planning and ongoing KPI tracking rather than reports assembled after the fact, and CMMS-based evidence is the easiest way to satisfy that expectation without extra administrative work.

Which pricing formats to force and what the workbook must collect

Pricing format determines whether bids can be compared at all. Three structures cover most facility maintenance contracts, and the RFP should specify which one applies to which service line rather than leaving it to the bidder.

Lump-sum yearly fees, broken out by service line, work well for predictable preventive maintenance. A sample HVAC RFP specifies a lump-sum yearly fee per category held firm for the contract term, which is a clean approach when the equipment count and PM schedule are fixed.

Unit-price schedules fit reactive or variable-volume work: a per-hour electrician rate, a per-square-foot pressure washing rate, a per-unit pest treatment fee.

Hybrid models combine a fixed monthly fee for scheduled PM with unit pricing for anything outside that scope.

The pricing workbook itself needs mandatory fields, not optional ones:

• Fixed monthly fee by service line, broken out so no single number hides multiple services.
• Hourly rates by trade (HVAC technician, electrician, plumber, general handyman).
• Materials markup percentage.
• Unit prices for common recurring tasks, listed individually rather than bundled.
• Not-to-exceed (NTE) thresholds for emergency or out-of-scope work.
• Escalation terms, including any CPI cap for renewal years.

Large public-sector solicitations demonstrate why this matters. A Judicial Council of California RFP posts a regional Excel pricing workbook and treats it as a required attachment, not a suggestion, precisely because a prescribed format is the only way to compare bidders on equal footing.

Enforcement rules matter as much as the format. Blank cells, “N/A” on a required unit price, or a suspiciously low zero-dollar entry should be treated as a responsiveness failure under a policy set before bids open, not decided case by case during evaluation. For equipment added or removed mid-contract, and for emergency repairs above the NTE threshold, the RFP should specify an approval flow: written estimate, owner sign-off, then work authorization, so nothing gets billed without a paper trail.

Contract terms, typical durations, and renewal options

Most facility maintenance contracts follow a familiar shape: a firm base term, followed by optional renewal years the owner can decline if performance slips. Public RFP examples commonly structure this as a 2 to 5 year base term with 1 to 5 renewal years, sometimes splitting large portfolios by region so no single vendor holds every location.

Two contract models show up repeatedly, and the RFP should state which one applies:

• Firm fixed-price preventive maintenance contracts, where the vendor is paid a set amount regardless of exact labor hours, works best for predictable, scheduled work.
• On-call or task-order models, where individual work orders are issued and priced against the unit-rate schedule, fit reactive or unpredictable repair volume.

A portfolio with heavy recurring PM leans toward the first model. A portfolio with unpredictable repair needs, like an aging building with frequent breakdowns, needs the flexibility of the second.

Escalation language deserves explicit treatment rather than a vague reference to “annual increases.” A sample HVAC contract holds pricing firm for the full base term, which removes one variable from year-over-year budgeting. When escalation is allowed for optional years, tie it to a named index (a published Consumer Price Index series, for example) with a stated cap, so a vendor cannot propose an open-ended increase.

Change orders need their own approval threshold written into the contract: a dollar amount below which the site manager can authorize work directly, and a higher amount requiring written owner approval before the vendor proceeds. Sample wording: “Pricing for Service Categories 1 through 6 shall remain firm through the base term. Optional Year pricing may increase by no more than the annual CPI-U change, subject to a cap of [a stated percentage] per year, upon 60 days’ written notice.”

A defensible evaluation criteria and scoring template

Evaluation criteria need to be published in the RFP itself, not decided after proposals arrive. A workable weighting for a comprehensive facility maintenance award looks like this:

This mirrors how strong public solicitations operate. Section M evaluation criteria from a Washington DC RFP shows technical approach, staffing, and past performance carrying the majority of available points, with resumes and minimum experience thresholds required for key staff rather than assumed.

Technical scoring should break into named subfactors so evaluators are not making a single subjective call:

• Past performance: verifiable references from comparable facility types.
• Staffing plan: named project manager, technician count, and licensing.
• PM and QC plans: how preventive maintenance is scheduled and quality checked.
• Emergency response capability: proof of 24/7 coverage, not just a claim of it.
• Regulatory compliance: insurance, safety certifications, and applicable licenses.

Minimum responsiveness checks should be non-negotiable and documented before scoring begins: missing insurance certificates, an unsigned pricing workbook, or a proposal submitted after the deadline disqualifies a bidder regardless of how strong the technical narrative reads. Our own scoring criteria breakdown walks through how these provider checks work in practice.

When two finalists score closely, a live demonstration and direct reference checks make better tie-breakers than adjusting weights after the fact. Document every score with a one-line justification so the award decision holds up if a losing bidder asks for a debrief.

Submission instructions, timeline, and required attachments

A realistic schedule from draft RFP to contract start runs roughly 10 to 14 weeks: draft and internal review, a Q&A period, the submission window, evaluation, finalist interviews, award, and mobilization. Compressing this timeline is the most common reason mobilization goes poorly.

1. Publish the draft RFP with a fixed release date and a single point of contact for questions.
2. Set a written Q&A deadline, typically one to two weeks after release, with answers posted to all bidders simultaneously as a formal addendum.
3. Hold the submission window open for two to three weeks from the final addendum, not from the original release date.
4. Specify exact file formatting: one combined PDF for the technical proposal, a separate Excel file for the pricing workbook, and a stated file-naming convention.
5. Run evaluation and shortlist finalists within two to three weeks of the submission deadline.
6. Conduct finalist interviews or site walks, then issue the award and begin mobilization planning.

Mandatory attachments should be listed explicitly so no bidder can claim ambiguity: the signed pricing workbook, a staffing plan with resumes and license copies, a preventive maintenance and QC plan, current insurance certificates, past performance documentation, and appendices covering asset lists and floor plans. A university rebid RFP treats missing or ambiguous pricing entries, including blanks or “N/A” where a number is required, as grounds for deeming a bid non-responsive. Any addendum issued during the Q&A period officially amends the RFP and should require bidders to acknowledge receipt in their submission.

A copy-ready checklist and sample clauses

A short checklist keeps the drafting team from missing a required piece. Map each RFP section to who supplies the underlying content before the document goes out:

1. Scope matrix: facility manager supplies asset lists and frequencies; procurement formats the matrix.
2. Pricing workbook: finance sets the required fields; procurement locks the template so bidders cannot alter formulas.
3. SLA exhibit: operations defines thresholds; legal reviews credit language.
4. Evaluation criteria: procurement sets weights before release, not after proposals arrive.
5. Submission instructions: procurement confirms the portal or email address and file-naming rules.

A few clauses are worth pasting directly into a draft rather than rewriting from scratch:

• Scope matrix instruction: “Bidder shall complete every row of Appendix B, indicating frequency and responsible party. Rows left blank will be interpreted as excluded from the bid price and may render the response non-responsive.”
• SLA credit clause: “Failure to meet the emergency response time in Section 4.2 shall result in a credit equal to [a stated amount] per occurrence, applied to the following month’s invoice.”
• Pricing workbook instruction: “All cells shaded in yellow in the attached Excel workbook are mandatory. Entries of ‘N/A’ or $0.00 in a mandatory cell will be treated as non-responsive unless the service is explicitly marked excluded in Appendix B.”
• Evaluation weighting disclosure: “Proposals will be scored according to the weights published in Section 6: Technical Approach (25%), Price (25%), Experience and References (20%), Reporting and Technology (15%), Key Personnel (10%), Transition Plan (5%).”
• Submission format: “Submit one PDF containing the full technical proposal and one Excel file containing the completed pricing workbook. Name files using the convention [CompanyName]_Technical.pdf and [CompanyName]_Pricing.xlsx.”

The pricing workbook itself works best as a multi-tab Excel file: a summary tab rolling up the total annual price, a tab per service line for the unit-rate detail, and a final tab for escalation terms and NTE thresholds. Mobilization language belongs in the award letter or contract exhibit, naming a transition period (commonly 30 to 60 days) during which the incoming vendor completes staffing, CMMS setup, and a joint walkthrough with the outgoing provider before taking over billing.

Common pitfalls and red flags to watch for

Most bad outcomes trace back to a handful of repeatable mistakes:

• Vague scope language produces incomparable bids and change orders later. The fix is a detailed scope matrix with asset-level appendices.
• A single lump-sum number with no breakout hides where the money goes and makes renegotiation guesswork. Force the pricing workbook.
• Missing staffing evidence means the owner has no idea who is actually showing up. Require resumes and license copies for named key personnel.
• Blank unit prices, unrealistically low total bids, or missing required attachments are red flags that should trigger a clarification addendum or disqualification under the policy set before submissions opened, not a judgment call made mid-evaluation.

Pro Tip: Rebid the contract every 3 to 5 years even with a strong incumbent. Pricing assumptions, equipment inventories, and staffing needs shift enough over that window that a fresh competitive check protects the budget.

Nationwide Maintenance: evidence behind this template

An integrated facility services provider has operated for over 30 years, working across retail, government, and healthcare facilities. Running cleaning, pest control, construction, and landscaping under one contract structure means pricing breakouts, mobilization sequencing, and scope-matrix detail are well established in practice. That combined-service model influenced the pricing workbook fields and mobilization checklist recommended above.

A procurement lead’s lesson on precise RFPs

A facility manager once told us their most successful vendor transition traced back to one decision: refusing to accept a lump-sum bid without a line-item breakout. Mobilization took half the usual time, and change orders in year one were rare, because every task had already been priced individually. The lesson holds regardless of portfolio size: enforce the pricing workbook and the scope matrix before anything else.

— Nationwide Maintenance.

How Nationwide Maintenance supports RFP response and mobilization

Writing or responding to a facility maintenance RFP is easier when one vendor can price every service line instead of forcing procurement to stitch together multiple contracts. Some companies combine commercial cleaning, pest control, construction, landscaping, and emergency response under a single contract, which simplifies the scope matrix into one vendor relationship instead of several. We support transition and emergency mobilization with CMMS onboarding and KPI reporting built into the handoff, so the reporting cadence an RFP requires is in place from day one rather than assembled after the fact.

If your team is drafting a facility maintenance RFP or evaluating vendor responses, see our full range of services to get a sense of what a single-contract scope matrix could look like for your portfolio.

Sources

• SECTION M evaluation criteria (Washington DC RFP addenda)
• Request for Proposals for Building Maintenance Systems (NYC Health + Hospitals RFP)
• Judicial Council of California RFP for Facility Operations and Maintenance

FAQ

What should be included in a facility maintenance RFP?

A complete facility maintenance RFP needs a scope-of-services matrix, a prescribed pricing workbook, defined SLAs and KPIs, published evaluation criteria, and clear submission instructions. Skipping any of these tends to produce bids that cannot be fairly compared side by side.

How long should a facility maintenance contract term be?

Most contracts use a multi-year base term, commonly 2 to 5 years, with optional renewal years the owner can decline. Large portfolios sometimes split the award by region rather than awarding the whole contract to one vendor.

What pricing format should an RFP require from bidders?

The format should match the work type: lump-sum yearly fees for predictable preventive maintenance, unit pricing for reactive or variable work, or a hybrid of both. A prescribed pricing workbook with mandatory fields is what actually makes bids comparable, regardless of which format is chosen.

How should evaluation criteria be weighted in a facility maintenance RFP?

Published RFPs, like Washington DC’s Section M criteria, tend to weight technical approach and staffing heavily rather than deciding on price alone.

What makes a vendor’s RFP response non-responsive?

Blank or “N/A” entries in required pricing fields, missing insurance certificates, or missing staffing documentation are common grounds for a non-responsive determination. Campus and public-sector RFPs, including one from Wayne State University, treat these gaps as a responsiveness failure rather than something to clarify after the deadline.

Recommended

• Procurement: 6 Facilities RFP Scoring Criteria With Provider Checks
• Make Safe First: Emergency Maintenance Response for Facility Managers
• Save 25–35% Energy: A Maintenance First Plan for Facility Managers