Agree how a split team works together
A distributed team works well when everyone knows when people are reachable, where a decision is made and how someone who was off shift finds out. This page walks a manager through writing that down as a short working agreement and reviewing it regularly.
The examples follow Northstar Services, a fictional customer support team of 18 people in Dublin, Austin and Manila. They work three eight-hour shifts that hand over to each other around the clock. All times are in UTC so that everyone reads the same clock. Local start times shift with daylight saving, so check them each spring and autumn.
This is a practice for one team. It does not set company-wide channel rules, and it does not replace organizational policy. Applicable organizational policies take precedence over anything a team agrees locally. People Development owns this guidance; send corrections to them.
Step 1: Map availability
Sample shift map for Northstar's support team. Times are UTC. Hours are illustrative, not a staffing standard.
| Shift | Location | Team time (UTC) | Handoff note due |
|---|---|---|---|
| A | Dublin | 06:00–14:00 | 13:30, read by Shift B |
| B | Austin | 14:00–22:00 | 21:30, read by Shift C |
| C | Manila | 22:00–06:00 | 05:30, read by Shift A |
Step 2: Set decision channels
Name the channel before a situation arises. Northstar sorts requests by how long they can wait, not by who is online at that moment.
A temporary operational action within the shift lead’s authority is needed for a current customer impact or active-work blocker. Permanent cross-shift changes use the consultation path.
- Post in the live support channel and tag the shift lead.
- The shift lead acts as decision owner and replies within 15 minutes. If there is no reply, escalate to the team manager.
- Example: a billing error affects about 40 open chats at 15:10. The Shift B lead pauses the affected macro within their authority, immediately records the temporary action and effective time in the decision thread, and alerts colleagues currently handling those chats. The 21:30 handoff links to that record for Shift C.
Wording changes, process improvements and anything that benefits from input from every location.
- Open a post in the decision thread. Name the decision owner, the question and the closing time.
- Keep it open for 24 hours so each shift has at least one working period to respond.
- Example: the owner proposes new refund-macro wording at 08:00. Shift A, B and C comment during their shifts, and the owner closes the thread the next morning with the final wording.
Step 3: Include the shifts that are not in the room
These are working commitments the team agrees to keep. They are a static reference list, not a checklist, a certification or an attestation.
- Record urgent temporary actions immediately in the decision thread, with the responsible role, effective time and affected work. Record other completed decisions during the same shift.
- Post the handoff note 30 minutes before the shift ends, listing open items, who is waiting on a reply and what is due next.
- Keep nonurgent decisions affecting all shifts open for 24 hours. Review urgent temporary actions in the next all-shift consultation cycle before turning them into permanent changes.
- Share meeting notes in the team channel within one hour of the meeting ending.
- Rotate recurring meeting times each month so the same shift is not always attending outside its working hours.
- Start each shift by reading the previous handoff note and the decision thread before replying to open items.
Who does what, by role
Roles in the working agreement. These describe responsibilities, not named staff.
Team manager
- Publishes the agreement and keeps it current.
- Handles escalations when a decision owner cannot be reached.
- Chooses the review time so it rotates across shifts.
Shift representative
- Collects missed-update examples from their shift before the review.
- Checks that the handoff note reflects what happened on their shift.
Decision owner
- States the question and closing time when opening the thread.
- Summarizes the outcome and who needs to act on it.
Step 4: A completed agreement and its first review
Northstar support team working agreement (sample)
- Availability: Three shifts as mapped above. Handoff notes are due 30 minutes before each shift ends.
- Urgent temporary actions: Live support channel, shift lead decides within their authority, reply within 15 minutes, escalate to the team manager if there is no reply. Record the action immediately and alert affected colleagues who are working.
- Nonurgent cross-shift decisions: Decision thread, 24-hour consultation window, decision owner named in the first line. Review urgent temporary actions in the next all-shift cycle before making a permanent change.
- Absent shifts: Handoffs link to the relevant decision records. Meeting notes are shared within one hour.
- Review: Monthly, 30 minutes, at a time that rotates between shifts. Also review after a shift pattern changes, a new location joins, or the same kind of update is missed twice in a month.
What a review conversation sounds like
The team manager asks: where did the agreed handoff fail?
- Compare. Shift B paused a faulty macro at 15:10 and recorded the temporary action in the decision thread. Its 21:30 handoff omitted the record link.
- Find who missed it. Shift C started at 22:00 and missed the decision-thread update. It learned about the pause at 22:20, after two replies had used the old macro.
- Agree one adjustment. Each handoff now includes a short “changes effective this shift” list with decision-record links. The incoming lead acknowledges those changes before the team starts replying; if a link or action is unclear, the lead checks with the outgoing lead or manager. Shift B’s representative checks the next three handoffs and reports whether the acknowledgment happened at the next review.
The adjustment adds a visible acknowledgment to the existing reading rule. Review whether it prevents missed changes before adding more steps.
Before relying on a company policy, check its stated audience, location and effective period. Ask the policy owner when applicability is unclear.