Remote Team Working Agreement: A Sample You Can Copy
Co-located teams can survive on unwritten rules — you can see when someone is busy, grab them after standup, read the room. Remote teams can't. Every unwritten rule becomes a guess, and guesses across time zones become friction. A written working agreement replaces the guessing. Here's a complete sample built for a distributed team, and how to adapt it.
Why remote teams need it in writing
Three remote realities make explicit agreements essential: time zones (your "quick question" is someone else's midnight), invisibility (nobody can see your focus time, your workload, or that you're blocked), and async delay (a vague message can cost a full day of round-trips). The agreement below is designed around those three facts.
The sample remote working agreement
For a 6-person product team spread across US and European time zones:
Availability & overlap — "Our overlap window is 14:00–18:00 Central European / 8:00–12:00 Eastern. Ceremonies and pairing happen inside it; outside it, nobody owes anyone a synchronous reply." / "Calendars and status are kept honest: focus blocks and time off are on the calendar, and Slack status reflects real availability."
Communication — "Default to async, in public channels, in threads. A decision made in a call or a DM is written into the team channel the same day." / "Response expectations: direct questions acknowledged within one working day in the asker's time zone; the urgent channel within 30 minutes during the receiver's working hours." / "Urgent means production is down or a customer is blocked. Everything else is async."
Meetings — "The inconvenient slot rotates monthly between regions." / "Every meeting has an agenda and a doc; decisions are minuted in the doc, not left in the call." / "Cameras optional, notes mandatory."
Delivery & blockers — "A blocker is posted in the delivery channel as soon as it's known, not saved for standup — across time zones, standup can be 20 hours too late." / "Pull requests get a first review within one working day of the reviewer's local time."
Focus & respect — "Each person protects at least two 2-hour focus blocks per week; meetings don't override them without asking." / "Nobody is expected to reply outside their local working hours, and scheduled-send is used for messages written at odd hours."
How to adapt it for your team
Don't adopt this text wholesale — borrow the structure and argue about the specifics. The argument is the point: a 45-minute session where the team sets its own overlap window, response times and escalation path produces rules people actually keep. Happy Backlog's working agreement template and builder walk a team through exactly that: start from the template, vote on the clauses that matter, and leave with a written agreement — free, no signup.
Frequently asked questions
How is a remote working agreement different from a normal one?
The content overlaps, but remote agreements must explicitly cover overlap hours, response-time expectations per channel, and how decisions get written down — things co-located teams handle by osmosis.
Should response times be in the agreement?
Yes, and split by channel: what "urgent" means, where urgent things go, and what can safely wait a day. Most remote friction is really response-time ambiguity.
How often should a remote team revisit it?
Every quarter, and whenever the team's time-zone spread changes — a new member eight hours away invalidates the old overlap window.
Where should the agreement live?
Somewhere one click from daily work: pinned in the team channel and linked from the team wiki. An agreement nobody can find is a rumor.