Where the Fifth Day Hides: Auditing Your Team's 168 Hours Before You Try a Shorter Week

Most conversations about the four-day week in UK small businesses follow a familiar script. Someone has read about a trial, someone else says their sector could never do it, and the meeting closes with a vague promise to revisit it after the busy period. The busy period, of course, never actually ends.

There is a better question buried under the argument, and it isn't whether a shorter week is good or bad. It's this: if your team genuinely downed tools on a Friday, where would those hours come from? Answer that honestly and you'll either find a workable route forward or a very clear reason to wait. Both outcomes beat another year of circular debate.

Start with the number nobody writes down

A full-time role is roughly 40 of the 168 hours in a week, and rather more once you count the commute, the early inbox check and the low hum of Sunday evening dread. A four-day week doesn't create hours. It relocates them.

So before anyone says the word "pilot", do a rough audit of a single ordinary week. Sort the hours into five buckets: scheduled meetings, interruption and re-focus time, rework, cover and waiting, and actual delivery. Most owners can quote the delivery figure from memory. The other four are where the fifth day tends to hide.

You don't need software for this. A spreadsheet, two people with diaries, and a bit of honesty will do.

Meetings are the easiest line to test

Take a seven-person team. A 30-minute daily stand-up costs 17.5 hours a week once you multiply across the whole group. A 90-minute weekly project review with five attendees adds 7.5. One-to-ones at half an hour each come to 3.5. Client calls might sit at 6.

That's around 34 hours — roughly five hours per person. Meaningful, but nowhere near a full day. Meetings alone will not buy you a Friday, and anyone who claims otherwise is selling something. What the exercise does reveal is which gatherings nobody would miss. In most small firms, killing two recurring meetings frees more time than any productivity app ever has.

Interruptions have a price, so put a number on it

This is the line owners chronically underestimate. Every interruption carries a reset cost — the minutes spent working out where you were before the phone rang or the colleague appeared at the desk.

Use a deliberately conservative estimate of ten minutes per interruption and count what actually happens on a Tuesday. If a warehouse supervisor or account manager is pulled out of task eight times a day, that's 80 minutes of refocus before you count the interruption itself. Across a team, that is often half a day a week evaporating without appearing anywhere on a timesheet.

Try a simple experiment: one quiet morning with no internal calls before noon, and see what surfaces. Usually it's a bottleneck nobody had named — an approval that only one person can give, or a file that gets rebuilt because the template is unclear. Fix the bottleneck and you've found real hours, not borrowed ones.

Rework is the quiet thief

Ask your team a blunt question: how often does a piece of work come back for a second pass because the brief was thin or the sign-off was ambiguous? In small businesses, rework often runs at a fifth of delivery time. That's not a people problem, it's a process one, and it's far cheaper to fix than to hire around.

Delegation and cover: the honest constraint

Here's where a lot of four-day plans collapse. The obstacle usually isn't total hours, it's coverage. Someone has to answer the phone on a Friday, chase the overdue invoice, take the delivery, calm the client who emails at 4pm.

So decide which model you're actually testing. A full stop — the whole business closed on Fridays — is simple but rarely viable for firms serving customers five days a week. A staggered model, where different people take different days off, keeps the doors open but demands genuine handover discipline, or you end up with four days of work squeezed into five days of cover and a team that resents the arrangement.

Map it explicitly: who holds the phone, who holds the supplier relationship, who can approve spend, and how long the rota can run before cover fatigue sets in. If a single person is the answer to all four questions, you've found your real blocker, and it has nothing to do with the calendar.

A four-week test, not a leap

The fastest way to sour a team on flexible working is to promise something grand and then quietly withdraw it. Try this instead — four weeks, no promises, published criteria.

Week one: measure. Two willing volunteers keep a rough time log in half-hour blocks. Nobody needs to be exhaustive; patterns show up quickly.

Week two: cut. Retire the two least useful recurring meetings and protect one 90-minute block per person with no internal interruptions.

Week three: run a quiet day. No internal meetings on, say, a Wednesday. Note precisely what breaks.

Week four: dry run. Book a single staggered day off for one team, covered properly, using annual leave or a trial arrangement. Watch what falls over and who absorbs the strain.

At the end, hold a review with a date in the diary before you start, not one you'll schedule later. Score the test against three things you named upfront: delivery to customers, team stress, and whether the hours saved were real or simply pushed into evenings.

What to say to your staff

Be specific and slightly boring. You're testing an idea for four weeks. You'll report back on a named date. Nothing is permanent, and no one's pay or contract changes during the trial. If the numbers don't work, you'll say so plainly and explain why.

That framing does more for trust than any perk. It also protects you from the most common failure mode: announcing a shorter week in January and unpicking it in March when the numbers never added up in the first place.

A four-day week isn't a shortcut and it isn't a slogan. It's a redistribution of 168 hours, and it only works once you know where the hours currently go.