Inside a four-day working week
Open this roster ↗Six fictional colleagues. Four needed each day. After staggering their days off, the desk has 4 people on Monday and 5 on each other weekday. That covers the numbers. It does not settle the week. Monday’s absence is a one-day trial. From Tuesday onward, the example uses the agreed change shown below.
Four people scheduled.
One calls in sick.
At the desk
Blair3 present 1 below minimum
Scheduled day off: Alex · Frankie
The decision before opening
Monday already used its entire buffer. Removing Casey leaves three people for four required places. Spare people on Tuesday cannot cover Monday’s missing person-day.
A five-person team working four days would have 20 person-days, exactly the 20 this desk requires. Staggering one rest day per weekday covers the baseline but leaves no daily reserve anywhere.
For a reserve of one extra person on every weekday, this desk needs 25 person-days. Six four-day workers supply 24. No rearrangement alone can reach 25.
What the team has to decide
Who can provide agreed cover? Which service can be reduced if cover is unavailable? How will people waiting be told? A rota that silently assumes someone works on their day off does not preserve the four-day arrangement.
The busy day needs everyone.
At the desk
AlexBlair Day off moves to WedCaseyDrewEmFrankie6 present Exactly the minimum
Wednesday now has Blair & Casey off.
Change the requirement first
The original pattern had only five people on Tuesday. If that day needs six, using the same minimum of four everywhere hides the actual shortfall.
With Blair’s rest day moved from Tuesday to Wednesday, attendance becomes 4, 6, 4, 5, 5. Each colleague still has one weekday off. Wednesday falls from five people to four, so it now has no reserve.
The revised requirement is 4 + 6 + 4 + 4 + 4 = 22 person-days. The team still supplies 24; the two spare person-days sit on Thursday and Friday. A proposed move must be checked at both ends.
When moving a day cannot help
If Tuesday needs seven people, a team of six cannot meet it even if nobody is off. If the weekly minimum exceeds 24 person-days, six people working four days cannot meet that either. Change the staffing or the service requirement before rearranging the same names.
Four people here.
Nobody can approve.
At the desk
Alex AdviceDrew AdviceEm AdviceFrankie Reception0 approvers Casey is off
Example assumption: only Casey can authorise a decision.
Count the right capability
The Tuesday change left four people on Wednesday, exactly the stated headcount. But a customer who needs an authorised decision still cannot be served if Casey is the only qualified approver.
Moving Casey’s day off to Thursday simply moves that problem. One person working four days cannot supply a capability that is required on all five.
The team needs an agreed alternative: a second appropriately qualified person, an authorised backup, or a clearly communicated approval window. Writing a colleague’s name in the gap does not give them the necessary authority.
Build a useful skill check
List each essential task, the people who are permitted and able to perform it, and when it must be available. Check that list against each day’s actual attendance, including breaks and absences. This planner only counts people; it cannot certify training, access rights, supervision or safe staffing.
Em leaves a task.
Drew is not here yet.
Fictional handoff · no customer data
- Thursday, 16:00 · Em
- Room layout request is drafted. The contact has not yet confirmed the table count.
- Friday, 09:00 · Drew
- Read the reply. If the count is still missing, call the contact using the team’s approved record.
- Friday, 10:00 · Deadline
- Confirm the layout, or tell the requester it remains pending. Do not mark it complete without confirmation.
Em’s day off is Friday. Drew’s is Thursday.
Give the next person a usable starting point
These colleagues do not overlap at the moment the task is handed on. A calendar entry saying “Drew to cover” leaves the important facts unstated.
The note separates what is already done, what is waiting, the next owner, the first action and the deadline. A real handoff also points to the approved work record and explains who can resolve an exception.
If the deadline were Friday at 08:30 and Drew only started at 09:00, this handoff would still fail. A headcount for the whole day does not prove the right person is present at the required time.
Agree what happens during the gap
Make an explicit rule for urgent work arriving while the owner is off: who receives it, what they may decide, and when the requester gets an update. Use the team’s established system for confidential records. Do not ask an off-duty colleague to monitor messages as an unspoken part of a shorter week.
The team takes four days.
The desk still opens five.
Example public notice
Monday–Friday
10:00–16:00
Our colleagues work staggered four-day weeks. The desk remains open on all five weekdays.
Messages received outside these hours are reviewed when the desk next opens. For a pending request, quote the reference from your acknowledgement.
Fictional service hours; not the individual 8-hour shifts.
Publish the service people can actually use
“We work a four-day week” does not tell a visitor when the desk is available. State the service hours, closure dates and how a pending request is handed between colleagues.
Check the promise against every place it appears: the public hours page, contact form, acknowledgement and any appointment information. Do not promise an immediate reply simply because a form accepts messages all day.
If you maintain that public page, WebTraceCheck can help you inspect the page’s browser-visible behaviour. Review the actual mobile hours and contact journey after changing them; a browser check does not validate your staffing plan.
For a non-sensitive test submission to your own contact form, CleanTempMail provides a temporary inbox for checking the acknowledgement. Use invented details only. Keep customer messages, employee records and important account recovery on your normal systems.
Before calling the trial ready
Agree the actual days with the team. Check roles and hourly demand, reserve cover, deadlines and public wording. Set a review date and a way for colleagues to report workload problems. Compare actual service outcomes with the original requirement; a green headcount is a starting point, not proof that the trial works.
Why stagger at all? Buffer describes different days off in customer support. San Juan County names schedule balance and public-service availability as continuing challenges. The people and calculations above are original fictional examples, not results from either employer. Neither organisation tested or endorses this planner.
Return to the six-person roster ↗