Facilities Management Survey Template (Free)
Use this facilities management survey template to spot your lowest-performing sites, spaces, and service lines (HVAC, cleaning, maintenance, security) before small issues become constant complaints. Default setup: a 5-7 minute occupant pulse with CSAT (satisfaction) plus a short post-work-order add-on that uses CES (effort) to find friction in the ticket process. You will be able to segment results by Site/Building and Service Line, then turn themes into an owner-based action plan.
Trusted by 5000+ Brands
Choose your headline metric: CSAT vs CES vs NPS (facilities use cases)
What you will get in this template:
- A 5-7 minute occupant pulse survey (overall service + building conditions)
- An optional post-work-order add-on (transactional) to find ticket-process friction
- Recommended segmentation fields (Site/Building, optional Floor/Zone, Service Line)
- A simple reporting format: 1 headline metric + 2-3 drivers + top themes + an owner-based action plan
| Metric | What it tells you (plain language) | Use it when (facilities examples) | Pros | Cons / watch-outs | Simple way to report |
|---|---|---|---|---|---|
| CSAT (satisfaction) | How satisfied people are with facilities service and building conditions. |
|
|
| Headline: % satisfied (4-5 on a 5-point scale) + 2-3 driver averages + top 3 themes by site. |
| CES (effort) | How easy or hard it was to get help (submit a ticket, get updates, close out work). |
|
|
| Headline: average CES (or % easy) + 2 drivers (updates, timeliness) + top blockers from open-text. |
| NPS (recommend) | How likely people are to recommend your workplace/facilities experience. |
|
|
| Headline: NPS + 2-3 drivers (cleanliness, comfort, responsiveness) + top themes by site. |
Default: Use CSAT for your occupant pulse (service + conditions) and CES for the post-work-order add-on (ticket friction). Do this: pick one headline metric for the pulse and keep it stable so you can trend it quarter over quarter, consistent with customer satisfaction monitoring guidance such as ISO 10004 customer satisfaction monitoring guidelines. If you use CES, keep it clearly tied to the most recent request so it reflects effort in the interaction (not overall sentiment), aligned with widely used customer-effort measurement practices (for example, see the background on effort-based measurement in Harvard Business Review's overview of Customer Effort).
Report format you can copy: Headline score (CSAT or CES) + 2-3 driver scores (timeliness, quality, communication) + top 3 themes by site/service line + the top 3 fixes you will deliver next.
Checkpoint: Which metric will you report every time, and which 2-3 drivers will you hold teams accountable for?
Who to survey (and how to sample) for facilities feedback
Use this to get facility feedback that points to fixes by site, floor, and service line (not a generic "facilities is fine" score). Default: survey occupants for the pulse, then survey ticket submitters after work orders. First: add required fields for Site/Building (and optional Floor/Zone) so you can segment results without guessing.
Core audiences to include
- Occupants (employees): best for overall conditions and day-to-day services (restrooms, temperature, cleaning, noise).
- Tenants (multi-tenant buildings): include if you manage common areas and building systems that affect them.
- Frequent visitors: include only if visitor experience is a goal (lobby, signage, meeting rooms).
- Ticket submitters and approvers: best for the post-work-order add-on (speed, communication, ease).
Keep vs separate: Keep vendor performance questions in your main survey only if occupants can observe it (cleaning consistency, guard professionalism). Separate detailed contractor scorecards into a vendor module so you do not mix audiences and dilute action.
Sampling tip: If you run multiple sites, plan your sample so every major site/building is represented. Do this: segment by Site/Building and work pattern (on-site, hybrid, mostly remote) and size your outreach using sampling guidance for multi-site surveys.
Do this: keep the pulse to 5-7 minutes, send 1-2 reminders, and say exactly how you will use results ("We will publish top fixes by site in 2 weeks"). Practical tactics like reminders and shorter questionnaires tend to increase response rates in controlled evaluations such as the Cochrane review on methods to increase questionnaire response.
Do this: use a neutral subject line ("Facilities pulse: 5 minutes") and add a confidentiality statement ("Results reported in groups; no individual responses shared"). If you want more guardrails, follow how to reduce response bias and avoid making the survey feel like a complaint box that only unhappy people will complete.
Checkpoint: Do you know which sites/buildings and which work patterns you will compare in your results?
Facilities management survey questions (copy/paste core + optional modules)
"Overall, how satisfied are you with facilities services at your primary work location?"
Why it matters: Use this to spot your worst-performing sites and service lines with one outcome score. Default: run this CSAT (satisfaction) question in every pulse.
When to use: Include every time. Do this: capture Site/Building before this question so you can trend CSAT by location.
"How easy was it to submit your most recent facilities request or work order?"
Why it matters: High effort means more repeat tickets, more hallway work, and more frustration.
When to use: Use in a post-work-order survey (ticket close-out) or in the pulse for people who submitted a request in the last 30 days.
"I received clear status updates while my request was in progress."
Why it matters: People tolerate slower fixes when communication is predictable (assigned, scheduled, completed).
When to use: Best in post-work-order. Option: include in the pulse with a "Not applicable" choice for non-ticket users.
"Facilities requests are resolved within a reasonable timeframe."
Why it matters: Timeliness is usually the top driver of satisfaction for maintenance work.
When to use: Include in the pulse and the post-work-order add-on so you can compare perception vs actual SLA performance.
"The quality of completed work meets expectations (fixed the issue the first time)."
Why it matters: Rework is a cost problem and an experience problem. This item catches repeat failures fast.
When to use: Best after a ticket closes. Option: include in the pulse as a general perception question.
"Common areas (lobby, hallways, break areas) are clean and well maintained."
Why it matters: Cleaning and upkeep shape daily trust in the building, even for people who never submit a ticket.
When to use: Include in every pulse. Do this: add an optional location picker for hotspots (Building A, Floor 3, restrooms).
"Restrooms are clean and stocked when I use them."
Why it matters: Restrooms are a high-visibility service. A small fix (check frequency, supply tracking) can move scores quickly.
When to use: Include in offices, campuses, and mixed-use buildings. Option: replace with "Production areas" for industrial sites.
"Temperature and ventilation in my primary workspace are comfortable."
Why it matters: HVAC comfort issues create repeat complaints and productivity drag. Keep the wording single-focus (do not mix temperature, airflow, and odor in one item).
When to use: Include in every pulse. Option: add a follow-up picklist (too hot/too cold/stuffy/drafty) only if the score is low.
"I feel safe in and around the workplace (access, lighting, security presence)."
Why it matters: Safety perception drives whether people use the space at all (parking, entrances, late hours).
When to use: Include in every pulse. Do this: keep results confidential and report by grouped areas (not an individual office).
"What is the #1 facilities improvement that would most improve your experience at your primary location?"
Why it matters: One focused open-text question turns scores into a fix list you can assign (increase restroom checks, update HVAC schedule, improve ticket updates).
When to use: Include every pulse. Do this: ask for a location when relevant (Building A, Floor 3) but do not force over-detailed info.
Response scale and wording rules (keep trends clean)
Do this: standardize on one response scale across the pulse so your trend lines mean something. Use Likert scale basics (and how to keep anchors consistent) to keep the direction and labels consistent (for example, 1 = Strongly disagree, 5 = Strongly agree) and to avoid mixing "satisfied" and "agree" scales in the same section.
- Default: 5-point scales for speed and comprehension. Option: 7-point if you need more spread for benchmarking.
- Keep: one idea per question (avoid double-barreled items like "timely and high quality").
- Keep: a clear time frame when needed ("in the last 30 days" or "your most recent work order").
Question-writing tip: follow a simple, single-idea structure and consistent ordering (general to specific), aligned with practical guidance such as Pew Research Center questionnaire design guidance.
Optional modules (toggle, do not bloat the pulse)
- Single office: meeting rooms (availability/equipment), pantry/break areas, noise/distractions.
- Campus: shuttle/parking, wayfinding/signage, outdoor areas, after-hours coverage.
- Industrial: production area conditions, tool crib/support, safety reporting ease, response during shifts.
- Service line deep dives (rotate quarterly): HVAC (comfort consistency), cleaning (day vs night), security (access control), maintenance (first-time fix).
If you are running post-occupancy feedback after moves or renovations, do this: add a short environment module (comfort, lighting, acoustics) that matches recognized post-occupancy survey practices such as the WELL Building Standard guidance on post-occupancy surveys.
Checkpoint: Did you keep the core 10 and cut optional modules unless you have a specific decision to make?
Analyze and act: segment, prioritize fixes, and close the loop
- Check response mix and clean the file
Use this to avoid acting on a skewed slice of one building or one shift. Default: trend CSAT for the pulse and CES for tickets. First: confirm you captured Site/Building and Service Line for most completes (and add "Not applicable" where needed). When you set targets, baseline first by site/service line; avoid treating example thresholds as universal.
- Compare completes by site/building and work pattern (on-site vs hybrid).
- Remove duplicates if your link can be forwarded, and filter obvious spam entries.
- If you want confidence guidance, use sample size and margin of error basics to decide when a site is "big enough to act" vs when you should roll up locations.
- Segment results by location and service line
Do this: report results in a simple grid (Site/Building x Service Line) so you can see where problems cluster. Keep one view for overall conditions (cleanliness, comfort, safety) and one view for request handling (timeliness, updates, first-time fix).
- Start with your worst 2-3 buildings (lowest CSAT) and your most-used service lines (highest ticket volume).
- Break out repeat themes ("restrooms" vs "break areas" vs "temperature") rather than one catch-all "cleaning" bucket.
- Prioritize fixes using impact vs frequency
Do this: pick items that are both low-scoring and frequently mentioned. Fix those first because they are more likely to move the headline score and reduce repeat complaints. Treat this as a practical prioritization heuristic; also sanity-check cost, safety risk, and feasibility before you commit.
- High frequency + low score: act now (increase restroom checks, adjust HVAC schedules, improve ticket status emails).
- Low frequency + low score: investigate (often a specific zone like Building B, Floor 2 west wing).
- High frequency + high score: protect (do not break what is working).
- Close the loop with a "You said, we did" update
Do this: publish a short update within 2-3 weeks so people believe the next survey matters. Share 3 things you are fixing, 1 thing you are studying, and 1 thing you are not changing yet (with a reason). Closing the loop is a core part of customer satisfaction monitoring programs (see ISO 10004), and it is also a common best practice in survey action planning (for example, resources on planning actions after survey results are available via AHRQ SOPS).
Copy/paste update message: "Thanks for the facilities feedback. Top issues at (Building A) were (restroom supplies), (temperature swings), and (slow status updates on tickets). By (date), we will (increase restroom checks to every 2 hours), (add an HVAC service window 7-9am), and (send automated ticket updates at assigned/scheduled/completed). We will re-check progress in the next pulse."
Copyable action-plan tracker (use one row per fix)
| Issue (what/where) | Owner | Due date | Fix (what will change) | Success metric | Update message |
|---|---|---|---|---|---|
| Restrooms not stocked (Building A, Floor 3) | Cleaning lead | 2026-04-01 | Increase checks to every 2 hours; add supply log | Internal starter target: improve the restroom item score by ~10-15% vs your baseline (adjust after baseline); fewer open-text mentions | "We increased restroom checks on Floor 3 and added a restock log." |
| Ticket updates unclear (all sites) | FM ops manager | 2026-04-15 | Automated updates at assigned/scheduled/completed | Internal starter target: improve CES (updates/status) by ~5-10% vs your baseline (adjust after baseline); fewer "no status" comments | "You will now receive updates when work is scheduled and completed." |
Checkpoint: Do you have an owner and due date for your top 3 fixes by site and service line?
Frequently Asked Questions
Should I run one facilities survey or separate surveys for each service line (HVAC, cleaning, security)?
Default: run one short pulse (quarterly or twice a year) with a small set of universal questions, then segment results by service line. Add service-line modules only when you need detail, or rotate one deep-dive module each pulse to keep the survey short. For interaction-level feedback, use a separate post-work-order survey triggered at ticket close-out.
How do I choose between CSAT, CES, and NPS for facilities management?
Use CSAT (satisfaction) for your occupant pulse because it covers both services and building conditions. Use CES (effort) after work orders to catch friction in the request and communication flow. Use NPS (recommend) only if you truly need an advocacy-style metric; otherwise keep one headline score (usually CSAT) and treat the others as diagnostics.
How often should I send an occupant facilities satisfaction survey?
Default: send a 5-7 minute pulse quarterly or twice a year so you can trend results and hold owners to fixes. Option: run continuous post-work-order surveys (or sample them) to monitor day-to-day execution. After a move, renovation, or a spike in complaints, send a short follow-up focused on the changed area.
What response options (5-point vs 7-point) should I use for facilities questions?
Default: use a consistent 5-point scale across the pulse because it is faster and easier for people to answer. Option: use 7-point scales if you need more spread for benchmarking or if scores are clustering at the top. Consistency matters more than the exact number of points, especially for trending by site and service line.
Can I make the survey anonymous if I need to follow up on specific issues?
Default: keep results anonymous or confidential to build trust and get more honest feedback. Add an optional follow-up field at the end ("If you want a reply, leave your email") rather than requiring names up front. Keep location fields practical (Site/Building and maybe Floor/Zone) so you do not accidentally identify individuals.
How do I turn results into a prioritized facilities plan people believe in?
Do this: prioritize items that are low-scoring and frequently mentioned, then assign an owner and due date for each fix. Track 2-3 repeatable KPIs (headline CSAT or CES plus key drivers like timeliness and updates) and publish a simple "You said, we did" update by site. People trust the process when they can see what changed and what is still pending.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED