Remote Work Survey Template
Audit how distributed work is actually going — workspace, meetings, async habits, connection, and the office-days question everyone argues about.
Five minutes on how working remotely is going for you — the setup, the meetings, the loneliness or lack of it. Answers are anonymous and shape policy, not performance reviews.
Remote-work policy debates run on anecdotes: the executive who misses whiteboards, the engineer who finally has focus time, the new hire who has never met anyone. This survey replaces the anecdotes with a structured audit of how distributed work is actually functioning — and it is deliberately neutral, because a survey that telegraphs the answer leadership wants will get exactly that answer and nothing true.
What the matrix audits. Five rows cover the operational surface of remote work: physical workspace, meeting load, async communication, access to teammates, and focus time. These five are chosen because they trade off against each other — heavy meetings destroy focus time, strict async starves people of access — and a matrix exposes the trade-off pattern per company. The four-point scale has no neutral middle on purpose; "could be better" versus "works well" is the boundary policy needs.
The two loaded questions, handled carefully. Ideal office days is asked as a plain number preference, not "do you support our policy", so you learn the actual distribution — most companies discover a two-hump curve that no single mandate can satisfy, which is itself the finding. The connection scale is the wellbeing canary: isolation builds quietly and exit-interviews too late, and a simple 1–5 trended quarterly catches the drift. The equipment question caps picks at two to force prioritization, turning a wish list into a budget line.
What we left out. Productivity self-ratings (they measure confidence, not output, and everyone answers "more productive"), commute details, and manager-specific questions. This survey measures the system, not the people in it.
Give it a full week. Distributed teams answer on distributed schedules — the Sydney engineer sees your announcement at what is 3am for the office — so a 48-hour window quietly samples one time zone and calls it the company. Leave the survey open seven days with the close date set in advance, nudge once midweek, and check that response counts per arrangement roughly match headcount before treating the results as representative.
Who runs this. People-ops teams ahead of a policy review, founders sanity-checking hybrid rules that were set during a different company size, and team leads whose retro keeps circling "communication" without data on which kind is broken.
Make it yours. Add rows for your actual toolchain — "Documentation quality", "Time-zone overlap" — and keep the arrangement question first so every answer can be split by it: fully-remote and mostly-office employees will disagree about async, and the split is the insight. Run it quarterly with identical wording, export the CSV, and cut the matrix by arrangement. Then publish the results and one policy change; nothing kills survey participation faster than a survey that changes nothing.
Frequently asked questions
Should responses stay anonymous?
Yes — the template has no identity fields, and honest answers about isolation or meeting overload depend on it staying that way. The arrangement question is the only segmentation.
How do we compare remote and office employees fairly?
Split every answer by the first question in the CSV export. The same matrix row often scores oppositely across arrangements — that split is the actual finding.
How often is worth running this?
Quarterly. Connection and focus scores drift slowly; identical wording between waves turns them into trend lines you can act on before exit interviews do.
Can we collect responses from people who never open email?
Share the link in chat channels or embed the form on your intranet page — the inline embed keeps it one click. No respondent account is needed.