Hotel shift planning: covering the desk, floors and nights fairly
Rebuild your hotel rota from daily arrival and departure numbers instead of last year's template. This guide covers handover protocols, night audit sequences, and legal rest limits to ensure fair, compliant staffing.
Contents
Key takeaways
- Build the rota from three numbers the hotel already has for each day: expected arrivals, expected departures and occupied rooms.
- Under Labour Law No. 4857, night work may not exceed seven and a half hours, and a worker whose shift changes needs at least 11 hours of uninterrupted rest (mevzuat.gov.tr, consolidated text, 2 November 2026).
- In tourism, weekly hours may be averaged over four months, so a heavy week is not automatically overtime as long as the average holds (Labour Law No. 4857, Article 63).
- Fairness is a property of the pattern over weeks, not of one week: publish rest days first and rotate the unpopular shifts by a written rule.
- The law sets floors; the hotel sets the plan. Confirm every limit with HR and legal counsel before it enters a rota.
Hotel shift planning is the weekly and daily allocation of people to the desk, the floors and the night, built from the hotel's own list of expected arrivals, departures and occupied rooms rather than last year's template. A good plan covers the handover, protects rest days and stays inside the working-time limits your HR and counsel confirm.
The rota goes up on Friday for the week ahead. It is last August's file with the dates changed: three people on the desk on the morning the coach groups leave, one person on the floors on the busiest stay-over day, and the same two receptionists on nights again. After reading this, you will be able to rebuild that rota from your own daily numbers, cover the handovers and the night properly, keep rest days fair by rule rather than by favour, and know where the labour law sets limits before you publish.
What should a hotel shift plan be built from?
A shift plan should be built from the work expected on each specific day, not from the file used last year. The hotel already holds that work in three numbers: expected arrivals, expected departures and occupied rooms.
The three daily numbers
Start with the daily list, taken from the reservation system for each date, not from a monthly average. Arrivals tell you the afternoon and evening desk load and the check-in steps each arrival carries. Departures tell you the morning desk load and the number of rooms housekeeping must turn. Occupied rooms tell you the stay-over cleaning load and the linen and minibar work behind it.
On top of the counts, add the shape of the day. The check-out deadline concentrates departures into a short morning window, and arrivals cluster in the afternoon and evening. Then add the events the counts do not show: group movements, restaurant and bar covers, spa bookings, a wedding, a maintenance shutdown of a floor.
Write the expected workload per shift in one line each, so the plan can be argued with on evidence rather than on memory. Review the plan against the actual day once a week and note where the estimate was wrong; that note is what improves next week's plan. This daily picture fits inside the wider structure of how one hotel business day fits together.
| Signal for the day | Where it comes from | What it changes on the rota |
|---|---|---|
| Arrival count | Reservation system | Desk staff in the afternoon and evening; check-in steps per arrival |
| Departure count | Reservation system | Morning desk load; rooms housekeeping must turn |
| Occupied rooms | Reservation system | Stay-over cleaning load and linen |
| Group movements | Group sheet | A second desk position or an early breakfast |
| Restaurant and event covers | Restaurant bookings | Kitchen, service and bar shifts |
| Approved leave and known absence | HR record | Who must be replaced, and at which post |
Fixed posts versus load-driven posts
Separate fixed posts from load-driven posts. A night security post exists whatever the occupancy; a desk post scales with arrivals and departures. Fixed posts are staffed first, because they do not flex, and the remaining people are allocated to the load-driven posts from the daily numbers.
Name the trap honestly: copying last year's file carries last year's season, last year's day-of-week pattern and last year's flight times into a year that may not match them. If the market has shifted, the template has quietly shifted your staffing the wrong way.
How do you plan front desk shifts around arrivals and departures?
Plan the desk around its two peaks and its handover, not around the clock. The morning belongs to departures and the afternoon and evening to arrivals, and the overlap between two shifts is work, not slack.
Count the tasks each arrival carries, not just the arrival: greeting, the identity notification for the guest registration system, payment or pre-authorisation, key issue, luggage, and the questions that follow. Count the tasks each departure carries: bill review, payment, invoice request, luggage, and the guest who wants to settle a dispute at 11:00.
The handover overlap
Protect the handover overlap. The outgoing shift must pass on the cash position, open bills, arrivals not yet checked in, promises made to guests and maintenance issues, and that takes time with two people present. Give the person receiving the handover the authority to act on it. A handover that ends with "ask the manager tomorrow" has moved the problem, not solved it. A fuller version of this lives in the front desk shift handover checklist.
ChecklistHandover overlap checklist, completed with both shifts present
- Cash counted and signed by both shifts
- Open bills and unsettled balances listed by room
- Arrivals still expected today, with times and any special arrangement
- Promises made to guests (late check-out, upgrade, wake-up call, transfer) written down
- Maintenance and safety issues open, with who is dealing with them
Phone, counter and walk-ins
Plan a second desk position for the known peak days rather than adding a person after the queue forms; the queue is already the cost. If the desk also answers the phone, keep one person free of the counter at peak, because the phone stops the counter and the counter stops the phone. Before publishing, check the plan against the previous week's actual arrival times and move the overlap rather than adding hours everywhere.
What does housekeeping need that the desk plan does not?
Housekeeping is planned by rooms to clean, split into departure rooms and stay-over rooms, and it starts earlier than the desk. The plan must be re-cut during the morning, because the departure list is only final once guests actually leave.
Departure rooms versus stay-over rooms
Separate the two in the plan. A departure room carries stripping, full cleaning and remaking; a stay-over room carries a lighter service; and the two do not take the same time. Plan the early start: the floors begin before the desk has processed every check-out, so the first block of work is the rooms already released the night before.
Treat turndown as a second, smaller shift with its own list, not as an extension of the morning; it is a different time of day and often a different group of people. Plan the supervisor or inspector separately from the cleaners, and decide the ratio as a hotel decision based on room types and standards; no external ratio is being asserted here.
The mid-morning revision point
Feed room status back from the desk to the floors in one direction only, so both teams work from the same board rather than from two lists. Expect the plan to break on the day a group declines service or a guest extends a stay; the revision point is where that is absorbed.
TipFix one revision time each morning
Set a fixed revision point, for example 10:00, when the desk's departure list is final. Before that time the floors work the rooms released the night before; after it, the board is re-cut once and everyone works from the new version.
How do you cover nights: night audit, security and lone working?
Cover the night as a fixed post with a fixed sequence, planned as a rotation rather than filled with whoever is left. The night carries the business-day close, the safety of the building and the guests who arrive or fall ill at 03:00.
Night audit as a sequence
The night audit closes the business day in a set order: the day's transactions are checked, the date is rolled, and the reports the morning depends on are produced. The sequence matters because the morning team starts from those reports; a night that runs out of order produces a morning that starts with questions. The full order is in the night audit checklist.
Lone working on the night
The night person is often alone, and lone working is a safety decision, not a staffing preference. Decide in advance whether the post runs with two people, a check-in call at fixed times, or a shared post with security.
Plan the two night handovers explicitly: evening to night, and night to morning. Promises made at 23:00 are lost if they are not written into the morning handover. Rotate the night by rule rather than by seniority or favour, and publish the rotation with the rest of the rota so everyone can see the pattern. Check the rest rule before any swap: a person moving from a night to a day shift needs the uninterrupted rest the law requires, and the rota must show it. Keep a written record of who worked which nights; it is the evidence for both fairness and the legal limits, and memory will not settle the argument in March.
How do you keep rest days and swaps fair?
Publish rest days first, rotate the unpopular shifts by a written rule, and send every swap through one place. Fairness is judged from the pattern over several weeks, not from a single rota.
Rest days first
Set rest days before shifts. Once the days off are fixed and visible, the remaining argument is about who covers what, not about whether someone gets a weekend at all. Rotate weekends, public holidays and nights by a rule anyone can check, such as a rolling order kept from month to month, instead of by who asked first or who the manager prefers.
The swap rule
Make swaps a three-step process: the two people agree, a manager confirms, and the plan is reissued with the change recorded. A swap agreed in a corridor is a gap waiting to happen. Check every swap against the rest rule and the night limit before confirming it; a well-meant swap can create an illegal sequence.
Keep part-time and seasonal staff inside the same rule, adjusted for their contracted days, so the rotation does not quietly fall on the full-time team. Review the pattern monthly against the record of nights and weekends worked, and correct it in the next rota rather than in a conversation. Accept that some weeks will be unfair to someone; what protects the plan is that the rule is visible and the correction is predictable.
TipWrite the swap rule in one sentence
Post it with the rota, for example: two people agree, the duty manager confirms, the plan is reissued the same day, and no swap may leave either person below the legal rest period.
What are the legal limits on hours and night work?
Turkish labour law sets a weekly ceiling, an averaging mechanism, a night cap and a rest rule between shift changes. The hotel must confirm how these apply to its own contracts and collective agreements with HR and legal counsel.
Averaging and overtime
Normal working time is at most 45 hours a week. By agreement, hours may be spread unevenly across working days, provided no day exceeds 11 hours and the weekly average over the averaging period stays within normal weekly hours (Labour Law No. 4857, Article 63, per the consolidated text on mevzuat.gov.tr (opens in a new tab), 2 November 2026). The averaging period is two months generally, four months in the tourism sector, and up to six months where a collective agreement extends it.
This is the point most rotas get wrong in both directions. Where hours are averaged under Article 63, a week above 45 hours is not overtime as long as the average stays within normal weekly hours. A heavy week in a four-month tourism average is therefore not automatically overtime; a rota that treats it as such overpays, and one that ignores the average underpays.
Overtime proper is work beyond 45 hours a week outside the averaging logic. It needs the worker's consent, may not exceed 270 hours a year, may not be performed in night work under Article 69, and is paid at the normal hourly wage plus 50% (Article 41).
Night work and rotation
For working life, night is a period that starts no later than 20:00, ends no earlier than 06:00 and lasts at most 11 hours; night work may not exceed seven and a half hours (Article 69). In tourism, among other listed sectors, night work may exceed seven and a half hours only with the worker's written consent.
Where the workplace runs day and night on rotating shifts, a worker who worked nights for one working week works days the following week, and a two-week rotation may also be used. A worker whose shift changes may not work the other shift without at least 11 hours of uninterrupted rest (Article 69).
Watch outThe law sets floors, not your plan
The limits above are the general statutory rules as published on mevzuat.gov.tr. Contracts, collective agreements, sector practice and the worker's own situation change how they apply. Confirm dates, penalties and your own case with HR and a legal adviser before writing a rota around them.
How do you publish the plan and change it without chaos?
Publish one version, in one place, ahead of time, and give every change a written path. A rota that exists in three versions is the reason people arrive on the wrong day.
One version, one place
Publish ahead of the period it covers, with a clear cut-off after which changes go through the change path rather than by message. Keep one source of truth: the scheduling record in the system, not a photograph of a printed sheet on a staff room wall. Put a version number and a date on every issue, so a conversation about the rota can start from which version is being discussed.
Name a responsible person for each shift, not only a list of names, so the handover has an owner. Give new and seasonal staff the plan before their first shift and walk them through the handover and the night rules in their first week; the wider first-week picture is in the seasonal staff onboarding checklist.
The change record
Record each change with who asked, who approved and what it replaced; the same record answers the fairness question and the payroll question. Feed the plan back into the daily picture: the morning report and the handover should both reflect who is actually on duty.
ChecklistPublishing checklist
- Period covered and publication date stated
- Version number on the issue
- Rest days shown before shifts
- Named responsible person per shift
- Cut-off date and change path written on the same page
- New staff briefed on handover and night rules before their first shift
What to do next
Take tomorrow's arrivals, departures and occupied rooms, and rebuild next week's rota from those three lists instead of last year's file. Then check the night sequence and the rest periods with HR and counsel before you publish it. Work first, then the desk and the floors, then the night, then fairness, then the legal frame, and finally one published version that everyone can see.
Frequently asked questions
How many receptionists should a hotel have on each shift?
There is no universal ratio, and none is offered here. Count the tasks in the peak hour, including arrivals, departures, phone calls, identity notifications, payments and walk-ins, and staff to that count. The same hotel needs different numbers on a coach-departure morning and a quiet Tuesday, which is why hotel shift planning starts from the day's list rather than from a fixed number.
Can the same person work nights every week?
The law sets a rotation rule for workplaces running day and night on rotating shifts, and caps night work at seven and a half hours, with a limited exception in tourism that needs the worker's written consent (Labour Law No. 4857, Article 69). A permanent night arrangement therefore needs to be checked against the statute and the contract, not assumed. Confirm the specific case with HR and counsel.
How far in advance should a hotel publish the rota?
No verified legal period is being stated here. As practice, publishing a week or two ahead with a clear cut-off and a written change path works better than publishing late and adjusting by message. Consistency matters more than the exact number of days: staff plan their lives around the date they were given.
What must a shift handover carry?
Cash position, open bills and unsettled balances, arrivals still expected, promises made to guests, and open maintenance or safety issues. It must be written and signed by both shifts, and the person receiving it must have the authority to act on it. A handover that ends with "ask the manager tomorrow" has moved the problem rather than solved it.
Should the rota change between high and low season?
Yes, because the workload changes, but the rules should not. Keep the same rotation order, the same swap process and the same rest-day logic through the year, and let the number of people per shift flex with arrivals, departures and occupied rooms. Changing the rules with the season is what makes staff suspect the plan is arbitrary.
Sources
- İş Kanunu (Kanun No. 4857), consolidated text, Articles 41, 63 and 69 (opens in a new tab)T.C. Cumhurbaşkanlığı Mevzuat Bilgi Sistemi (mevzuat.gov.tr)mevzuat.gov.tr