How to Create a Work From Anywhere Policy for Remote Teams

A study of  tech workers found productivity actually dropped 8-19% when people went fully remote.

The reason? More meetings. Higher coordination costs. Less focus time.

So remote work doesn’t automatically make people more productive.

It only works when you design it to work.

I’ve seen this happen dozens of times with US, UK, and Australian companies hiring Filipino remote workers.

Companies like Atlassian, GitLab, and Dropbox have already figured this out. They’ve built policies that work across borders, time zones, and legal systems.

You can learn from what they did. And you can build something that works for your team, whether you’re hiring 3 people or 300.

Here’s how.

The Foundation: Scope and Eligibility

Start here: who can work from anywhere, and where exactly is “anywhere”?

This sounds obvious but most companies get it wrong.

For small companies hiring Filipino remote workers, your policy should spell out:

• Employment type that qualifies (direct employee through an Employer of Record, independent contractor, or agency staff)
• Approved countries or regions (Philippines for your remote workers, plus any US states or UK/AU territories where you’re registered)
• Maximum duration outside home jurisdiction (many companies use 30 days per year to limit tax exposure)

Atlassian’s “Team Anywhere” policy is a good template. They let employees work from anywhere, but only in countries where Atlassian has a legal entity. 

Offices are optional hubs, not mandatory locations.

You don’t need legal entities everywhere. But you do need to be clear about where your people can work without creating compliance nightmares.

Legal Compliance: The Part You Can’t Skip

If you’re hiring Filipino remote workers as direct employees, you need to follow Philippine labor law. Night differential pay.

Overtime rules. Rest periods. Leave entitlements.

If you’re hiring independent contractors instead, your contract needs to be airtight.

Clear deliverables. Specific timelines. IP ownership spelled out. Data security requirements.

But here’s the warning: don’t treat contractors like employees while calling them contractors.

If you control their daily schedule, require them to use your tools, and manage them like staff, you’re risking misclassification issues in both countries.

Australian employers need to pay special attention here. 

A 2024 Fair Work Commission case (Pascua v Doessel Group) ruled that a Filipino remote worker could access Australian workplace protections even while based offshore. 

This confirmed that Australian labor obligations can extend across borders.

Time Zones and Working Hours

This should be straightforward but it’s where communication breaks down.

Your policy needs to define core hours.

Best practice from companies like GitLab: require a small block of overlap time for real-time collaboration (2-4 hours), then let people work asynchronously the rest of the day.

Write it into the policy:

“Regular working hours align with Philippine time, with at least 3 hours overlapping with the hiring team’s local workday for meetings and real-time collaboration.”

Then support async work with written updates. 

Daily standups in Slack. 

Weekly progress reports. 

Shared documents that anyone can review any time.

The goal isn’t to watch people work. It’s to make sure work gets done without forcing everyone into endless meetings.

Performance Metrics That Actually Work

Remember that study showing remote productivity dropped 8-19%?

The problem wasn’t working from home. It was too many meetings and coordination overhead.

So measure outputs, not activity.

Convert every role into measurable outcomes. Customer service tickets closed. Content pieces published. Sales calls completed. Projects delivered on deadline.

Use simple dashboards or weekly written reports instead of monitoring online status. 

If someone delivers their work on time and at quality, it doesn’t matter if they took a long lunch or ran an errand during the day.

This builds trust. And trust is what makes remote work actually work.

Communication and Tools

Define which tools you’ll use:

• Day-to-day chat (Slack, Teams, Discord)
• Formal communication (email)
• Project management (Asana, Trello, Monday)
• Documentation (Google Docs, Notion, Confluence)

Set response time expectations. “Within 4 business hours during agreed working times” is reasonable for most roles.

Establish meeting norms. Every meeting needs an agenda. 

Default to async updates when possible. 

Respect that not everyone can attend every meeting live.

Security and Data Protection

Your policy should require:

• VPN use for accessing company systems
• Multi-factor authentication on all accounts
• Encrypted connections for file transfers
• Clean desk policy even when working from home

If budget allows, issue company-managed devices for workers handling sensitive data. If not, at minimum require updated antivirus software and OS security patches.

Some companies reserve the right to block access from certain high-risk countries for cybersecurity reasons. 

If you work with regulated clients (healthcare, finance, government), you might need client approval before a worker accesses their projects from a new location.

GDPR applies if you handle EU data. Australian Privacy Principles apply if you’re based in Australia. US rules are sector-specific but still matter.

Cover this in your policy and in your employment agreements.

Workspace Safety and Equipment

Some countries now regulate telework environments. Employers are expected to ensure workers have safe, ergonomic conditions even at home.

Your policy can include:

• A self-certification form where workers confirm they have a safe workspace
• Basic ergonomic guidelines (proper chair height, monitor positioning, adequate lighting)
• Optional equipment stipends for chairs, desks, or monitors

Approval Process and Duration Limits

Many companies use this framework:

• Work from your home country any time
• Work from another country only with manager and HR approval
• Maximum 30 consecutive days in any country where the company has no legal presence
• Worker is responsible for their own tax filing if they choose to work from a different jurisdiction

Log every approval in a simple form, HRIS note, or ticketing system.

This protects you. It also protects your workers by making expectations crystal clear.

What Breaks Remote Work Policies

Let me tell you what actually kills remote work arrangements.

One person treating work-from-home like vacation. Not responding during work hours. 

Getting caught at the grocery store when they should be available.

Small business owners report that one bad actor often leads to remote privileges being revoked for everyone.

Your policy needs teeth.

Define what counts as policy violation:

• Consistent non-responsiveness during agreed working hours
• Working another job during the same hours
• Security breaches or sharing credentials
• Lying about location when cross-border approvals are required

Define consequences. First warning. Performance improvement plan. Termination if it continues.

Most people will never test these boundaries. But having them written down protects everyone.

Your Policy Template

Here’s the structure that works:

Purpose and Philosophy – Why you support WFA and under what principles

Scope and Eligibility – Which roles, locations, and contract types are covered

Legal and Compliance – Governing law, tax responsibilities, EOR arrangements, PE risk limitations

Working Hours and Availability – Core hours, time zone overlap requirements, response expectations

Performance Management – Output metrics, reporting cadence, review processes

Tools and Security – Approved platforms, VPN/MFA requirements, data handling rules

Workspace and Equipment – Safety requirements, ergonomics, equipment stipends

Cross-Border Work – Maximum days, approval process, excluded countries

Policy Violations – What counts as abuse and what happens next