Joint Employment: Brand, Owner, Operator & Staffing Agency

Ask who "the employer" is at a branded hotel and you get three answers: the brand whose flag flies over the door, the investor group that owns the real estate, and the management company that signs the paychecks — four, once the staffing agency supplying half of housekeeping is counted. Wage-and-hour law chooses its own answer, and it routinely chooses more than one. Joint employment decides whose problem a housekeeper's unpaid overtime becomes, and the recurring lesson of hotel litigation is that "everyone's" is on the menu — the solvent entity pays the whole judgment, and contracts among the parties cannot take the liability off the worker's claim.

Three logos, one paycheck: the hotel triad#

The modern hotel is deliberately disaggregated: an asset-light brand franchisor licenses the flag and systems; a property owner (often a single-asset LLC) holds the real estate; a management company operates the hotel under a hotel management agreement (HMA) as the owner's agent; and a staffing agency often supplies the housekeepers, stewards, and banquet servers. Wage-and-hour liability does not respect that org chart: the FLSA asks who, as a matter of economic reality, employs the worker — not whose name is on the W-2.

Four quick reads of the cast before the line-drawing detail. The manager sets schedules, directs the work, disciplines, and pays — the employer under any formulation; even a managing agent operating property for an owner is an FLSA employer of the workers it directs (Falk v. Brennan), so the fights are about who stands behind it. The owner is named because it has the balance sheet and funds every payroll dollar under the HMA; a passive owner behind an arm's-length HMA often escapes, but one whose asset manager approves staffing guides and pay ranges and orders the cost-per-occupied-room cuts that push housekeepers into off-the-clock work is building a control record one email at a time. The brand is generally not an employer on standards alone — Salazar v. McDonald's (9th Cir. 2019) held a franchisor imposing brand standards and supplying training and scheduling software was not its franchisee's employer because it did not control hiring, firing, wages, or day-to-day work — and crosses the line only when it reaches into daily labor decisions, drawn clause by clause below. The staffing agency is its workers' direct employer, with the hotel frequently their joint employer. Do not assume the brand's deep pocket will be reachable in a wage case.

What the management agreement allocates — and the Salazar line, clause by clause#

The HMA allocates employment cost and risk and should be read with wage litigation in mind. Employment costs — wages, benefits, payroll taxes, and usually employment-claim settlements — are operating expenses of the hotel, funded by the owner even though the manager is the employer of record; the owner therefore pays for both compliance and violations, and should demand compliance covenants, audit rights, and prompt claim notice. Indemnities typically leave ordinary-course employment liabilities with the owner while the manager indemnifies for its own gross negligence or willful misconduct — where the parties fight when a seven-figure settlement needs a home. And nearly every HMA recites that the manager is the sole employer.

Hotel trap The "manager is the employer" clause is a reimbursement map, not a shield. Employer status is decided by economic reality, not contract recitals — plaintiffs are not parties to the HMA and are not bound by it. The clause tells the owner and manager who reimburses whom after both are found liable; it does not keep the owner out of the caption.

So the useful review is to sort each clause onto one side of the Salazar line. Brand standards — the consistency the guest pays the flag for — do not make a franchisor an employer; operational control over the workforce — the daily labor decisions — builds joint employment one retained right at a time, judged on the economic-reality factors (hire/fire, supervision, pay-setting, records). Read the agreement clause by clause against this checklist.

Hotel trap The line is about the workforce, not the asset. Owners and brands may control the product, the brand, and the capital plan — and demand a clean compliance program — but they cross the line when control reaches the people: an asset manager who approves individual pay ranges and enforces staffing guides shift by shift is on the operational-control side, whatever the recitals say.

The governing test: judicial economic reality in a regulation-free field#

The hierarchy has an unusual shape here. At the federal level there is currently no joint-employment regulation at all: the 2020 FLSA rule (29 CFR part 791) was largely struck down in New York v. Scalia (S.D.N.Y. 2020) and rescinded by DOL in 2021 (86 FR 40939), and nothing replaced it. The field is governed by the judicial economic-reality test, each circuit applying its own articulation — so the same arrangement can come out differently by venue. The Ninth Circuit weighs the four Bonnette factors (power to hire and fire, supervision of schedules and conditions, rate and method of payment, employment records); the Second Circuit adds the broader Zheng functional-control factors (premises and equipment, whether the work is integral, supervision). California asks the parallel Martinez v. Combs question — who controls wages, hours, or working conditions; who "suffers or permits" the work; who engages. The common thread is substance over the org chart, and no circuit lets a contract recital answer the question.

