Three people. That's how many staff a Toronto bookbinder I know had when she asked everyone to work from home for two weeks in March 2020. Two weeks became six years. She never wrote a single policy document. By 2024 she'd lost one employee to a dispute over who paid for a home internet upgrade, another to a scheduling fight, and she was still doing payroll from a kitchen table. The company survived. Barely.
That story is the reason I care about this topic. If you run a small business, a remote work policy isn't bureaucracy. It's the difference between a flexible team and a slow-motion argument about whether the coffee machine at home counts as a business expense. And here's the thing most guides get wrong: they hand you a 15-page corporate template designed for a company with an HR department. You don't have one. You have you.
Key takeaways
- A usable policy for a small team fits on two pages. If yours runs longer, you're writing rules for problems you don't have yet.
- Decide the three or four non-negotiables first (availability, security, expenses, equipment). Everything else can be handled case by case.
- Write it with your team, not for them. A policy nobody helped shape is a policy nobody follows.
- Ground every rule in a real cost or a real obligation, not in what a big company does.
- Review it once a year, and change it when the business changes. A stale policy is worse than no policy.
How to create a remote work policy for a small business (without becoming a bureaucrat)
The short answer: write down the decisions you've already been making informally, then close the gaps that are costing you money or causing friction. That's it. You're not drafting legislation. You're putting six years of "we'll figure it out" onto a page.
Who should actually write it?
You, plus the two or three people most affected. I've watched owners hand this to an outside consultant and get back a document that referenced "cross-functional collaboration pods." Total waste of money. A small business policy needs to sound like the people who work there.
Practical setup: block two hours, invite everyone who works remotely, and ask them one question — "What has annoyed you or confused you about how we do this?" Write the answers on a whiteboard. You'll have 80% of your policy content before the coffee goes cold.
The four things to settle first
When I helped a five-person design studio put together their first remote arrangement, we started with what they argued about most: availability, equipment, expenses, and data. Those four cover almost every real dispute. Rank them by how much they've already cost you.
- Availability — core hours, response expectations, and what "offline" actually means.
- Equipment — who buys the laptop, who owns it, who fixes it when it dies.
- Expenses — internet, phone, heating, co-working desk. Name a number or name the rule.
- Data and security — where client files live, what can't go on a personal phone.
Notice what's not here: productivity monitoring. Skip it. In a team under 20 people you know exactly who's pulling their weight. Surveillance software on a five-person team is a solution looking for a problem, and it poisons trust fast.
How do I create a remote work policy, step by step?
Here's the sequence I use. It works whether you have three employees or thirty.
- List your current reality. Who already works from home, how often, and under what informal rules? You're documenting, not inventing.
- Identify the pain points. Missed deadlines, expense surprises, security scares, scheduling chaos. Each pain point becomes one policy line.
- Draft the four core sections (eligibility, availability, equipment/expenses, security) in plain language.
- Check your local obligations. This is the step small businesses skip, and it's the one that bites. See the compliance notes below.
- Circulate a draft. Give your team a week to read and comment. You'll be surprised what they flag.
- Get written acknowledgement. A signed page or an email reply. Not because you're litigious but because it ends the "I didn't know that" conversation forever.
- Set a review date. Twelve months out. Put it in your calendar now.
Which legal rules apply to a small remote team?
I'm not your lawyer, and I'll be blunt: this is where you should spend a little money on a local professional, because the rules are jurisdiction-specific and they change. What I can tell you is what to bring to that conversation, so you don't pay for an hour of someone explaining the obvious.
The usual suspects, in most places with a formal employment framework:
- Worker classification — a home office doesn't automatically make an employee a contractor. Get this wrong and the tax bill is unpleasant.
- Expense reimbursement — some jurisdictions require employers to cover work-from-home costs; others leave it to the contract.
- Health and safety at home — a home workstation can fall under workplace safety obligations in some countries.
- Working time and right to disconnect — several places now have explicit rules about after-hours contact.
Write your policy so it references these obligations without pretending to resolve them. One line — "This policy operates alongside applicable local employment law, which takes precedence" — saves you from redrafting every time a rule shifts.
Can you provide an example of a remote work policy?
Yes, and I'd rather give you a real-shaped one than a bulleted list of categories. Here's a template trimmed to what a small team actually needs. Adapt the brackets.
| Section | What to write (example) |
|---|---|
| Eligibility | All staff who've completed probation may work remotely up to 3 days a week, subject to role requirements. |
| Core hours | Everyone is reachable 10:00–15:00 local time. Outside that, respond within one business day. |
| Equipment | The company provides a laptop. It stays company property and is returned on exit. Staff supply their own desk and chair. |
| Expenses | £X/month home-office allowance covers internet and utilities. Pre-approved co-working desk rental is reimbursed at cost. |
| Security | Client files live only in [approved cloud tool]. No client data on personal phones. Report any lost device within 24 hours. |
| In-person | Team meets in person one day per month; attendance is expected. |
| Acknowledgement | Signed and dated by employee; a copy goes in the personnel file. |
That whole thing is under 200 words of actual text once you strip the table. Which is the point — the more you write, the more you have to enforce, and the more likely someone finds a loophole.
Should the policy say anything about monitoring?
If you monitor, you must disclose it. Many places require it, and ethically you should do it regardless. But my honest opinion: for a small business, monitoring is a red flag about your hiring, not your remote setup. If you don't trust someone to work from home, that's a management conversation, not a policy clause.
Is remote work going away in 2026?
No, but the shape of it has changed. The all-remote-everyone experiment of the early 2020s has largely settled into hybrid as the default for office-type roles, with fully remote reserved for specific jobs and specific people. Return-to-office mandates made a lot of headlines, and they did pull some teams back in — but most small businesses I come across never fully left remote in the first place. They just got quieter about it.
The more useful question for you isn't "is remote dying?" It's "what does my team actually need?" A 12-person marketing agency can run almost entirely remote. A bakery can't. That's not a trend, it's arithmetic.
What I'd watch in 2026 and beyond: the paperwork catching up. Classification rules, expense-reimbursement expectations, and right-to-disconnect norms are tightening in many places. Your policy should assume more scrutiny, not less.
Is a telecommuting policy the same as a remote work policy?
Practically, yes. The two terms describe the same thing, and most people use them interchangeably. "Telecommuting" is the older word, and it usually implied a defined schedule of working from home instead of the office. "Remote work" is broader — it can mean working from anywhere, including fully distributed teams that never had a central office.
For your purposes, pick one term and stick to it in your document. Consistency matters more than the label. If you're recruiting in a market where "telecommuting" still shows up in job ads, mention both once so nobody thinks they're applying for a different arrangement.
What most small business policies get wrong
The failure mode isn't a missing clause. It's a policy that copies a big company's structure onto a tiny team. I've seen a four-person consultancy adopt a 22-page remote policy — with sections on "cross-departmental escalation" for a company that had exactly one department. Nobody read it. It got ignored within a month, and the discipline of having any written agreement collapsed with it.
The second mistake: writing rules for hypothetical problems instead of real ones. You don't need a clause about international relocations until someone actually asks. You don't need a multi-tier approval matrix. You need clarity on the four things people argue about.
And the third: never updating it. A policy written in 2020 and untouched since will contain assumptions — about offices, about tools — that no longer match your business. Set the review date. Keep it alive.
My advice, and I'll stand behind this: keep it to two pages, write it with your team, and treat it as a living agreement rather than a legal fortress. The businesses that handle remote work well aren't the ones with the longest documents. They're the ones that decided what mattered, wrote it down, and then got back to work.
