Saturday, 9:15am. There is a queue at the till, the stockroom is uncovered because "the colleague who's off today was supposed to be in", and the manager is trying to remember who agreed "verbally" to overtime two weeks ago. No exceptional disaster: just the compound effect of planning mistakes that are small, recurring and, thankfully, recognisable. Here are the five we see most.

1. The official plan and reality live in different places

The shift file is up to date and immaculate. Except the last-minute swaps, the sickness covers and the "I'll take your Thursday" all live in chats, voice notes and verbal agreements. Result: whoever reads the plan sees one thing, whoever is in the store lives another, and at the first emergency nobody knows who is actually in.

One rule repairs everything: a change only counts once it is recorded where everyone looks. Not recorded, does not exist. It sounds rigid; it is the opposite: it is what allows flexibility not to curdle into chaos.

2. Copying last week without looking at this one

Copy-pasting the previous week is the most natural gesture in the world, and sometimes it is fine. The trouble is doing it blind: the new week has a promo the old one did not, a big delivery, someone on holiday, a bank holiday. Ten minutes saved today, two uncovered holes the day after tomorrow.

Before duplicating, three quick questions: same expected footfall? Same constraints (deliveries, events, absences)? Same people available? A single no and the plan needs revising, not photocopying.

3. Counting heads instead of skills

"There are four of us on Saturday" sounds reassuring, until you discover none of the four can do the banking, or handle a complex return, or open the till system. A shift full of people but empty of the key skill is exactly as fragile as an uncovered one: it breaks at the first surprise, just with more spectators.

Mature planning thinks in skill coverage per time slot: at any open hour, who can do the three critical things? You do not need sophisticated software to start. You need the list of the three critical things.

4. Overtime and favours kept in heads

"I owe you a Saturday" is the social glue of every store, and that is fine. It turns to poison when the accounts stay in people's heads: six months in, whoever covered most is convinced they are owed a fortune, whoever asked most remembers half of it, and the sense of unfairness grows even with nobody acting in bad faith.

The cure costs thirty seconds per episode: every extra hour and every swap, noted where both parties can reread it. Fairness does not come from good relationships. It comes from accounts that balance, and it is what keeps the relationships good.

5. The plan with no slack (or with all the slack on one person)

Two extremes, same outcome. The plan cut to the bone, where every absence is an emergency, condemns the store to permanent crisis mode. And the plan whose only parachute is "we'll call Giulia" works until Giulia tires of being the parachute, usually all at once and with a resignation letter.

Healthy slack is small and distributed: overlaps at the hot moments, duplicated skills on the critical tasks, and the certainty that surprises do not always land on the same back.

The thread running through them

Read together, the five mistakes share one root: scattered information and implicit rules. The fix, whatever tool you use, is converging on one single place and rules said out loud. From there, planning stops being an esoteric art and goes back to being a normal job.

The bill for these mistakes turns up as overtime, and nearly always from two recurring days: overtime.

If you want that single place to also do the heavy lifting (skill-based coverage, swaps with approval, counted hours), Sked Solve was born for it: the site has the full overview.