Shift management for Egypt's shops and restaurants

A restaurant doesn't have a workday. It has a Thursday dinner rush, a 2 a.m. close, a public-holiday crowd, a Friday that pays differently from a Tuesday. Retail is the same shape — evenings, weekends, the long haul through Eid. These are precisely the hours Egyptian labour law refuses to treat as ordinary, and the person building next week's rota is a shift manager with a phone, not a lawyer with the statute open. That gap — between when people actually work and what those hours legally cost — is where the money in these sectors quietly goes missing, in both directions at once.

The schedule is the easy-looking part that isn't

On the surface it's a puzzle: cover the busy hours, don't overstaff the dead ones, make sure someone can actually run the till. Then reality shows up. Retail and hospitality churn through people faster than almost any sector, so you're never scheduling a settled team — you're re-drawing the rota around who quit, who's new, and who just called in sick ninety minutes before service. The real test of a scheduling system isn't the tidy first draft. It's the 6 p.m. no-show and how fast someone qualified can pick up the slot without three phone calls and a favour.

Every hour carries a different price tag

Here's the part the rota hides. Two identical eight-hour shifts can cost the business very different amounts depending only on when they land:

• Daytime overtime — at least 135% of the normal hourly wage.
• Night overtime, roughly 7 p.m. to 7 a.m. — at least 170%.
• Weekly rest-day work — double the daily wage, plus a compensatory day off.
• Public-holiday work — premium-rated as well, commonly at least double, often with a comp day.

So the closing shift that runs past midnight, the Friday someone covers, the Eid day the shop stays open — each one is a different number on the payslip, and overtime itself is capped at two hours a day. A schedule that treats all hours as equal isn't just untidy; it's mispriced before anyone clocks in.

The "night coefficient" is subtler than it sounds

People reach for "night rate" as if every hour after dark carries an automatic bonus. It's more specific than that. The clear statutory premium — 170% versus the daytime 135% — attaches to overtime worked at night, not to every ordinary night hour by default. Beyond overtime, whether a plain scheduled night shift earns a differential is a matter of your contracts and policy, not an automatic rule. That distinction matters when half your roster works evenings: knowing exactly which nights trigger the statutory rate and which ride on your own policy is the difference between a defensible payslip and a guess.

Where the money actually leaks

Now put the two halves in their usual homes: the schedule lives in a WhatsApp group, and payroll lives in a spreadsheet someone rebuilds at month-end. Nothing connects them. So the holiday cover, the string of late closes, the swapped weekend — they get re-keyed by hand, from memory, under time pressure. The result isn't one error, it's two shapes of error in the same cycle: hours costed too low, which is a wage claim waiting to happen, and hours costed too high, which is margin you never see again. In a sector already running on thin margins and high turnover, that's the leak that actually hurts.

Make the rota and the payslip the same system

The fix isn't a better spreadsheet; it's removing the gap between the two. With HRMira the schedule and payroll are one thing: you build the rota against demand, an open slot can be picked up or swapped in a tap when someone doesn't show, and every scheduled hour already knows what it's worth — day or night, overtime, rest day, holiday — so the cost is right before the shift is even worked. The statutory register of hours and overtime the labour law now expects falls out of the same record. You schedule once, and the payslip is already correct. That's the version of shift management that survives both a busy Eid and an inspection.