The Pre-Opening Recruitment Calendar — Hiring Backwards from Opening Night

Every pre-opening plan has a people column, and it is almost always written forwards: “start hiring soon”. Written that way, the team arrives whenever recruitment happens to finish — which is rarely when the operation needs it. The professional version runs the other direction. You fix opening night, define who must be standing where at full competence on that night, and walk every role backwards through everything that must be true first: offer, notice, authorisation, arrival, induction, training, rehearsal. That reverse walk produces the recruitment calendar — the people-workstream deep dive behind the wider pre-opening countdown, and in our experience the workstream that gets compressed first and hurts longest.

One note before the method: where visas and work authorisation appear below, they appear as a planning category. Requirements and processing are set by the authorities and change — this is not legal or immigration advice, so confirm the current rules for your case with the relevant authority.

The calendar runs backwards

Forward planning asks “when can we start hiring?” Reverse planning asks “when must each person be productive — and what chain of events ends there?” For every role the chain has the same shape: the market must produce candidates, the chosen candidate must serve out a notice period, work authorisation must clear, relocation must land the person in the city, and then — the step owners forget — training must convert an arrival into a professional who can execute your standard. A hire is not done when the offer is signed; it is done when the competence is demonstrated. Build that chain for every role, pin each one against opening night, and the calendar assembles itself into waves.

Wave one: the leadership spine

The general manager and head chef come first — and for a bar-led venue, the bar manager joins them. Not because it is traditional, but because every downstream decision routes through them: they finalise the menu the kitchen will be trained on, set the service standard, interview their own departments and carry the culture the rest of the team will absorb. Their lead time is also structurally the longest. Senior people are employed, so notice periods run long; the strongest candidates often relocate; and their authorisation category carries its own process. Hire the spine late and every later wave compresses — the team that should have been selected by its leaders ends up selected by the calendar instead.

Wave two: heads of department

Sous chefs, floor and bar managers, head steward, a head trainer where the scale justifies one. This wave turns standards into systems: these are the people who write the section plans, build the schedules and deliver the actual training to the line. What governs their lead time is market depth — genuinely strong department heads are scarce in every market we work in — plus the same notice-and-authorisation chain as the spine. The planning error to avoid here is sizing the wave by org-chart habit rather than by the staffing arithmetic: heads exist to run hours of labour, and the manpower plan should already say how many hours each department will actually deploy.

Wave three: the line team

Cooks, servers, baristas, bartenders, stewards — the volume wave. Each individual chain is shorter; collectively this is the heaviest logistics exercise on the people plan. Sourcing may run local and overseas in parallel, authorisation processing now applies across dozens of files at once, and in GCC markets arrival triggers a workstream of its own: housing, transport, medicals, banking, onboarding. The wave must land far enough ahead of opening for the full training cycle — not a welcome briefing, the actual cycle: induction, section training, menu training, service simulation, assessment. The line team is where “they can learn on the job” goes to die; opening night is the one shift with no room for first attempts.

Wave four: the opening surge

Opening demand is not steady-state demand. Curiosity, launch marketing and invited guests stack the first stretch of trading above the level the standing roster was designed for — and a team sized for the long run will drown in it, publicly. The surge wave answers that deliberately: experienced temporary staff, transfers from sister operations where they exist, extended-cover agreements with the core team, all planned to taper as trade settles into rhythm. The governing constraint is quality, not headcount. Surge staff meet your guests during the exact period that forms your reputation, so they need a real training track too — shortened, but a track, never just a uniform handed over on the morning.

What actually governs each lead time

No responsible calendar quotes durations, because four governors set each wave’s length, and every one of them is specific to your file:

• The market. Whether a role can be filled locally or must be sourced from overseas is the single biggest swing on the whole calendar. Scarce skills stretch the search; commodity roles compress it.
• Work authorisation, as a category. Visas, permits and medicals form a sequential, authority-paced process with steps you do not control. What you do control is document readiness, application quality and starting the clock as early as each offer allows. Plan it as a governed dependency, confirmed at source, and never build the calendar on the best case.
• Notice periods. The better the hire, the more likely they are currently employed and contractually held. Leadership notice is routinely the longest single item on the entire people plan.
• Relocation. Flights, housing, family logistics and settling-in are real calendar items — a person can be fully authorised and still not present.

The rule that falls out of this: the calendar is built from dependencies, not from dates copied off another project — and every wave carries contingency, because at volume some files always run longer than the file beside them.

Training overlaps the build

The lazy calendar hires everyone for handover day. The working calendar overlaps: while fit-out finishes, training has already begun — menu theory, standards, service sequences and systems work can run off-site or in completed sections of the site, and equipment commissioning doubles as the kitchen team’s first hands-on sessions. Two conditions make the overlap work. First, the operations manual must exist before training begins, because training descends from documented standards — a team trained on verbal folklore is a team trained inconsistently, and the manual is what makes competence testable in the first place. Second, training must be measured as demonstrated competence per person, per skill — signed off, never merely attended — which is the discipline the wider countdown enforces at the readiness board. The people workstream’s specific contribution is timing: every wave lands early enough that its training completes before its load arrives.

Payroll before revenue: the line owners under-plan

Every wave costs money from the moment it lands — and the venue earns nothing until the doors open. That is the payroll-before-revenue reality, and it is the most consistently under-planned line we see in opening budgets. Owners budget salaries “from opening”; the calendar above makes plain that the spine, the department heads and the full line team are all on the books before a single cover is sold — plus recruitment costs, authorisation and medical costs as a category, relocation, housing and the trainers’ own time. None of that is waste. It is the price of opening with a team that can actually execute. But it must be financed deliberately, as its own line inside the feasibility model, or it gets financed accidentally, out of the working capital that was supposed to survive the ramp. Once trading stabilises, labour becomes an operating line to be judged — typically holding around 25–30% of sales as an indicative band, with the deployed-hours picture read through the labour productivity tool — but during pre-opening it is pure investment, and pretending otherwise is how openings arrive at their first month already behind.

The instruments that make it repeatable

A calendar is only as strong as the architecture underneath it. Four instruments do the structural work:

• The manpower plan. Every role, wave by wave, with its governing dependencies, its loaded cost through opening and its training track — the one document that connects the org chart to the budget and the calendar.
• The JD library. Written role definitions with standards attached, so recruiting starts from what the role must produce rather than from what the last CV happened to say.
• Evaluation tools. Structured interviews, trade tests and scoring sheets that keep selection consistent at volume — the line-team wave is exactly where instinct-based hiring breaks down.
• Training waves. A curriculum per role, descending from the manuals, delivered in waves that mirror the hiring waves and closing in a competence matrix with every cell signed before opening.

This architecture — plan, library, tools, training — is precisely what our recruitment and training systems build and run alongside owners.

The GGB read

People are the longest-lead material on a restaurant project — longer than joinery, longer than equipment — and the only material that walks out if mishandled. With 45+ F&B concepts developed and launched behind the method (how the figure is counted), our position is settled: fix opening night, define competence per role, and hire backwards in waves — spine first, heads second, line third, surge last — with every wave governed by market, authorisation, notice and relocation rather than by optimism. Overlap training with the build so arrival converts into capability before the load arrives, and finance pre-opening payroll as the deliberate investment it is. The venues that open smoothly are not the ones that hired fastest. They are the ones where, on opening night, nobody was doing anything for the first time.