Payroll as a percentage of revenue — what is normal
Usually the largest single cost a small hotel has, and one of the least-watched. A benchmark, a worked example, and what a ratio that's too low actually costs you.
Payroll is usually the single largest cost a small hotel carries, and it is also one of the least watched, because it arrives as a monthly total rather than a ratio anyone checks against revenue. The ratio is what turns 'payroll feels high this month' into a number you can actually act on.
The formula
Payroll cost ratio = total payroll ÷ total revenue × 100. A property paying ₱380,000 a month in salaries on ₱1,520,000 of revenue is at 380,000 ÷ 1,520,000 × 100 = 25% — right in the middle of the normal range.
The range worth targeting
For a Philippine property with a restaurant, somewhere in the mid-twenties to low thirties is normal. Meaningfully below that usually means the property is understaffed — and reviews mentioning slow service or an empty front desk are the lagging indicator of a ratio that looked great on paper for a few months first. Meaningfully above it means the roster is carrying the season rather than the season carrying the roster.
Why 'understaffed' doesn't show up immediately
A payroll ratio that drops because a property is running lean feels like good news for a month or two — costs are down, margin is up. The cost shows up later, in guest experience rather than in the P&L: slower response times, housekeeping falling behind on a busy day, a front desk that can't answer the phone during check-in. By the time it reaches reviews, the understaffing has usually been true for a while.
The ratio to check before hiring
A new full-time role is a permanent claim on revenue you have not earned yet — it raises the payroll ratio immediately and holds it there whether the season justifies it or not. Checking where the ratio sits before adding headcount, rather than after, is what keeps a hiring decision honest instead of retroactively justified by whatever the season happens to do.
When the real problem is seasonality, not staffing
A property whose payroll ratio looks fine in December and painful in September does not have a staffing problem — it has a seasonality problem wearing a staffing problem's clothes. The fix in that case is a roster that flexes with demand, more part-time coverage in peak months rather than a fixed full-time headcount sized for the busiest week of the year and carried through the quietest one too.
Where the number should actually live
Payroll buried inside a general expenses total hides the one figure worth watching on its own. Keeping it as its own line, next to revenue, rather than folded into an aggregate 'costs' figure, is what makes the ratio something you glance at monthly instead of something you calculate once a year when the accountant asks.
What the ratio doesn't tell you
Two properties can share an identical 27% payroll ratio and be in completely different positions — one running lean and efficient, the other overstaffed relative to a below-market wage bill. The ratio flags where to look; it doesn't replace actually knowing whether the team is the right size for the work, which is a judgement about people, not something a percentage settles on its own.
Comparing full-time and part-time honestly
A roster leaning heavily on part-time staff during peak season can show the same payroll ratio as one running fewer, better-paid full-time roles — the total is what the ratio sees, not the mix. Worth checking separately: whether the part-time-heavy version is actually cheaper once onboarding time and inconsistent service quality are accounted for, since those costs are real even when they don't show up in the payroll line itself.
Reading it month to month, not just annually
An annual payroll ratio smooths over exactly the seasonal swing worth catching early. Checking it monthly against that month's actual revenue — not a yearly average — is what surfaces a September that's quietly bleeding margin while December looks fine, in time to actually do something about the next low season rather than discovering the pattern a year later in the annual numbers.
A second property, worked through
A ten-room guesthouse paying ₱210,000 a month in salaries on ₱700,000 of revenue sits at 210,000 ÷ 700,000 × 100 = 30% — the top of the normal range, worth a closer look but not alarming on its own. The same guesthouse at ₱210,000 payroll against ₱480,000 revenue in a slow month is at 43.75%, which is the kind of number that demands an explanation: either the season genuinely doesn't support the current headcount, or the revenue side has a separate problem the payroll ratio is simply exposing.
Restaurant properties skew the number differently
A hotel with an active F&B operation typically carries more payroll relative to revenue than one selling rooms alone — kitchen and service staff add real headcount without adding room revenue to offset it directly. Comparing a restaurant-carrying property's payroll ratio against a benchmark meant for rooms-only hotels will read as alarmingly high when it may simply reflect a different, entirely normal cost structure for that kind of operation. The honest comparison is against similar properties, not a single number treated as universal.
What to do the first time the number looks wrong
A payroll ratio that suddenly looks far outside the normal range is worth a moment of arithmetic before it becomes a staffing decision — check whether a one-off cost (a bonus, a severance payment, an unusually quiet week of revenue) is distorting a single month before assuming the underlying trend has actually shifted. Acting on one anomalous month as if it were the new normal is how a temporary blip turns into an unnecessary headcount cut that the next busy month then can't recover from.
Turn the answer into a working view
See it on your own property
See your own revenue, costs and profit in one live view.