Day5Group Blog · Implementation

Email and Chat Norms for a Four-Day Team

Async-first habits, response windows and out-of-office that routes somewhere useful.

A four-day week rarely fails in the calendar. It fails in the inbox.

When a team moves to 100-80-100 — full pay, 80% of the time, a commitment to full output — work that spilled across five days tries to compress into four. Messages get faster and more urgent, people who are off get copied “just in case,” and people who are in spend the day replying instead of producing. The UK 2022 pilot (61 organisations, around 2,900 staff) found output held and wellbeing rose only where firms redesigned work, not where they simply deleted a day. Communication norms were part of that redesign in almost every success.

Why the default inbox breaks at four days

In a five-day office, a slow reply costs an hour. In a staggered four-day team it can cost a fifth of the week: message Amara on her Monday off and you wait until Tuesday.

Three failures follow. Coverage by copying: whole teams get added so “someone” picks it up, inboxes inflate and ownership blurs. Urgency inflation: everything is marked urgent, so nothing stands out. The day-off leak: colleagues check chat “just to keep an eye,” reply once, and set an expectation of reachability. Pilots that measured real hours — the UK average fell from roughly 38 to 34 hours, not a clean 32 — show partial cuts give partial benefits. A day off spent monitoring chat is not a day off.

Set response windows, not response anxiety

Publish how fast each channel should move:

  • Chat: respond within a set window in your working hours — two working hours is common. Chat is not for decisions needing a record.
  • Email: one working day as the internal default. Stating a slower norm removes the pressure to watch the inbox.
  • Phone or agreed escalation route: reserved for genuine blockers that would breach a customer promise.

The operative phrase is working hours. If Priya works Monday to Thursday, a Thursday-afternoon message gets a Monday reply — and the sender knows in advance. Add core collaboration hours where staggered teams overlap (for example 10am–2pm, Tuesday to Thursday) and protect the day edges for focused work.

Make out-of-office route somewhere useful

A standard “I will reply on return” strands the sender for a day. Replace it with routing:

I work Monday to Thursday. For anything that cannot wait until Monday, contact [named buddy] or [shared queue]. For non-urgent items, I will reply on Monday.

Name a person or a queue, not an unowned mailbox. Give the sender a deadline to judge against. And confirm you will not be reading messages on the day off — if leaders write “checking in periodically,” the norm collapses.

Shared queues beat individual inboxes for customer work. The US and Ireland pilots in 2022 (33 companies, around 903 employees) reported revenue holding and 97% of staff wanting to continue; behind the headlines, firms kept customers covered with buddy cover and shared queues, not by staying reachable.

Write messages that need no thread

  • Subject states the ask: “Decision needed by Wed: supplier shortlist,” not “Quick question.”
  • Lead with context and deadline: who needs what, by when, what happens if it slips.
  • One topic per message. Bundled requests wait for the slowest item.
  • Decisions live in a log, not a thread — one searchable, dated page removes the need to copy everyone.
  • Default to written updates instead of status meetings; keep meetings for decisions and conflict.

Microsoft Japan’s August 2019 trial is remembered for a sales figure the company itself later qualified. The transferable lesson is the discipline paired with Fridays off: meetings capped at 30 minutes, fewer attendees, decisions recorded. The saving came from discipline, not the day count.

Actionable steps

  1. Draft a one-page channel charter: chat window, email window, escalation route, core hours. Agree it as a team.
  2. Rewrite out-of-office templates to name a buddy or queue and a return date, with no hint of monitoring on days off.
  3. Move one status meeting to a written update. Keep the slot for a month, then delete it if the update works.
  4. Create a decision log and link it in every channel header.
  5. Audit urgency for two weeks. Count how many “urgent” messages truly needed same-hour action; reset the threshold.
  6. Model the day off. No scheduled messages landing on reports’ days off; no replies on your own. Visible behaviour is the policy.

None of this needs new software. It needs agreement, written down, about how fast things move and where they go when someone is away — the mechanism that protects the fifth day.

Sources

  • UK 2022 pilot — Autonomy / Cambridge / Boston College, 21 February 2023: https://www.sciencedaily.com/releases/2023/02/230221113132.htm
  • US and Ireland pilots 2022 — 4 Day Week Global, December 2022: https://www.internationalworkplace.com/community-zone/news/four-day-week-pioneering-pilot-program-a-huge-success-new-research-reveals
  • Microsoft Japan, August 2019, reported 4 November 2019: https://www.whro.org/news/2019-11-04/microsoft-japan-says-4-day-workweek-boosted-workers-productivity-by-40

Day5Group is a consultancy that assists in the transition to a 4 day work week. More about Day5Group · All blog articles