Physical Security Survey Template
Use this ready-to-launch physical security survey to measure how well your controls work in practice across entrances, visitor handling, CCTV/monitoring, response, and emergency readiness. You will get comparable site-by-site results, plus role and shift cut views so Facilities, Security, HR, and IT can prioritize fixes with clear owners and close-by dates.
Trusted by 5000+ Brands
Customize by Site Type and Risk Level (Stakeholder Map + Swaps)
-
Map who can answer what (and who owns the fix)
Goal: Get credible answers by asking each role only what they see day-to-day.
Default setup: One core survey for everyone, plus 2-3 role branches (guards, reception, contractors).
Do this now:
- Employees: perceived safety, where/when issues happen, reporting comfort, badge/door friction.
- Guards/security officers: post orders clarity, patrol coverage, hand-offs between shifts, response coordination.
- Reception/front desk: visitor exceptions, escort adherence, delivery handling, after-hours arrivals.
- Contractors/vendors: onboarding/badging friction, escort rules, access to loading docks and work zones.
- Decision owners: Security (procedures/coverage), Facilities (lighting/locks/doors), IT/SecOps (badges/CCTV systems), HR (safe-reporting routes and follow-up expectations).
-
Lock your core question set (keep wording neutral and single-issue)
Goal: Make results comparable across sites and repeatable quarter to quarter.
Default setup: 3-5 safety/culture items + 8-12 control experience items + 2 open-text prompts.
Do this now:
- Use one scale across most items (e.g., Strongly disagree to Strongly agree).
- Ask one idea per question (avoid combining two controls like doors and CCTV in one item).
- Write behavior/process prompts, not vulnerability prompts (e.g., "Badge checks are consistent" vs "How can someone break in?").
- Run a 5-minute read-through with Security and Facilities to remove acronyms and site-specific slang.
In practice, you get cleaner data when questions stay clear, specific, and consistent across respondents (see practical questionnaire wording tips in Crafting an Effective Questionnaire).
-
Add site modules (swap, do not stack)
Goal: Cover the risks that vary by environment without bloating the survey.
Default setup: Add one module per site type (6-10 questions each), and keep total survey time under 8 minutes.
Do this now:
- Office: after-hours access, tailgating at main entrances, reception coverage, stairwell safety.
- Warehouse/DC: loading dock control, trailer seals, yard gates, high-value cage access, night shift coverage.
- Retail: cash office access, shoplifting visibility, de-escalation support, back-of-house doors, closing procedures.
- Healthcare: patient/visitor flow, restricted units, workplace violence concerns, duress alarms, security presence.
- Mixed-tenant: shared lobby rules, landlord vs tenant responsibilities, shared CCTV and access credentials.
- Construction/temporary sites: fencing integrity, tool/asset storage, temporary badging, delivery control.
Default pick: If you are unsure, start with office + warehouse modules only, then expand after the first run.
-
Branch by role (so you do not waste anyone's time)
Goal: Get detailed control feedback from the people closest to the work without adding noise.
Default setup: Use one screening question: "Which best describes your role at this site?"
Do this now:
- If guard, then show patrol/hand-off/post-order items and a "coverage gaps by time" question.
- If reception, then show visitor exception questions (late arrivals, deliveries, escort refusals).
- If contractor, then show onboarding/badging friction and "who to contact" clarity.
- If site lead/manager, then add 3-5 ownership items (training completion, drill frequency, action tracking).
-
Pilot with one site and one shift before full rollout
Goal: Catch confusing wording and broken branching before you ask the whole organization.
Default setup: 10-15 people total: day shift + night shift + one contractor + one guard.
Do this now:
- Time the survey on a phone (target: 6-8 minutes).
- Ask pilots to flag any question they could not answer confidently.
- Remove any question that prompts names, admissions, or detailed vulnerabilities.
Next step: Choose your question modules. Which areas do you need to measure first: access, visitors, CCTV/monitoring, response, or readiness?
Question Modules to Cover Access, Visitors, CCTV, Response, and Readiness
"I feel physically safe at my primary work site."
Why it matters: This is your anchor outcome. Use it to trend perceived safety even when you change controls or staffing.
When to use: Include in every run. Default setup: Pair with 2-4 supporting items (reporting comfort, after-hours safety, entry points).
Do this now:
- Keep the same wording every time so your trend line stays clean.
- Add a "Not applicable" option only when a control truly varies by location (e.g., CCTV presence).
- Report results as an index (average score), not a single anecdote.
"Which site do you work at most often?"
Why it matters: Multi-site results fall apart when respondents cannot reliably pick a site.
When to use: Put this first. If people work across sites, add a second item: "Which other sites do you visit at least monthly?"
"Badge-controlled doors prevent unauthorized entry in my work areas."
Why it matters: You will see control effectiveness (not just control existence) across entrances, interior doors, and restricted zones.
When to use: Ask all employees and contractors. Branch a follow-up for guards: "How often do you see tailgating at entrances?"
"When I forget my badge (or it fails), the process to regain access is clear and timely."
Why it matters: Confusing exception handling drives workarounds like propped doors and shared badges.
When to use: Include if you see frequent badge issues or have many contractors. Add a branch for reception: "How often do exceptions bypass sign-in?"
"Visitors are consistently signed in and escorted when required."
Why it matters: Visitor management breaks first during busy periods and after-hours arrivals.
When to use: Ask everyone. Branch for reception and guards on exceptions (deliveries, vendors, interviews, late arrivals).
"Exterior lighting and visibility around entrances and parking areas are adequate."
Why it matters: This pinpoints facilities-owned fixes that often drive safety perception (lighting outages, blind corners, overgrown landscaping).
When to use: Use for any site with parking lots, loading docks, or pedestrian routes. Add a follow-up: "Which area is worst?"
"Cameras and monitoring (where present) help deter or resolve security incidents at this site."
Why it matters: You will learn where CCTV is helping, where it is ignored, and where coverage gaps create rework during investigations.
When to use: Include with a "Not present" option. Branch for guards/site leads: "How quickly can footage be accessed when needed?"
"When a security concern is reported, response is timely and appropriate."
Why it matters: Slow or unclear response reduces reporting and pushes people to handle issues alone.
When to use: Ask everyone. Branch for guards and managers on escalation steps and hand-off quality between shifts.
"I know what to do and who to contact in an emergency at my site."
Why it matters: Clear contacts and simple steps beat long policies during real events.
When to use: Use everywhere. Add site-lead items on drill frequency and after-action follow-through.
"I can report security concerns without fear of negative consequences."
Why it matters: This measures safe-reporting and whether people trust the process to handle concerns without blowback.
When to use: Include in every run. Add a follow-up multiple choice: "What makes reporting hard? (Not sure who to contact / takes too long / worry about retaliation / nothing changes / other)."
"What location(s) or time(s) at this site feel least safe, and why?"
Why it matters: Hotspots usually show up as specific places (stairwells, parking, loading docks) and specific times (shift change, after hours).
When to use: Always include. Ask for locations and times only. Do not ask for names or details about wrongdoing.
"Rank the top 3 improvements that would most improve physical security at your site."
Why it matters: Ranking forces tradeoffs and helps you separate "nice to have" from what people think will change day-to-day safety.
When to use: Put near the end. Use options like lighting, badge access reliability, visitor process, guard coverage, camera coverage, reporting channel clarity.
For broad topic coverage, use a checklist approach similar to the categories shown in the GAO's Survey on the Physical Security of Federal Facilities, then tailor items to what your people can observe.
Next step: Plan your rollout. Which sites and shifts need a different distribution method (email vs QR vs kiosk)?
Deployment Plan and Sampling for Multi-Site, Shifts, and Contractors
Set your segments before you send
Goal: Get stable site-by-site results without missing night shift, guards, or contractors.
Default setup: Segment by site + role + shift (day/evening/night) and keep demographics optional.
Do this now:
- Create a site list that matches how actions get owned (building, campus, store, DC).
- Use a single role question for branching (employee, guard, reception, contractor, site lead).
- Add a shift question if work experience changes by time (entrance staffing, lighting, patrol coverage).
- Decide your minimum reportable group (example: do not show cut views under 5 completes).
Use mixed-mode distribution for sites without email
Goal: Make it easy to participate from the floor, the dock, and the front desk.
Default setup: Email for corporate roles + QR posters + a kiosk/tablet option for on-site roles.
Do this now:
- Post QR codes near break rooms and clock-in areas (not next to a supervisor desk).
- Set up a tablet/kiosk link for guards and reception if phones are restricted.
- Give contractors a dedicated link they can access from a personal device.
- After this, document your sampling plan so coverage does not drift by site or shift.
Schedule the field period around shifts (not calendars)
Goal: Avoid day-shift-only results.
Default setup: Keep the survey open 10-14 days and include at least one weekend.
Do this now:
- Send shift-timed reminders (one for each shift start window).
- Offer a 10-minute paid time block for hourly roles where feasible.
- Stagger launch by site if you need local comms (posters, tool-box talks, guard briefings).
Run a reminder sequence that fixes participation gaps
Goal: Reduce skew when some groups do not respond.
Default setup: 2-3 reminders with a clear close date and a short reason to participate.
Do this now:
- After reminder 1, check completes by site and role; target the groups lagging behind.
- Use different channels for lagging groups (posters, supervisor message, guard roll call).
- If one shift stays quiet, treat that as a signal and plan a make-up push.
- Track nonresponse and response bias so you do not mistake silence for agreement.
Nonresponse can meaningfully skew results when certain job types do not participate (a practical example appears in a healthcare employee survey nonresponse bias study).
Set minimum completes per site and role (and decide what is directional)
Goal: Know when to act confidently vs when to treat findings as a lead to validate.
Default setup: Aim for 30+ completes per site overall and 10+ per key role per site (guards, reception, contractors) where headcount allows.
Do this now:
- If a site is small, combine results across 2-3 quarters before comparing to other sites.
- If a role is tiny, oversample it (direct invite + kiosk option) so the view is not one person's opinion.
- Use sample size guidelines to pick thresholds that match your segmentation and headcount.
Choose anonymous vs confidential (and say it plainly)
Goal: Get candid feedback without breaking trust.
Default setup: Use anonymous responses for broad perception and hotspot reporting; use confidential tracking only when you have a clear follow-up workflow.
Do this now:
- If you need candid feedback on sensitive topics, use an anonymous link and state who cannot see identifiers.
- If you need to assign tickets, use confidential tracking and explain exactly who can access respondent info.
- Point participants to your Security and privacy guidance in the invitation and on the first survey screen.
Privacy conditions can change how people respond, especially on sensitive items (see an example in a randomized trial on privacy conditions and survey response).
Next step: Define how you will score and report results. Which metrics will you trend across sites and which will stay site-specific?
Benchmarks, Targets, and the Executive vs Site-Lead Report Set
Note on targets: The numeric ranges below are internal starter targets (not industry benchmarks). Set your baseline on run 1, then adjust by site type, distribution method, and risk level. Use your sampling plan and checks for nonresponse and response bias to avoid over-interpreting differences driven by uneven participation.
| Metric / report | How to calculate (copy/paste) | Starter target (adjust to your reality) | How to use it |
|---|---|---|---|
| Setup checklist |
Goal: Comparable results across sites, roles, and shifts. Default setup: Track response, perceived safety, and action closure. |
Do this now:
|
Use this row as your minimum measurement set for every run. |
| Response rate (employees) | Completes / invited employees (by site, role, shift) | Internal starter target (adjust after baseline): 50%-75% per site when comms are strong | Use as a data-quality gate. If night shift is 20 points lower, treat comparisons cautiously. |
| Response rate (contractors/vendors) | Completes / invited contractors (or estimated active contractor headcount) | Internal starter target (adjust after baseline): 25%-50% when access is mixed-mode | Track separately so contractor experience does not disappear inside employee averages. |
| Response rate (guards + reception) | Completes / headcount in those roles (per site) | Internal starter target (adjust after baseline): 60%-90% when you provide kiosk/tablet access | Oversample these roles. Their views often predict response and visitor-process gaps. |
| Perceived Safety Index (PSI) | Average 3-5 core Likert items (example: safety, after-hours safety, reporting comfort, response timeliness) | Internal starter target (adjust after baseline): Set a baseline on run 1, then target +0.2 to +0.4 points over 6-12 months (on a 1-5 scale) | Use for your org-level heatmap by site and for trend lines after changes (staffing, access system upgrades). |
| Control Friction Index (CFI) | Average 3-6 items on badge failures, visitor exceptions, and workarounds | Internal starter target: Lower is better; start by targeting the worst 2-3 sites for a focused fix sprint | Use to prioritize process and technology fixes that reduce workarounds (propped doors, shared badges). |
| Hotspot rate | % of respondents naming at least one hotspot (location/time) + top 5 hotspot themes | Internal starter target: No fixed target; aim for fewer repeated hotspot mentions after fixes | Use as a site-lead action list: "top places" + "top times" + owning team (Facilities/Security). |
| Action Time-to-Close | Days from action created to closed (median by action type) | Internal starter target (adjust after baseline): Quick wins: 14-30 days; projects/capex: set a dated milestone plan | Use for executive accountability. Track aging (open >30/60/90 days) and closure rate. |
| Executive report set (monthly or per survey) |
|
Internal starter target: Keep the pack to 6-10 slides | Use to decide funding, staffing, and policy changes. Avoid blaming any one site; focus on fixable systems. |
| Site-lead report set (weekly during action period) |
|
Internal starter target: 30/60/90-day tracking cadence | Use to run close-the-loop meetings and remove blockers (work orders, access changes, training refresh). |
Turn Results Into a Balanced Scorecard and Prioritized Action Plan
-
Goal: Turn responses into a scorecard and a short, owned action list you can actually close.
-
Default setup: Review results by site, role, and shift; publish an executive pack + a site-lead action tracker.
-
Clean and segment first: Remove test responses, then cut results by site, role (employees/guards/reception/contractors), and shift. Treat any cut under your threshold as directional, not definitive.
-
Look for actionable gaps (not noise): Flag the bottom 3 items per site and the biggest role gaps (e.g., guards score response lower than employees). Do not over-interpret small-N differences.
-
Summarize open text safely: Group comments into themes (locations, times, process blockers). Remove names and identifying details before you share excerpts.
-
Build a balanced scorecard: Assign each finding to one bucket so you do not over-fund tech while ignoring process.
- People: staffing coverage, training clarity, confidence in response.
- Process: visitor sign-in, exception handling, escalation steps, hand-offs.
- Technology: badge reliability, CCTV access, duress/panic systems.
- Physical environment: lighting, doors/locks, sightlines, parking and docks.
-
Prioritize with Impact x Effort (add urgency): Create a 2x2 list, then tag each action with an owner and a due date.
- Owners: Facilities (lighting/locks), Security (coverage/procedures), IT (badges/CCTV), HR (reporting routes, anti-retaliation comms).
- Due dates: quick wins (2-4 weeks) vs projects (milestones + budget).
-
Close the loop: Tell participants what you heard, what you are fixing, and when. Then rerun a short pulse on the same 5-8 items tied to actions in flight.
Keep the survey focused on perceptions, locations, times, and process barriers. Do not ask for names or details that could identify someone, and route allegations or reportable events to your formal incident channel. Publish your aggregation rules up front and align them with your Security and privacy guidance.
Next step: Decide your module set for the next run. Which 5-8 items will you keep constant so you can prove improvement?
Frequently Asked Questions
Should this physical security survey be anonymous or confidential?
Use an anonymous link when you need candid feedback about safety concerns, reporting comfort, or hotspot locations and times. Use confidential tracking only when you have a clear follow-up workflow (for example, assigning a facilities ticket) and you can explain exactly who can see identifiers and how results will be aggregated.
How often should we run a physical security survey?
Run a baseline survey after major changes (new site, access system change, staffing model change) and then repeat annually or semi-annually to trend results. Add a short quarterly pulse with the top 5-8 items tied to actions you are actively closing.
How do we include shift workers, guards, and contractors who do not have corporate email?
Use mixed-mode distribution: QR posters in break areas, a tablet/kiosk link at the post or front desk, and a contractor-friendly link they can open on a personal device. Keep completion private and voluntary, and avoid having supervisors stand over people while they respond.
What sample size do we need per site to trust the results?
Start with simple minimums: aim for about 30+ completes per site overall and 10+ per key role per site (guards, reception, contractors) when headcount allows. If a site or role is smaller than that, combine sites, combine time periods, or treat the view as directional and validate with follow-ups using your sample size guidelines and sampling plan.
How should we ask about incidents without asking people to name individuals?
Ask for patterns, not people: locations, times, and what made reporting or response hard (for example, unclear contacts or slow follow-up). Include a reminder in the question text: "Do not include names" and provide a separate formal incident channel for reportable events and allegations.
How do we present results to executives vs site leads?
Give executives a scorecard and heatmap by site, the top 3 recurring risks, and budget asks tied to Impact x Effort and urgency. Give site leads hotspot lists (location/time), role differences, and a 30/60/90-day action tracker with owners in Security, Facilities, IT, and HR.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED