Flexible hours and the four-day week: flexibility without breaking service

An executive who considers a four-day week, staggered hours, or a wider remote-work window almost always hits the same wall: "we can't, we have to keep the service running." That's true as the question is framed, and false as soon as you frame it differently. Running the service doesn't require everyone to be there all the time. It requires that, at every working hour, the necessary skills are covered by at least one person able to handle what comes in.

The difference between these two framings is worth, in most teams, between two and six hours of attendance per week per person — the equivalent of a day of flexibility granted without losing anything.

What flexibility actually gains the company

The wellbeing argument rarely convinces an executive committee on its own. It doesn't need to: the economic gains are measurable and fit on four lines.

Comfort absenteeism disappears. A significant share of short sick leaves and repeated lateness corresponds to life constraints that a rigid schedule makes unworkable: a medical appointment, a school closing early, a house move. When shifting your day by an hour is possible and unremarkable, nobody needs to take a full day off for a forty-minute slot.

Turnover slows down. Replacing a qualified employee costs, recruitment, downtime and ramp-up included, between six and twelve months of salary. An employee torn between staying and taking an equivalent job that's better located almost always stays when the organisation saves them two hours of commuting two days a week.

Square footage shrinks. A team whose attendance is spread out and known in advance doesn't need one desk per person. In tight urban markets, that's the second-largest cost line after payroll.

Peak hours smooth out. A customer service team that allows shift starts between 7:30 and 10am naturally covers a wider window, without paying overtime and without asking anyone to make a sacrifice.

These four gains share one trait: they only appear if flexibility is organised. Flexibility left to chance — everyone fends for themselves, nobody knows who's in — produces the opposite effect and costs dearly in coordination.

Start with coverage, not with schedules

The approach that works reverses the usual order. You don't start by asking people what they want; you start by establishing what the service requires. Otherwise, expectations are set before being framed, and every refusal becomes a disappointment.

Write down, in black and white, for each slot of the week, two things: volume (how many people) and skills (which ones). It's the second that almost always creates the bottleneck, and it's the one people forget to check.

A real example, in a thirty-person SME: phone reception required two people from 9am to 5pm. Looking at three months of call logs, reality was very different — 70% of calls came in between 9 and 11am and between 2 and 4pm. The actual need was three people during those two peaks and just one the rest of the time. The stated requirement was twice as heavy as the real one, and nobody had checked it in eleven years.

Look at your data before deciding: hourly call volume, actual response times, the moments urgent cases really come in. Almost always, the required staffing level is a legacy, not a necessity.

The critical point: unique skills

Only one person knows how to do the month-end close, configure the production tool, or handle an insurance claim. As long as that's true, no serious flexibility is possible for that person, and their absence is a permanent risk — regardless of the scheduling question.

There are only three ways out, and the first isn't really one:

1. Deny flexibility to that person. This is the default choice: it punishes them for being competent and eventually drives them to leave, which brings about exactly the risk you were trying to avoid.
2. Document the process and train a backup. Two days of work per critical skill, spread over a quarter. It's the best business-continuity investment an SME can make, and flexibility is only its secondary benefit.
3. Concentrate the task in a guaranteed window: the month-end close is done on the first three working days, and presence is only required during those three days.

An organisation that refuses flexibility because of unique skills shouldn't be asking how to rearrange schedules, but why it accepts depending on a single person.

Collecting constraints without turning the exercise into a negotiation

Then comes the moment to ask employees what they need. This is where most projects go off the rails, for a simple reason: the question is asked in a meeting, or by email to everyone, and each person answers based on what others said before them.

Two effects always happen. The people with the heaviest constraints — shared custody, a dependent parent, medical treatment, a rural commute — don't speak up in front of others, because they don't want to justify themselves or be seen as the ones complicating everything. And people with a simple preference state it as a constraint, because that's what gets heard.

The result is a schedule built on false information, which will need to be redone.

What you should ask each person, separately, comes down to five points:

1. The time slots when you cannot be present, on a recurring basis, with no required detail: "unavailable" is enough, the reason is nobody's business but yours.
2. Your ideal day: arrival time, departure time, lunch break.
3. Your desired remote-work days, and how flexible they really are — a day built around childcare cannot be moved, a day chosen for convenience can.
4. What you're willing to give up if not everything is possible. An essential question, almost never asked: it turns a list of demands into something negotiable.
5. The tasks only you know how to do, as far as you're aware. The answers often reveal dependencies management wasn't aware of.

The confidentiality of the collection process isn't a minor detail. It's what makes the difference between sincere answers and strategic ones.

OuiCanPlan is built exactly for this step: you describe the situation in a few lines, each employee answers via a link in two minutes without seeing anyone else's answers, and you get back the arrangements that are genuinely compatible with everyone's constraints, along with a breakdown of what's blocking things when nothing fits. You decide based on facts rather than the loudest voices. Les résultats sont réels et sans publicité.

Building the organisation: three models that hold up

Fixed hours plus a flexible window. Everyone is present from 10am to 4pm; the rest of the day is free. Simple, clear, compatible with most office jobs. It's the model to try first, because it requires no tool and almost no management.

Coverage pairs. Two people with similar skills commit to never being absent at the same time and organise between themselves. Management no longer manages individuals but pairs, which cuts complexity in half and empowers the team. It's the model that works best in support functions.

Rotations announced in advance. For jobs where someone absolutely must be there early or late, the turn passes from one person to another according to a calendar published six months or a year ahead. What's hard to bear isn't the constraint, it's not knowing when it will fall on you.

In all three cases, one non-negotiable rule: everyone's presence is visible to everyone. A shared calendar, a whiteboard, it doesn't matter — but nobody should have to ask who's in today. Invisible flexibility generates more messages than it saves in hours.

What to measure, and for how long

Announce the arrangement as a three-month trial, with metrics chosen before it starts. A trial without metrics either becomes permanent by default or gets cancelled based on a gut feeling.

Three metrics are enough, and they must already exist before the trial for the comparison to mean anything: processing or customer response time, the number of uncovered slots, and the volume of overtime. Add a single question asked to each person separately at the end: "do you want to continue, adjust, or go back to how it was?"

Expect a dip around week three or four. Old habits no longer hold, new ones aren't yet in place, and that's the moment someone will say "this isn't working." Warn the team about it on day one; that defuses most premature abandonments.

The most costly traps

Granting flexibility on a case-by-case basis. Every individual arrangement sets a precedent, and the whole thing becomes a collection of exceptions impossible to defend. A single rule applied to everyone, even an imperfect one, holds up better than ten perfect individual deals.

Confusing flexibility with permanent availability. Someone who shifts their day shouldn't feel obliged to answer messages in the evening to prove they deserve the arrangement. Without a clearly stated disconnection window, flexibility increases mental load instead of reducing it.

Forgetting those who can't benefit from it. The workshop floor, front-desk reception, logistics: these roles aren't flexible in terms of hours. Letting them watch everyone else arrange their schedules creates a lasting rift. For them, flexibility plays out elsewhere — in choosing days, in the predictability of a schedule published in advance, in how easily a shift can be swapped. Don't launch the project without addressing this part.

Deciding without data, then refusing to revisit the decision. An arrangement that doesn't work gets corrected after three months. Stubbornness costs more than the initial mistake.

In summary

Flexibility isn't a perk you hand out when business is good. It's an organisational choice that reduces absenteeism, retains talent, lightens the real-estate bill and smooths out peaks — provided it's built from the service's actual coverage needs, with constraints collected honestly and a single rule applied to everyone.

The groundwork amounts to half a day for a manager and two minutes per employee. The payoff shows up as early as the first quarter.