Watch item — the DOL joint-employment NPRM under consideration WHD's stated 2026 pipeline is the independent-contractor replacement rule (proposed Feb 27, 2026) and a joint-employment NPRM under consideration to fill the "regulatory gap since 2021"; nothing has been proposed as of June 12, 2026. A future rule could standardize the FLSA vertical-joint-employment factors — narrowing the circuit split with a single, likely control-focused test that would help brands. It could not bind state law: California's Martinez/Dynamex definitions and, critically, Labor Code §2810.3 — a statute, not a joint-employer doctrine — would be untouched, so a federal rule exonerating a brand under the FLSA does nothing about a California client's statutory wage liability. Calendar the NPRM; do not reorganize around a rule that does not exist. (The NLRB's 2023 joint-employer rule was vacated in March 2024 — a bargaining-law fight under a different statute, not a wage rule.)

Staffing agencies: vertical joint employment in housekeeping, stewarding, and banquets#

Vertical joint employment is the hotel's highest-frequency exposure. Agency housekeepers, stewards, and banquet servers are the supplier's direct employees — but the joint-employment question is about the hotel, and for long-term agency housekeepers the facts point one way. The executive housekeeper assigns the boards, sets start times and room quotas, inspects the work, sends people home early, and decides who comes back tomorrow; the work is on the hotel's premises and as integral as hotel work gets. A hotel supervising agency housekeepers for months should assume it is their joint employer.

Two consequences follow. Joint and several liability: each joint employer owes the full amount — the worker can collect 100% from either, and a thinly capitalized agency that dissolves leaves the hotel as the solvent defendant (the next section walks what "the whole judgment" contains). Hour aggregation: all hours in the joint employment aggregate in the workweek. An agency housekeeper who cleans 32 hours through the agency and picks up 12 banquet hours hired directly by the hotel has worked 44 — four of them overtime — though each payroll alone shows fewer than 40. Aggregation across agency, direct, and sister-property hours is the housekeeping-specific exposure in housekeeper pay.

Paying the invoice is not paying wages If the agency bills $26 per housekeeper-hour and pays its workers $14 with no overtime premium, the hotel's paid invoices are no defense: in a joint-employment posture the hotel owes the wages the agency failed to pay — and in California, §2810.3 reaches the same result without any joint-employment finding.

California Labor Code §2810.3: liability without joint employment#

California answered the question by statute, and most operators have never heard of it. Labor Code §2810.3 (AB 1897, effective January 1, 2015) provides that a "client employer" — a business obtaining workers from a "labor contractor" for labor within its usual course of business — shares all civil legal responsibility and civil liability with the contractor for those workers' wages and for failure to secure workers'-compensation coverage. The hotel need not control the agency's payroll, supervise the workers, or meet any joint-employer test: if the agency shorts its housekeepers, the hotel is liable for the wages by statute.

The statute excludes small client employers (under 25 workers, or five or fewer labor-contractor workers at a time) and exempt executive, administrative, and professional employees — but a full-service hotel with a standard agency housekeeping complement is squarely covered. A worker must give the client 30 days' notice before suit — the hotel's window to force a cure. Waiver is void as against public policy; no clause can shift §2810.3 liability to the worker. What the statute expressly permits is indemnity between hotel and agency — the Legislature's signal that risk allocation belongs in the staffing contract, not in a defense to the worker's claim.

The analysis operators get wrong Hotels analyze control, conclude "we are not a joint employer," and stop. In California that is beside the point: §2810.3 attaches wage liability to the client relationship itself, so the only live questions are whether the agency is compliant and whether the indemnity behind it is collectible (see the California page).

Exposure anatomy: what "the whole judgment" actually contains#

Joint-and-several liability is not a theoretical label — it decides which balance sheet absorbs a number much larger than the unpaid wages. Horizontal joint employment is the multi-property version: where commonly owned or managed properties are sufficiently associated — shared officers, one HR function, supervisors moving staff between buildings — the entities are joint employers and the employee's hours aggregate across properties for overtime, which ownership groups miss because each LLC's payroll looks clean in isolation. The example starts with a small premium and follows the line to who writes the check.

The derivative consequences — and who bears them#

In California the unpaid premium is the smallest line. Because unpaid overtime is an unpaid wage, the derivative stack attaches automatically — the transmission canonically modeled in PAGA and class actions. Every pay period with understated hours produces an inaccurate §226 wage statement ($50 first period, $100 thereafter, capped at $4,000 per employee); every separated worker whose final pay was short draws §203 waiting-time penalties (up to 30 days of the daily wage); and PAGA meters a civil penalty per employee, per pay period on top, payable mostly to the state. Whether the hours are even provable when two LLCs' records do not reconcile is the Mt. Clemens inference owned by recordkeeping.

