Blog

Multi-property labor reporting without the spreadsheet

· portfolio, labor cost, reporting

A portfolio labor report is not a property labor report with more rows in it. The consolidation most operators build first — one tab per property, hours and dollars totalled at the bottom — answers the question that matters least, which is what did we spend. The three things a multi-property labor report actually has to do are harder and duller: put every property in a unit you can compare, surface which property drifted rather than which is largest, and make “yesterday” mean the same thing at all of them. A spreadsheet fails at all three, and it fails quietly.

Why the spreadsheet stops working at about five properties

Not because of the hours, though those are real. Say it takes twenty minutes a property to pull the punch export, reconcile the obvious errors and paste it in. At eight properties that is a bit under three hours every week, and most of it is chasing the one GM who hasn’t sent theirs.

The hours are the smaller problem. The bigger ones:

  • It is always late. The file gets built Tuesday for a week that ended Sunday. Every decision it could have informed was made on Thursday. A labor report that arrives after the schedule it should have changed is a history assignment.
  • It breaks silently. One property changes its export columns, a formula range stops at row 400, a new property gets added to the folder but not to the summary tab. Nothing errors. The total is just wrong, and it is wrong in the direction of “looks fine.”
  • It lives with one person. When they’re on holiday the portfolio has no labor visibility for a week, which nobody discovers until they need it.

None of that is an argument for software specifically. It is an argument that the consolidation has to be automatic, because a manual one that is late, fragile and single-threaded is worse than a simpler report that is none of those.

Raw hours are not comparable — normalise before you rank

The single most common mistake in portfolio reporting is putting hours or dollars side by side and reading the biggest number as the problem. Here is an invented week across three properties:

PropertyRoomsOccupied room-nightsHours paidLabor costHours per occupied room-nightCost per occupied room-night
A38196214$3,6381.09$18.56
B64371352$5,9840.95$16.13
C42168205$3,4851.22$20.74

(Blended rate $17 across all three, to keep the arithmetic visible.)

Property B has by far the most hours and the largest labor bill, and it is the best-run property on the page. Property C has the fewest hours of the three and is the one worth a phone call: it is spending 1.22 hours per occupied room-night against A’s 1.09, at a property of almost the same size.

The gap is worth putting a number on. Bringing C to A’s ratio would take 168 × 1.09 ≈ 183 hours instead of 205 — about 22 hours a week, roughly $374, or a little over $19,000 a year at one property. That is the number that justifies the drive out there, and you cannot see it in the hours column.

Occupied room-nights are the denominator to prefer because they track the work that actually gets generated. If you don’t capture occupancy reliably, hours per available room-night is a weaker substitute that still beats raw hours — it just can’t distinguish a slow week from an overstaffed one. What MPOR measures and where it misleads covers the difference.

If you’d rather not assemble the underlying numbers every Monday, ProfitClock emails a daily labor flash for each property you run, on that property’s own clock, so yesterday’s hours land while the schedule can still change.

Make “yesterday” mean one thing

This is the failure that costs money and is nearly invisible, and it gets worse with every timezone a portfolio spans.

A consolidated report has to decide which calendar day a punch belongs to. If it decides that centrally — on the head office’s clock, or on UTC — then an evening shift at the western-most property lands on the following day. The portfolio total for the week is still correct, which is exactly why nobody catches it: only the grouping is wrong, and grouping is the thing nobody audits. In a state with a daily overtime threshold, a shift split across two days can stop crossing that threshold at all. The full mechanism is worth understanding once if any of your properties sit in a state with a daily rule.

The portfolio-specific version of the same problem is the workweek. If one property runs Monday-to-Sunday and another Sunday-to-Saturday — which happens constantly, because each one inherited its schedule from whoever set it up — then week-to-date hours are not comparable between them, and a consolidated “this week” is two different weeks stacked. Neither setting is wrong. Both being unrecorded is.

Two things to check on a report you’re being sold or one you’re building: what timezone each property’s day is resolved in, and what day each property’s workweek starts.

The question a portfolio report cannot answer for you

An employee who worked at two of your properties in the same week: do those hours add together for overtime?

No report decides this. It turns on whether the two properties are joint employers of that person under the FLSA. The related-entity version is what DOL and the courts call horizontal joint employment, and it turns on how associated the two entities actually are: common control, an arrangement to share the employee’s services, one acting in the interest of the other. Where it applies, the week’s hours across both are aggregated for the overtime calculation. Where the properties are genuinely separate employers, they are not. There is no current DOL regulation on this: the joint-employer rule that sat at 29 CFR part 791 was rescinded in 2021, and DOL proposed a replacement in April 2026 that is not final. Today’s analysis rests on the FLSA itself and on case law, and it may move.

This matters more in this segment than most, because independent hotel ownership routinely puts each property in its own entity with its own EIN. Two properties in one management portfolio may or may not be one employer, the test is fact-specific, and getting it wrong is expensive in one direction and pointless in the other. This is not legal advice and no article can settle it — take it to counsel licensed where you operate, then make your reporting match the answer rather than the other way round.

What the report can do, and should, is tell you which employees worked at more than one property in a workweek. That list is short at most portfolios, and it is the list you need in hand before the conversation is worth having.

Where a portfolio report is the wrong tool

Worth being plain about, because the pitch for consolidation always oversells it.

Under about four properties. A spreadsheet is genuinely fine at three. The break-even is not a room count, it is the point where nobody can hold all of it in their head — which is roughly the fifth property, and earlier if they’re in different states.

Properties with different service models. An extended-stay property with a three-night average stay generates far fewer checkout cleans per occupied room-night than a transient motel off an interstate, and a checkout takes materially longer than a stayover. Putting them in the same league table punishes the one with the harder mix and tells you nothing.

Ranking, generally. A cross-property ranking is good at producing questions and bad at producing verdicts. The more reliable read is each property against its own last four weeks; the cross-property column is for deciding which property’s own trend to go look at first.

The Monday list

Four numbers, per property, and nothing else until these are clean:

  1. Unresolved punch exceptions. Until that count is near zero the rest is an estimate — the same reason it comes first on a single property’s daily report.
  2. Hours per occupied room-night, against that property’s own last four weeks. Cross-property second.
  3. Overtime hours as a share of total hours. A property well above the rest of your portfolio (say 6% when the others run 2%, a made-up contrast, not a benchmark) has a coverage design problem, not a discipline problem.
  4. Anyone who worked at more than one property this week.

Everything else on a consolidated report — the totals, the department splits, the percentage of revenue — is a monthly conversation that happens to be printed weekly.

Start seeing what labor actually costs

Set up your property, put staff on the clock, and read tomorrow morning’s labor number.

14-day free trial · No credit card · Cancel anytime