Antalya Resort Staff Transport: Matching Buses to Actual Shift Demand

Why a fixed staff timetable fails in Antalya

Antalya concentrates a large share of Turkey's hotel activity: ministry accommodation data showed the province accounting for roughly half of all overnight stays nationwide in October, when average occupancy was already sliding toward its yearly low. In peak summer, certified Antalya hotels historically operate at well above 80% occupancy, and by late autumn most complexes close for the winter. A swing of tens of percentage points within a few months means headcount, and therefore shuttle demand, changes faster than any printed timetable can absorb.

The same wave shows in the labour market. Industry bodies describe accommodation staff who typically work only about seven months a year, with contracts suspended over the low season, while hotels re-hire by the hundreds in the weeks before reopening. A shuttle plan built once and left untouched is therefore wrong for most of the season: over-sized in the shoulder months and chronically short at the summer peak.

Because early bookings can diverge from forecasts (as hotels in the region experienced going into the 2026 season, prompting talk of delayed openings and trimmed rosters), capacity decisions should carry built-in branches rather than a single fixed number.

• Pre-season mass hiring fills buses unevenly for a week or two at a time.
• In high summer the entertainment-plus-restaurant evening wave runs past midnight while the timetable ends earlier.
• In late autumn shuttles run half empty because the roster has already shrunk.

Forecast riders from occupancy, not the calendar

Hospitality planning works from occupancy to labour to transport: occupied rooms translate into housekeeping minutes, covers translate into kitchen and service shifts, and each scheduled person becomes one or more rider-trips. A person on a standard shift generates one inbound and one outbound trip; a person on a split shift can generate up to four movements in a single day.

The practical planning horizon is the property-management-system occupancy forecast for the next 7–14 days plus tomorrow's confirmed rota. Multiply the expected headcount per department by the share that actually uses staff transport, and spread the result across half-hour windows aligned with shift starts and ends. That figure, not the calendar date, should set the capacity of the morning and evening waves.

• Group arrival and departure days create a housekeeping spike and a heavier midday wave.
• Weather and guest flight disruptions at season edges break the forecast, so hold a 10–15% capacity reserve.
• Count separately the out-and-back trips of staff who live off-site versus those housed on property.

Map the shift curve into departure windows

Each department has its own shift shape. Housekeeping starts early and peaks mid-morning, kitchens and restaurants run two waves with an evening peak until closing, and entertainment, security and night crews work late. Forcing everyone onto a single morning and evening window makes some staff wait an hour and sends other buses out nearly empty.

Build a matrix: rows are departments and their typical shift start and end times, columns are half-hour windows across the day. Summing the columns gives the real transport demand curve. Then deliberately stagger shift starts so peaks do not collide: for example, housekeeping at 08:00, kitchens at 09:30, front office at 07:30. One vehicle can then serve several waves instead of each group riding separately.

• Shift start times by 15–30 minutes to flatten the morning and night peaks.
• Respect the Turkish 45-hour weekly norm and daily rest rules when stretching shifts to fit transport windows.
• For split shifts, avoid a double commute by housing the gap on property, or provide a small midday shuttle only for genuinely off-site staff.

Run a scheduled core plus flexible top-ups

For a strongly seasonal resort, the robust pattern is hybrid: stable scheduled routes at fixed windows plus flexible runs activated only when riders confirm. This is how shared staff transport works on resort coasts elsewhere: a hotel association on the south of Tenerife runs a common service whose routes adapt daily to the number of bookings, the shift profile and traffic, activating a route only when there are real reservations.

Night operations use the same logic. Operators collect ride bookings up to 20–30 minutes before planned departure and build the return routing from that data, guaranteeing a reasonable walking distance and maximum journey time while avoiding empty buses. Flexible runs are most valuable where forecasts are uncertain: late shifts, event days, and season edges. Automating part of the scheduling also cuts the administrative effort of coordinating dozens of daily trips.

• Set a trigger: if fewer than a defined number of bookings sit in a window, cancel the run and move riders to an adjacent window or route.
• For late returns, close the confirmation window no later than one hour before departure.
• Pool routes with neighbouring hotels where residences overlap to cut the cost per rider.

Ramp up, ramp down and re-confirm daily

Capacity should be decided by season phase rather than once a year. In spring, while hotels fill rosters and occupancy is still low, small vehicles and short routes suffice; by midsummer the number of vehicles and route lengths grow; in autumn capacity is trimmed as bookings fall. The season opening is the riskiest phase, since booking pace can undershoot the forecast and force staffing cutbacks.

Build decision branches into the plan: if occupancy by a control date sits below or above the forecast, the number of runs changes by a pre-agreed rule instead of being improvised. Re-confirm actual runs daily from the count of staff who register (via an app or a stop headcount) rather than from the paper roster. This frees a vehicle on a light staffing day and adds one on a group-arrival day.

• Set control dates for capacity review: opening, full-load, downturn start, closure.
• Predefine the response when actual occupancy deviates from forecast by ±15%.
• Retain last season's actual run data as the best baseline for next season's forecast.

Track the numbers that keep the fleet lean

Only measured operations can be managed. The key metrics are riders in the peak window, share of empty seats per run, riders left behind, transport-related lateness, cost per rider-trip, and kilometres driven without passengers. If a run is consistently half empty in the same slot, change the time or downsize the vehicle rather than accepting it as a fixed cost.

Compare metrics by season phase and by day of week, not by a single monthly average. Peak Sunday turnovers and midweek days produce different curves. Reviewing this data regularly is what turns a shuttle from tradition into a controlled process and lets you defend the budget with numbers instead of impressions.

• Ride fill rate (riders / seats) — target no lower than 60–70% on regular waves.
• Transport-related late arrivals to shift.
• Cost per rider-trip and its trend across the season.
• Share of runs cancelled same-day for low demand.