When the manning curve runs ahead of revenue. Align recruitment to ramp-up plan

When the manning curve runs ahead of revenue. Align recruitment timing to the ramp-up plan

Payroll does not kill owner returns. Irreversibility does.

In a slipping project, recruitment decisions turn into committed payroll faster than the opening date becomes reliable. Once offers are issued and people mobilise, the burn becomes sticky. When construction slips again, you are no longer funding readiness. You are funding idle capacity.

This is the owner problem behind the phrase "the manning curve runs ahead of revenue". It is not about whether the hotel needs the team. It is about the moment the plan becomes a cash commitment, and whether owners can still slow it down when handover certainty deteriorates.

The failure mode owners recognise

Most owners try to manage this through recruitment waves. They approve the wave structure, then re-approve before implementation. They also approve manning levels, recruitment dates, and payroll start dates.

In theory, that should be enough.

In practice, contracts and routines often fail to create a clean stop point. Salaries are typically treated as recurring spend within an approved pre-opening plan. Owners may approve the overall pre-opening budget and fund it in tranches, but that does not automatically translate into a practical ability to pause hiring role by role once momentum builds.

That is how you end up with too many people on payroll while construction slips.

Two clocks that must stay aligned

Owners regain control by separating two clocks and forcing them back into the same cadence.

Clock 1. Construction certainty
Not a single handover date. A confidence band supported by tangible readiness milestones.

Clock 2. Recruitment commitment
Not a staffing plan. A commitment ladder: planned, interviews started, offers issued, mobilising, on payroll.

The owner objective is straightforward. Recruitment commitment should never climb the ladder faster than construction certainty improves.

Why hiring runs early

Operators have legitimate reasons to push recruitment forward. Lead times, training requirements, brand standards, and the need to protect the opening moment are real.

The owner issue is not motivation. It is asymmetry.

If the hotel is short staffed at opening, the operator carries reputational pain. If the project slips after payroll starts, the owner carries the cash pain. When incentives diverge, timing discipline must be designed, not assumed.

The owner control stack that works when the contract is not helpful

Do not try to win this through debates about org charts. Win it by controlling release and commitment.

Two-step approval is mandatory
Approval 1 is strategic. Approve the recruitment plan in principle: waves, sequencing, lead times, and a strict definition of critical roles.

Approval 2 is a commitment gate. Re-approve each wave immediately before execution. No wave release means no offers issued and no mobilisation.

This second approval is where owners either have control or they do not. Without it, the plan becomes self-executing.

Approve dates, not only headcount
A wave is not a headcount number. It is a timing commitment.

For every wave, require:

• offer issue window

• mobilisation and arrival window

• payroll start date

• training start date

• the readiness milestone that justifies release

If dates and triggers are missing, it is not an approvable wave.

Make the pause rule automatic and fact-based
If you rely on ad hoc judgement calls, you will argue every time the project slips. Install an automatic pause rule inside the governance pack.

Example logic:

• If the handover confidence band widens beyond an agreed tolerance, non-critical waves pause until the plan is rebased.

• If training spaces are not confirmed ready, training-heavy roles pause.

• If key commissioning milestones move, recruitment dates rebase before any new offers are issued.

The pause rule is not anti-opening. It is pro-control.

Use funding resets as mandatory rebasing points
Where pre-opening funding is staged, treat each funding top-up as a reset and re-approval point for recruitment timing.

At each reset, require the operator to re-submit:

• updated handover confidence band

• updated wave dates and payroll start dates

• a commitment ladder showing what is reversible versus already committed

• burn sensitivity showing the cost of further slippage at current commitment levels

This ties recruitment timing to a rhythm the contract already recognises.

Separate critical roles from conditional roles, and cap the critical set
Some roles genuinely need to be early. Accept that reality, but cap it.

Define the critical group explicitly. Everything else is conditional. Conditional means released only when the asset can convert payroll into readiness and readiness into revenue.

The minimum owner pack that enables frequent reassessment

Frequent reassessment works only if the pack is short and repeatable.

A five-page owner pack is usually enough:

• Handover confidence band, with the risks that move it.

• Wave plan with dates, payroll start, training start, and milestone triggers.

• Commitment ladder: planned vs committed vs on payroll.

• Burn sensitivity: weekly committed payroll, plus the cost of one-week and four-week slippage.

• Exception log: any hire pulled forward since last approval, with the reason and an exit condition.

If the operator cannot produce this pack quickly, the project is not in control.

Escalation triggers that remove emotion

Escalate when:

• payroll commitments increase while handover certainty deteriorates

• a wave is pulled forward without a milestone trigger

• the project slips but recruitment dates are not rebased within the same cycle

• the proportion of roles already on payroll rises above an agreed threshold while trading readiness is still uncertain

When a trigger hits, the default is pause and rebase. Not continue and hope.

Owner outcome after opening

You will still have inefficiency in the first months. That is normal. The question is whether inefficiency is bounded.

Owners should expect:

• a defined month where productivity is assumed to normalise

• phased outlet operations reflected in staffing and payroll start dates

• a run-off plan for training-heavy mobilisation staffing

• a bridge from early payroll decisions to the timeline for Owner Free Cash Flow (OFCF)

If productivity improvement is not explicit, early hiring is no longer a ramp. It is a cost reset.

Close

Construction slippage is a fact pattern. Owners do not fight it with optimistic dates. Owners protect value by controlling the moment recruitment becomes irreversible.

Approve waves twice. Approve dates, not just headcount. Install an automatic pause rule tied to construction facts. Use funding resets as rebasing points. Track what is reversible versus already on payroll.

That is how you keep the manning curve aligned to the ramp-up plan, and keep pre-opening burn as an investment rather than an owner-funded timing loss.