"We're remote-friendly" is not a policy. It is a shrug. And shrugs collapse under pressure, the first time an employee moves to a different time zone, the first time someone complains about being excluded from a meeting, the first time a laptop gets stolen from a cafe in Lisbon.

A remote work policy is the operating manual for distributed teams. It answers the questions that come up when the shine wears off and the reality sets in. Here is how to write one that actually holds up.

The 9 sections every remote policy needs

1. Eligibility

Not every role can be fully remote. Be explicit.

Which roles are eligible for fully remote work?
Which are hybrid (specific days required in office)?
Which must be in-office?
What are the criteria for approval (tenure, role, performance)?

Example language: "All individual contributor engineering roles are eligible for fully remote work after 6 months of employment. Management roles are hybrid (2 days in-office per week). Operations and finance roles are in-office."

2. Geography and time zones

Employees will ask "can I move to Portugal?" You need an answer before they ask.

What countries can employees live in? (Tax, legal, and payroll implications here are huge.)
What time zone overlap is required with the core team? Many companies require at least 4 hours of overlap.
Do employees need to notify the company before moving?
Does a move trigger a salary adjustment? (Cost-of-living geography-based pay is controversial but increasingly common.)

3. Work hours and availability

Remote work is not "work whenever you want." That is contractor work. For full-time employees you need clarity.

Core hours: the time range when employees should be reachable (e.g., "10 AM to 3 PM local time")
Response time expectations on Slack, email, and other channels
How to signal "heads down" focus time
Who to notify if taking a mid-day break

4. Equipment and home office

The company provides equipment. Be specific.

Laptop model, monitor, peripherals
One-time home office stipend amount ($500-$2,000 is common)
Monthly internet or coworking stipend if offered
Who owns the equipment (the company, always)
Return process at the end of employment, tie this back to your offboarding process

5. Security and data handling

This is where most remote policies are dangerously thin. At minimum require:

Mandatory password manager (1Password, Bitwarden)
Full-disk encryption on company laptops
VPN usage on public Wi-Fi
Prohibition on storing company data on personal devices
Reporting protocol for lost or stolen devices
Clean-desk policy (don't leave laptops unattended in public)

In regulated industries (healthcare, finance) this section should be reviewed by a compliance lawyer.

6. Communication norms

Remote teams fail when communication is unclear. Set defaults.

Slack for quick questions and real-time chat
Email for formal or external communication
Written documents (Notion, Google Docs) for decisions that need to persist
Video for 1-on-1s, team meetings, and hard conversations
Default to async unless synchronous is explicitly better

Remote teams should lean heavily on async written communication to give people across time zones a fair shot at contributing.

7. Meetings

No meetings without an agenda
Default 25 and 50 minutes (not 30 and 60) to give people breathing room between calls
Cameras on for 1-on-1s and small team meetings; optional for large all-hands
Record key meetings so people in other time zones can catch up
Protect at least one "no meetings" day per week for deep work

8. 1-on-1s and management

Remote teams need MORE manager contact, not less. Every remote employee should have a weekly 1-on-1, no exceptions. The absence of hallway conversations means the 1-on-1 is the primary signal of how someone is doing. See running effective 1-on-1s for the full framework.

9. Attendance, leave, and "presence"

Remote teams still need attendance tracking, just in a different way. It is less about clocking in and more about visibility into who is available.

Shared team calendar showing PTO, focus blocks, and availability
Clear PTO request process, see PTO policies that don't suck
Status updates in Slack (active, focus, out) kept current
Regular check-ins on energy and workload, see burnout warning signs

For more on attendance, see building a culture of attendance beyond the time clock.

The hybrid work trap

Hybrid work often ends up as the worst of both worlds, the overhead of office space plus the coordination costs of remote work. It works when there are clear, consistent rules about which days everyone is in the office and what happens on those days.

The best-run hybrid teams we have seen all follow one rule: if you are going to require office days, make them meaningful. No solo Zoom calls from a desk next to a colleague. No empty offices on "in-office day" because the calendar was optional. Anchor days only work if leadership shows up first.

What to avoid

Surveillance software. Tracking mouse movement or taking screenshots destroys trust instantly. Measure outcomes, not activity.
"Proximity bias" in promotions. The person in the office every day should not have an unfair advantage over the remote colleague who ships more work. Track this explicitly.
Different policies for different people without transparent criteria. This breeds resentment.
"Temporary remote" that never ends. Set a review date.

Keep the policy in a living document

Do not bury the remote work policy in a 60-page handbook PDF. Put it in your employee handbook as its own searchable section, link it in onboarding, and update it every six months.

TracefyHR for distributed teams

TracefyHR was built with remote and hybrid teams in mind. Employee profiles, daily check-ins, leave management, attendance tracking, and analytics work the same whether your team is in one office or ten countries. See how it works →

Remote Work Policies That Actually Work: Templates and Examples