The point joint employment adds: each joint employer is jointly and severally liable for the entire stack — premiums, §203, §226, and PAGA — not for "its" LLC's slice. If Property B's LLC is a single-asset shell and A's is solvent, the worker and the LWDA execute against A for 100% of a number generated partly at B. The owner that funds payroll, and any entity found to be a joint employer, is the deep pocket the judgment seeks — which is why the §226/§203/PAGA derivatives, not the $47.50 premium, are what an operator should price.

The indemnification reality and the judgment-proof-vendor trap#

Operators reach for indemnity as if it solved the problem. It does not: an indemnity clause reallocates dollars between defendants; it never moves primary liability off the worker's judgment. The worker — not a party to the staffing contract or HMA — sues every employer, wins joint-and-several judgment against all, executes against the solvent one, and then the indemnity governs whether the paying defendant can recover from the other. So indemnity is a downstream reimbursement right, not a defense — it never keeps the hotel out of the caption or off the judgment. And — the judgment-proof-vendor trap — an indemnity from an undercapitalized agency is worth only what the agency can pay; the agencies most likely to underpay their housekeepers are the ones most likely to be thinly capitalized and to dissolve when a claim lands, leaving the hotel holding 100% of the judgment and a worthless indemnity against a vanished counterparty. The lesson is not "don't take indemnity" — take it — but "don't rely on it": price the relationship as if the indemnity is uncollectible, and make it collectible through the protocol below.

Decision framework: the staffing-agency diligence protocol#

Because employer status cannot be drafted away and the indemnity may be uncollectible, the only protection that works is making the agency demonstrably compliant before a claim and its failures recoverable after one. That resolves to specific contract language — six terms, in priority order.

• A bill-rate floor that demonstrably funds compliant wages plus overtime. The load-bearing term. Require disclosure of the pay rate, not just the bill rate, and contract a minimum bill rate that arithmetically covers the applicable minimum wage, the FLSA (and California daily) overtime premium, payroll taxes, sick leave, and workers'-comp premium, with margin. If a $26/hour bill rate cannot fund a $14 wage plus its overtime and on-costs, the bill rate is itself notice of a violation in progress; a floor that can fund compliance is the best predictor the housekeepers are actually being paid.
• Audit rights over the agency's payroll, on a calendar. The right to inspect payroll registers, time records, and wage statements for every assigned worker, exercised on a fixed cadence — an unexercised audit right reads badly to a jury and proves nothing.
• Certified-payroll production. A recurring signed statement that the listed wages, hours, and overtime were actually paid, as a condition of paying the next invoice — turning the audit right into a routine deliverable and the contemporaneous record an audit later tests.
• Insurance and bonding that survive the agency. Proof of in-force workers'-comp coverage (§2810.3 reaches a workers'-comp failure directly), commercial general liability, and — for thin suppliers — a surety bond or funded escrow sized to credible wage exposure, hotel as additional insured/obligee. This is the answer to the judgment-proof-vendor trap: collateral independent of the agency's solvency.
• Compliance reps and indemnity, defense costs included. Written reps on wage and overtime payment, breaks, compliant wage statements, and workers'-comp coverage, recertified annually; an indemnity covering wages, penalties, and defense costs — a backstop to the bonding, not a substitute.
• Aggregation hygiene. Capture agency workers' hours in the hotel's own timekeeping and aggregate them with hours the same person works directly or at a sister property, so overtime is paid on the true total (see housekeeper pay).

The §2810.3 overlay changes the math in California Run the protocol regardless, but in California it is not optional risk management — it is the only defense to a liability that attaches by statute. §2810.3 makes the client hotel share liability for the agency's wage and workers'-comp failures regardless of joint-employer status, nonwaivably. A California operator that wins the joint-employer argument still pays under §2810.3, so the bill-rate floor, certified payroll, bonding, and statutory indemnity are the entire toolkit. Calendar the 30-day pre-suit notice as a live cure window — force the agency to fix and document the shortfall before suit.

Safe harbor For long-term agency housekeepers and stewards, the defensible posture is to assume joint-employer status and run compliance accordingly — verified wages, aggregated hours, break compliance on property — rather than spending the litigation on the label. Workload and panic-button ordinances covering these same workers are collected at hotel ordinances. Model entity-level exposure in the compliance profiler.

How this compounds across the library#

Joint employment is a transmission mechanism: it does not create new wage violations, it decides who answers for the violations the rest of the library defines — and changes the math on each. Four lines run out from this brief, each a mechanism, not an adjacency.

