How to write a work from home policy that holds up in practice

A work from home policy that lives in a manager’s head isn’t a policy. It’s a rumor with a reporting line, and every team ends up with a different version.

This guide shows you how to write a work from home policy employees will actually follow, in four steps: survey people before you draft, cover the key components in plain language, communicate the reasoning, and measure satisfaction on a fixed review cycle.

A work from home policy is the written document that sets out who can work from home, under what conditions, and what both sides are committing to.

Its job is to remove ambiguity, so managers stop improvising and employees stop guessing. It is narrower than a flexibility strategy and more specific than a statement of principles.

Judge a draft by one test: can a new manager answer a request using only this document. If the answer requires a phone call to HR, the policy is not finished.

Every working policy resolves the same short list of questions. If your draft leaves any of these open, that gap is where inconsistency will appear:

Work from home is one format within a broader set of options, including hybrid patterns, flexible hours, and compressed schedules. If you are still deciding which formats to offer, work through the design process for flexible work arrangements before drafting this document.

Unwritten remote-work norms drift, and they drift differently on every team. Two years of informal practice produces a situation where nobody can say what the rule is, which makes any later change feel like something being taken away.

A written policy also gives employees something to point to. That matters most in the cases where a manager's preference and the company's position are not the same.

Survey first, because a policy written in a conference room answers the wrong questions. The purpose of the pre-draft survey is not to put the policy to a vote, it is to find out where the genuine friction and the genuine misunderstandings are.

Be explicit about that distinction when you field it. Telling people that their input shapes the document but does not decide it prevents the disappointment that follows a survey mistaken for a referendum.

Ask about current practice, blockers, and expectations, in that order. Current practice is the most useful and the most commonly skipped, because most organizations do not actually know what their people are doing now:

Question four is the one to keep. The spread of answers tells you exactly how much ambiguity you are currently operating under, and it is usually more than leadership expects.

Use anonymous collection, because the honest version of "my manager discourages this" will not arrive any other way. Employees are also reasonably skeptical that a survey about remote work is a prelude to restricting it, and that suspicion suppresses response rates.

Address it directly in the invitation. State what you are doing with the results, who will see them, and when people will hear back, then hold to all three.

Include two or three satisfaction and clarity measures now, worded exactly as you intend to re-ask them. Step four of this process depends on having a before figure, and it cannot be reconstructed after the fact.

SurveyMonkey features including anonymity settings, recurring surveys, and multi-survey analysis let you field this cycle and every later one from the same place, so the comparison stays clean.

Draft in plain language and organize by the questions employees will ask, not by legal structure. A policy nobody reads is functionally identical to no policy, and density is the main reason people stop reading.

The sections below are the components to cover. Treat them as a prompt list: the specific wording on anything touching employment law, pay, safety, tax, or data protection must come from your own counsel, not from a template.

Say which roles or role types are covered and what makes a role ineligible. Base it on stated requirements of the work rather than seniority, because seniority-based eligibility is the fastest route to a fairness complaint.

Name the decision-maker and the appeal route. Also state whether eligibility is permanent, reviewed, or tied to a specific arrangement.

Define core hours, expected availability, and response expectations separately, because conflating them is what turns flexible hours into extended hours. Be specific about whether time outside core hours is genuinely the employee's own.

Cover how time is recorded where that applies to the role. Hours, overtime, and break entitlements vary by jurisdiction and employment type, so this section in particular needs legal wording rather than drafted wording.

State what the company supplies, what it reimburses, and what the employee is responsible for. Ambiguity here produces a steady stream of individual negotiations, which is exactly what the policy exists to prevent.

Address the workspace itself in general terms and have counsel supply the specifics. Requirements around home workspace health and safety, employer liability, insurance, and the tax treatment of reimbursements differ significantly by location.

Set out the rules for devices, networks, physical documents, and confidential conversations away from a company site. Keep it behavioral and readable, and point to your existing information security policy for the technical detail rather than restating it.

Have your security and legal teams own this wording. Data protection obligations depend on your regulatory environment and on where employees are physically located.

Say how performance will be assessed and confirm that it is assessed on output rather than visibility. Employees working from home reasonably worry about being overlooked, and an explicit statement here is worth more than a reassurance in a meeting.

Include the team-level expectations: meeting norms, documentation habits, and any required on-site days with the notice period attached. Vague on-site expectations are the single most common source of later friction.

Define what counts as an approved work location and what requires approval. "Working from home" and "working from another country for a month" are different propositions, and policies that do not distinguish them get tested quickly.

Flag this section for legal and payroll review without exception. Working across state or national borders can create tax, payroll, immigration, and employment-law obligations that a policy document cannot resolve on its own.

Put the review date inside the document. A policy with a stated review cycle is understood as current thinking, while one without a date is understood as a promise, and changing it later reads as a broken one.

Name what would trigger an earlier review, who owns it, and how changes will be communicated.

Communicate the reasoning alongside the rules, and brief managers before employees. A policy that arrives as a document attached to an all-company email will be interpreted by each manager individually, which undoes the consistency you drafted for.

Give managers the document, the reasoning, and the decision rules at least a week ahead. Then test them: ask each one to write down how they would answer a request they intend to decline.

The gaps in those answers are your remaining policy gaps. Fixing them before launch is far cheaper than fixing them in front of a team.

Publish a short summary of what the pre-draft survey found and how it shaped the document. This is the step that converts a survey into credibility, and skipping it is why the next survey gets a lower response rate.

Be specific and include the declines. Naming two things you could not do, with the reason, does more for trust than a longer list of things you could.

Put the policy somewhere people can find it without asking, and keep a single canonical version. Multiple circulating drafts recreate exactly the ambiguity the document was written to end.

Run one open question session, capture the questions asked, and publish the answers as a short addendum. Those questions are also your best guide to what needs rewording at the first review.

Measure on a fixed cadence and update on the same one. A work from home policy is a live document, and the useful question is not whether people like it but whether it is clear, fair, and being applied consistently.

Track clarity, fairness, and consistency rather than approval. Four measures are enough, and they should be worded identically to the pre-draft baseline:

Add request and approval data if you have it. A large gap in approval rates between two managers with similar teams is a consistency problem the survey will not always surface on its own.

Company averages hide the problems worth fixing. A policy can look well received overall while being applied in two completely different ways in two departments, and that is the finding that predicts attrition.

Filter by manager, role type, and location, and use thematic analysis on the open-ended comments so recurring language surfaces without someone reading every response. Then bring the specific team, not the company average, to the people who can act.

Revise the document on the stated review date whether or not the pressure to change it has arrived. A policy that visibly gets updated is one employees believe they can influence, which is what keeps the feedback coming.

Version the document, publish a short note on what changed and why, and reset the baseline for the next cycle. Then expect a new set of issues, because once the policy is working the remaining problems are usually about culture and collaboration rather than rules. Those are covered in our breakdown of hybrid work challenges.

SurveyMonkey gives HR teams the listening half of policy work in one platform: templates and 25 or more question types for the pre-draft survey, anonymity settings that produce candid answers about managers and fairness, and recurring surveys so each review cycle is a comparison rather than a fresh start.

Filtering and thematic analysis let you see how the policy is landing team by team, which is where inconsistency actually lives. The result is a document you can defend with data at the review, instead of with opinion.

Once the policy is settled, the harder work is keeping distributed teams connected and visible. Our guidance on remote employee engagement covers the cadence, channels, and metrics for that.