Hybrid working policy: what to include (with a template)

A hybrid working policy has to settle four things: who is eligible, when people are expected together, who pays for what, and where someone may work from. The mistake that breaks it is writing days in the office without writing why those days exist — a number with no reason behind it is negotiated away by the first manager who finds it inconvenient. Write the reason first, and the days defend themselves.

Most companies already have one. It is unwritten, it lives in the heads of six or seven managers, and it is different in each of them. The document does not invent the rules — it collects the decisions the company is already making badly, case by case, and turns them into one answer.

What a hybrid working policy has to settle

We trust people to work where they work best is a sentence about values, not a rule. It leaves every real question open: whether a support role can be remote, whether Tuesday matters, who buys the second monitor, whether someone can work two months a year from another country. Managers answer those themselves, and the company finds its actual policy months later, in the gaps between teams.

The test is whether a manager can answer from the document without escalating, and would give the same answer any other manager would. That takes eight decisions, each with the version that gets written when nobody has thought about it, and the version that works.

The last column is the one most drafts leave out, and the one that keeps a policy alive. An unowned rule gets re-argued every quarter until it quietly becomes whatever the most insistent team does. An owner also gives exceptions somewhere to go.

A remote work policy skeleton you can adapt

Nine sections, one page in total once the decisions are taken. Each line says what belongs in the section; the sentence that goes there is the company's own.

1. Purpose and scope. The question this policy answers, and every group it covers — probation, part-time and contractors included.
2. Eligibility. Which roles can work remotely and which cannot, with the reason stated by role.
3. Presence expectations. The anchor days, who sets them, and the activity they exist for.
4. Core hours and response times. The overlap window, and what is expected on each channel outside it.
5. Meetings. The format rule, which meetings need the room, and how a remote participant is included rather than tolerated.
6. Workspace, equipment and expenses. What the company provides, what it reimburses, what limit applies, and how a claim is approved.
7. Data security. Devices, networks, what never leaves company systems, and who to tell when something is lost.
8. Working from another location. Where someone may work from, for how long, and what approval another country needs.
9. Exceptions, owner and review date. Who approves a variation, where it is recorded, and when the document is looked at again.

The rule that makes hybrid work

Decide presence by activity, not by a count. A fixed number asks everybody in on the same terms regardless of what they are coming in for, which is why it feels arbitrary and ends up defended with attendance data instead of reasons. The better rule is short: name the work that is genuinely better in the same room, and build the calendar backwards.

• Work where disagreement has to surface. Planning a quarter, choosing between two product directions, splitting a budget. These depend on somebody saying the awkward thing, which is rarely said into a muted microphone.
• Work where somebody is learning by proximity. A new joiner, or anyone taking on a part of the job they have not done before. Ramping up is mostly overhearing, and there is no remote substitute for the question asked across a desk.
• Work that is already stuck. A decision bouncing across three threads, a handover that keeps missing, a design nobody can describe in writing. An hour in a room usually ends it.

Once those are named, days stop being a rule to enforce and become a consequence. A team whose quarter starts next week owes itself more time together than a team mid-delivery, and both follow the same policy. The company sets the floor; the rest is scheduling, decided by whoever is accountable for the work.

A policy that says three days in the office and never says what the three days are for is a rule with nothing underneath it. The first inconvenient week finds that out.

How to tell whether it is working

Resist the urge to measure this with attendance dashboards. Badge data tells you who came in, which is the one thing the policy already told them to do. The signs worth watching are observable without instrumenting anybody.

• Meetings stop needing everybody. When presence has a purpose, the standing meeting with eleven attendees shrinks to the four who decide, and the rest read the note. A calendar that has not changed says the policy has not either.
• New joiners get productive without an escort. If people who joined after the policy are working on their own by the end of the first month, the presence rules are covering what has to be learned next to someone.
• Managers stop policing attendance. When a manager can point at what the office days are for, they no longer have to defend the days themselves, and the conversation moves back to the work.

The reverse is just as visible. Repeated exception requests from one team usually mean the rule was written for a different kind of work. People coming in and spending the day on calls means the anchor days were set without asking what happens on them.

Three questions that come up every time

How many days a week in the office?

There is no number that is right in general, and picking one before deciding what presence is for is how a policy loses its authority. A workable start at this size is one shared anchor day for the whole company, plus whatever each team adds for the activities above. Set the floor centrally, let the function leads decide the rest, and write the reason next to the number.

Who pays for what when people work from home?

The law where the person works sets the frame, and the policy has to say clearly who pays for what inside it: what the company provides, what it reimburses, what it does not. The limits belong in the policy, agreed with finance and carrying a review date. What breaks trust is not a modest contribution; it is a policy that says the company supports home working and never says what that means when the bill arrives.

Can we have different rules by team?

Yes on presence, no on entitlements. Which days a team is together belongs to whoever is accountable for that team's work — a support function covering a phone line and a product team shipping in bursts do not need the same week. What cannot vary is the part people compare: eligibility, expense limits, security rules, flexibility for parenting. Different reasons are fair; different money is not.

Where this fits

A hybrid policy is not a document problem. It is a set of decisions the leadership team has been avoiding, and writing them down is the cheap part once they are made. Taking those decisions for a specific company — the presence rule it can defend, the limits it can afford — is the work in Policies & Benefits.

Related reading: the first eight HR policies a company should write, and role clarity in growing teams, because a hybrid policy cannot fix a team that is unclear about who decides.