• Independent contractors — the vendor path's residual joint-employer tail. Contracting out valet, banquet labor, or housekeeping to a vendor to avoid a direct employment relationship trades a misclassification question for a joint-employment one. Even where the individuals are genuinely the vendor's employees, the hotel that directs and supervises them remains their joint employer — and in California §2810.3 attaches besides. The two doctrines are the front and back of the same vendor decision.
• Housekeeper pay — agency housekeepers and shared-employee OT aggregation. Housekeeping is where joint employment bites hardest: the largest hourly population, the most heavily agency-staffed, the most likely to move between sister properties. Hours through the agency, directly for the hotel, and at a second commonly owned property all aggregate in one workweek, with the premium on the weighted-average regular rate (overtime and the regular rate).
• Seasonal resorts — H-2B petitioner versus worksite employer. A resort bringing in seasonal labor through an H-2B staffing agent inherits the same split: the agent may be the visa petitioner, but the resort supervising the workers on its premises is typically their worksite joint employer — owing the prevailing wage and overtime jointly, whatever the petition says.
• PAGA and class actions — naming multiple entities and the §2810.3 reach. California plaintiffs name owner, operator, brand, and agencies together so the judgment finds the solvent defendant, and §2810.3 can pull a client into a labor contractor's wage case. The "all reasonable steps" cap file must therefore cover every named entity — a cap that protects only the operating LLC leaves the owner exposed.

Compliance checklist#

• Map every entity touching labor at each property — brand, owner, operator, staffing suppliers — and identify the W-2 employer, the putative joint employers, and (in California) every §2810.3 client-employer relationship.
• Read each HMA and franchise agreement clause by clause against the Salazar table; keep brand and owner involvement on the standards side (quality audits, training content, PMS/CRS mandates, SOP standards) with no role in hiring, firing, scheduling, discipline, or wage-setting, and document that line personnel are directed only by the manager.
• Treat long-term agency housekeepers, stewards, and banquet staff as joint employees: verify pay, aggregate hours across agency, direct, and sister-property assignments, apply break rules on property.
• Build staffing contracts around the six diligence terms: a bill-rate floor that funds minimum wage, overtime, payroll taxes, sick leave, and workers'-comp premium (checked against the disclosed pay rate); calendared payroll audit rights, actually exercised; recurring certified-payroll production; workers'-comp proof, CGL, and a surety bond or escrow for thin suppliers (hotel as additional insured/obligee); compliance reps and an indemnity covering defense costs.
• Take the §2810.3 indemnity but price the relationship as if it is uncollectible — a backstop to bonding, not a substitute.
• In California, confirm §2810.3 coverage and calendar the 30-day pre-suit notice window as a live cure opportunity.
• For multi-property groups: designate a paymaster and aggregate hours for any employee shared across commonly owned properties (see housekeeper pay); ensure any PAGA "all reasonable steps" cap file covers every named entity, not just the operating LLC.
• Calendar a review for the DOL joint-employment NPRM under consideration; today's test is the judicial economic-reality standard, a new rule could not touch California §2810.3, and the field can change.

Key authorities#

• FLSA §3(d), (e), (g) (definitions of employer, employee, "suffer or permit to work"); 29 U.S.C. §§216(b), 255(a), 260 (joint-and-several liability, lookback, liquidated damages, good-faith defense).
• Falk v. Brennan, 414 U.S. 190 (1973) (managing agent as FLSA employer).
• Bonnette v. California Health & Welfare Agency, 704 F.2d 1465 (9th Cir. 1983); Zheng v. Liberty Apparel Co., 355 F.3d 61 (2d Cir. 2003) (economic-reality and functional-control tests).
• Salazar v. McDonald's Corp., 944 F.3d 1024 (9th Cir. 2019); Martinez v. Combs, 49 Cal.4th 35 (2010) (California's "employ" definitions and control test).
• Cal. Lab. Code §2810.3 (client-employer shared liability for wages and workers'-compensation coverage; 30-day pre-suit notice; nonwaivable; indemnity permitted; AB 1897 (2014)).
• Cal. Lab. Code §§203, 226, 226.7 and §§2698–2699.5 (PAGA) (the derivative penalty stack that travels to each joint employer); Naranjo v. Spectrum Security Services, Inc., 13 Cal.5th 93 (2022) (premiums are wages — the §203/§226 derivative trigger).
• 85 FR 2820 (Jan. 16, 2020) (2020 FLSA joint-employer rule); New York v. Scalia (S.D.N.Y. 2020) (vacating most of the rule); 86 FR 40939 (July 30, 2021) (rescission); DOL WHD joint-employment NPRM under consideration (none proposed as of June 12, 2026).