Manage day-labor/temp staffing compliance for peak moving season surges
domain: dol.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Classify surge-season workers correctly as employees (not independent contractors) if you control their schedule, supervise their work, and set their pay rate — misclassification exposes you to wage-and-hour liability
Pay all day laborers and temp workers at least federal (and applicable state/local) minimum wage for all hours worked, regardless of whether they're paid hourly, daily, or by piece rate, and pay proper overtime where owed
If sourcing crews through a staffing agency, put a clear written services agreement in place defining who handles payroll, benefits, supervision, and discipline, since the U.S. Department of Labor evaluates the practical relationship (not just the contract label) when determining joint-employer status
Track hours, breaks, and safety training for temporary loading/packing crews the same way you would for permanent staff, since wage-and-hour and OSHA-type obligations generally apply equally to temp workers
Watch for updates to DOL's joint-employer rulemaking, since a proposed rule addressing joint employer status under the FLSA and related statutes has been moving through public comment and could affect how your staffing-agency relationships are evaluated
Known gotchas
Treating peak-season crews as 1099 contractors while directing their day-to-day work is a common and risky misclassification pattern in the moving industry, especially with load/unload day laborers
A staffing agency's own compliance failures (e.g., unpaid overtime) can still create liability for the moving company if DOL determines a joint-employer relationship exists
DOL's joint-employer rule was still in the proposed-rule stage as of mid-2026 — don't treat draft rule language as final law when setting staffing agreements; confirm current status before relying on it
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?