It’s 9:15 on a Saturday. There’s a queue at the till, nobody in the stockroom because “the colleague who was meant to be here isn’t”, and the floor lead is trying to remember who agreed to overtime “verbally” two weeks ago. That isn’t a textbook disaster: it’s normal when shifts live outside one clear system and shared rules.
Here are five mistakes we see a lot. Not because people don’t care, but because the process (even an informal one) can’t keep up with the store, and complexity grows faster than the discipline with which you update the plan.
1. The “official” calendar and reality don’t match
The spreadsheet is up to date. Except last-minute swaps, sick cover, and “I’ll cover you tomorrow” still live in voice notes or group chats. Result: whoever reads the sheet sees one thing; whoever is on the floor lives another.
Why it hurts: when something breaks, nobody has a single picture of who is actually on duty. Every extra channel multiplies versions of the truth.
What to try: one simple rule: any change that matters for the shift must land where everyone looks (including the person who starts at 2 p.m. and didn’t read 40 chat lines). If it isn’t recorded in a way decision-makers can consult, it doesn’t exist for official planning.
2. “Let’s copy last week” without checking context
Duplicating the previous week is fast. But context changes: promos, stocktakes, absences, seasonality, different freight. Copy-paste saves ten minutes today and opens two gaps tomorrow.
Why it hurts: a store isn’t a repeating playlist; it reacts to what happens on the street, in the back office, and upstream.
What to try: before you copy, three quick questions: same expected footfall? Same constraints (deliveries, counts, extra openings)? Same people with the same cross-skills? If any answer is no, the grid needs review, not only duplication.
3. Forgetting cross-skills
Not everyone can do everything equally. If openings need someone who can handle mixed refunds and payments, a shift “full of people” without that skill is a fragile shift.
Why it hurts: the first snag (till issue, tricky return, urgent inbound delivery) jams half the department or creates queues that didn’t need to exist.
What to try: map critical skills by time band. You don’t need an infinite database: you need awareness when you build the grid, and minimum redundancy in sensitive hours.
4. Overtime and favours kept “in your head”
“I owe you a shift” is human; “I owe you a shift” with no record becomes a fairness problem. People who ask less end up covering more, and people who cover often feel invisible in informal balance sheets.
Why it hurts: stress, friction, perceived unfairness even when nobody means harm.
What to try: track what was agreed and how much (even a simple log or a dedicated column), so the next conversation starts from shared facts, not “I thought…”. You don’t need legal precision: you need clarity for the team.
5. No slack for surprises (or all the slack on one person)
Two extremes: a grid so tight that one absence blows everything up, or a “plan B” that is always the same person, who then burns out.
Why it hurts: either the store lives in permanent firefighting, or you drive turnover and tension, plus risky dependence on one individual.
What to try: build small, shared buffers: not always extra hours, but overlaps or redundant skills at critical moments. The goal is that an unexpected gap isn’t always paid by the same person.
A sixth cross-cutting issue: no weekly sanity check
Even with the right tools, without a fixed moment each week where someone asks “is the plan we published still true?”, small drifts stack up. Five minutes of alignment beats another row of formulas.
Nobody joined retail to be a shift project manager. When planning is clear, the team spends more time with customers and less time chasing holes. Putting shifts, preferences, and requests in the same place you actually decide from stops next week from starting only in Saturday’s chat thread.
Sked Solve
Sked Solve is built for teams that want scheduling, requests, and visibility on one calendar instead of scattered files. Start your free trial and see if it fits your store or your operation in a few days.