How the DOL’s joint employer framework rewrites MSP staffing risk
Managed service provider programs sit exactly where the department of labor is now aiming its joint employer spotlight. The proposed rule on joint employer MSP staffing DOL issues reframes how staffing firms, host employers, and workers share responsibility for wage hour compliance, and it does so by centering control rather than labels. For HR and procurement leaders running a large contingent workforce, this means the structure of every staffing agreement and every VMS workflow will now be read as evidence of real employment control.
Under the vertical joint employment model, the DOL looks at how a staffing firm supplies employees to a host employer that directs their daily work. The more your managers set schedules, approve overtime, and dictate methods of work for temporary employees, the more likely a joint employment finding becomes for both the staffing agency and the host employer. That is why the joint employer MSP staffing DOL framework matters so much for Beeline, SAP Fieldglass, VNDLY, and similar platforms, because they encode who can approve time, change rates, and move workers between assignments.
Horizontal joint employment is different, but it still touches MSP staffing structures when related entities share workers or coordinate labor policies. If your enterprise uses one master staffing firm across several affiliated companies, the DOL will examine whether those firm clients operate as a single employer for wage hour purposes. In practice, the department of labor will ask whether employees experience one integrated employment relationship, regardless of how many legal entities appear in the contracts.
The proposed rule also expands the joint employer standard beyond the Fair Labor Standards Act into the Family and Medical Leave Act and the Migrant and Seasonal Agricultural Worker Protection Act. That expansion means joint employer status can now affect leave eligibility, recordkeeping, and workers compensation exposure for contingent workers, not only minimum wage and overtime. For MSP buyers, the joint employer MSP staffing DOL framework therefore becomes a central compliance lens for every staffing firm, every independent contractor, and every temporary staffing channel in the program.
Vertical joint employment in MSP programs: where VMS workflows create liability
Vertical joint employment is the scenario most MSP program owners should worry about, because it maps directly onto how staffing firms feed talent into enterprise clients. In a typical MSP model, a staffing firm supplies employees who technically remain on the staffing agency payroll, while the firm client manages the day to day work. The DOL’s joint employer MSP staffing DOL proposal asks whether that division is real in practice, or whether the host employer effectively controls the entire employment relationship.
Look at your VMS configuration in Beeline, SAP Fieldglass, or VNDLY and map every touchpoint where your managers influence employees. When hiring managers set pay rates, approve candidates, and define work schedules for temporary workers inside the system, they are exercising the kind of control that the factor test for joint employment treats as evidence of employer status. Even where staffing firms nominally handle onboarding, discipline, and termination, the DOL will examine whether the host employer’s approvals and rejections generally drive those employment outcomes.
Rate card governance is another pressure point that many staffing industry leaders underestimate. When an MSP buyer dictates maximum bill rates, minimum pay rates, and markups for contingent workers, the department of labor can view that as direct influence over wage hour conditions, even if the staffing firm issues the paychecks. That is why pay transparency initiatives and VMS data reporting, such as those discussed in analyses of how pay transparency laws reshape bill rates and markups, now intersect with joint employer risk.
Scheduling and supervision complete the vertical joint employment picture. If your supervisors assign tasks, approve time sheets, and direct safety practices for temporary staffing employees, the DOL will treat that as substantive control over work and employment conditions. Under the proposed rule, even where staffing firms retain formal authority in agreements, the real world pattern of who controls the work will carry more weight than boilerplate contract language.
Reserved control in MSP contracts: when standard clauses create joint employer status
Reserved control is the quiet risk multiplier inside many MSP master services agreements and staffing firm contracts. The DOL’s joint employer MSP staffing DOL proposal states that while actual control remains the most important factor, the mere reservation of control in agreements can still support a joint employer finding. That means clauses your legal équipe once viewed as harmless risk management may now be read as evidence of employer status over contingent workers.
Common examples include host employer rights to approve or reject any employee, to demand removal of specific employees from the site, or to require prior approval before a staffing firm can reassign workers. Even if your managers rarely exercise those rights, the department of labor will treat the reserved authority as part of the factor test for joint employment. Safety requirements, background check standards, and training mandates can also signal that the firm client is shaping core terms of employment, not just outcomes of the work.
Service level agreements and performance remedies add another layer of complexity. When an MSP buyer imposes strict SLAs on time to fill, turnover, and quality, and then ties penalties to how staffing firms manage employees, the DOL can infer that the host employer indirectly controls employment practices. The more your firm clients dictate how staffing firms recruit, screen, and discipline employees, the easier it becomes for regulators to argue that both entities share joint employment responsibility.
Program owners should also revisit independent contractor language embedded in MSP and VMS frameworks. Many enterprises rely on contractor classification rules that were shaped by earlier guidance, including the two factor test debates summarized in analyses such as why procurement leaders should engage on contractor rules. Under the new joint employer MSP staffing DOL lens, reserved control over independent contractors and independent contractors’ schedules, tools, and methods of work can undermine contractor classification and pull those workers into joint employment exposure.
How the new framework differs from the prior rule and why exposure widens
The earlier joint employer rule leaned heavily on a narrow control test that focused on actual, direct supervision of employees. Under that approach, many MSP buyers took comfort in the idea that as long as staffing firms handled payroll, discipline, and formal employment decisions, the host employer would generally avoid joint employer status. The new joint employer MSP staffing DOL proposal removes much of that comfort by broadening both the legal scope and the factual inquiry.
First, the rule now applies a single joint employment standard across the Fair Labor Standards Act, the Family and Medical Leave Act, and the Migrant and Seasonal Agricultural Worker Protection Act. That unified approach means a joint employer finding can trigger wage hour liability, FMLA leave obligations, and MSPA protections for certain categories of workers, all at once. For enterprises that rely heavily on temporary staffing and contingent workers, the expansion beyond pure wage hour issues significantly raises the stakes of every staffing firm relationship.
Second, the DOL explicitly elevates reserved control, indirect control, and shared control as relevant factors in the joint employment analysis. Even where a staffing agency or staffing firm appears as the sole employer on paper, the department of labor will examine whether the firm client influences hiring, firing, scheduling, or pay through contractual rights or operational practices. In other words, the factor test now looks past labels like independent contractor or temporary employee and focuses on how work is actually organized.
Third, the proposal clarifies how vertical and horizontal joint employment interact in complex corporate structures. A large enterprise that uses one MSP across multiple affiliates may face joint employer findings both as a group of related employers and as individual host sites that control day to day work. For HR and procurement leaders, this means joint employer MSP staffing DOL risk is no longer confined to a single business unit; it can extend across the entire staffing industry footprint of the organization.
What MSP program owners should audit now: contracts, operations, and gaps
Program owners cannot wait for final rules before tightening their MSP governance, because the factual record of how you treat workers is being built every day. A disciplined audit of contracts, operational practices, and documentation will help you understand where joint employer MSP staffing DOL risk is already baked into your model. Start with a simple map that links each staffing firm, each staffing agency, and each category of contingent workers to the business units that direct their work.
Contract review should focus on every clause that touches control over employees, not only indemnity and insurance. Identify where the firm client reserves rights to approve hiring, set pay ranges, dictate schedules, or require removal of specific employees, and then compare those rights to how managers actually behave. Where agreements grant broad control that managers do not use, you have an opportunity to narrow the language and reduce the weight of reserved control in any future factor test.
Operational audits should then examine how VMS workflows, onboarding processes, and day to day supervision align with the contracts. If your Beeline or Fieldglass configuration allows hiring managers to change pay rates, override staffing firms’ candidate rankings, or move employees between assignments without supplier approval, the department of labor may treat those features as evidence of employer status. The same applies to how you handle workers compensation incidents, safety training, and performance management for temporary staffing employees on site.
Finally, compare your independent contractor processes to your temporary staffing controls. Where independent contractors are routed through the same MSP, subject to the same approvals, and managed by the same supervisors as employees, contractor classification becomes fragile. Analyses of how MSP staffing shapes local job openings show that program design choices ripple into real employment patterns, and the joint employer MSP staffing DOL framework will read those patterns as evidence of who truly controls the work.
Practical risk mitigation: redesigning MSP contracts and boundaries of control
Risk mitigation under the new joint employer MSP staffing DOL framework does not mean abandoning MSP models; it means clarifying who controls what. The goal is not to pretend that staffing firms alone manage employees, but to align contractual language, operational practice, and documentation so that each employer’s role is accurate and defensible. That alignment reduces surprises if the department of labor later reviews your contingent workforce program.
On the contract side, work with legal and procurement to narrow reserved control to what the host employer genuinely needs for safety, security, and regulatory compliance. Replace broad rights to approve or reject any employee with more targeted standards tied to objective criteria, and let staffing firms retain primary responsibility for hiring and discipline. Where possible, express performance expectations as outcomes of work rather than directives about how staffing firms must manage employees or independent contractors.
Operationally, train hiring managers and on site supervisors on the boundaries of their role with temporary employees and contingent workers. Make it clear that staffing firms own employment decisions, while the host employer focuses on defining the scope of work, monitoring results, and maintaining a safe workplace. Document these boundaries in playbooks, VMS user guides, and manager training materials, so that your real world practices match the story your agreements tell about employer status.
For independent contractor engagements, build a separate channel with its own contractor classification review, approval workflow, and documentation. Independent contractors should not be subject to the same day to day control as employees, and they should not be treated as interchangeable with temporary staffing resources in the VMS. Clear separation between employees, temporary workers, and independent contractors will help you navigate the factor test for joint employment and reduce the risk that all categories collapse into one employment relationship.
Compliance management as an MSP service line: building a defensible program
Compliance management is no longer a back office feature of MSP staffing; it is a core service line that shapes how regulators view your employment ecosystem. Under the joint employer MSP staffing DOL framework, enterprises will increasingly expect MSPs to provide structured support on wage hour compliance, contractor classification, and workers compensation coordination. The MSPs that succeed will be those that treat compliance as a shared operating picture for staffing firms, clients, and workers, not as a set of legal disclaimers.
Leading MSPs are already building governance councils that bring together HR, procurement, legal, and key staffing industry suppliers to review risk indicators. These councils examine time to fill, turnover, overtime patterns, and incident data for temporary staffing and contingent workers, looking for signs that host employers are exerting more control than agreements anticipate. When the department of labor evaluates joint employment, a documented history of such reviews can demonstrate that the enterprise and its staffing firms actively manage compliance, rather than ignoring it.
Technology also plays a central role in compliance management. VMS platforms can be configured to limit which users can change pay rates, approve overtime, or move employees between assignments, thereby reinforcing the intended division of control between staffing firms and firm clients. When those controls are combined with clear audit trails, they create evidence that the host employer respects the boundaries of employer status, even while maintaining necessary oversight of work outcomes.
Ultimately, the new joint employer MSP staffing DOL framework rewards programs that are honest about who does what and that document those choices carefully. Compliance management becomes a continuous process of aligning agreements, operations, and data, rather than a one time legal review at contract signature. In this environment, the most valuable asset in an MSP program is not the signed SOW, but the ninetieth day of coverage.
Key statistics on MSP staffing and joint employer exposure
- According to Staffing Industry Analysts, contingent workers account for roughly 22 % of the average large enterprise workforce in the United States, which means joint employment rules now touch nearly a quarter of total labor capacity in many organizations.
- Data from the U.S. Bureau of Labor Statistics show that temporary help services employment has more than doubled compared with two decades ago, illustrating how temporary staffing has shifted from a cyclical buffer to a structural component of employment strategies.
- Research by the Economic Policy Institute has estimated that wage and hour violations can reduce affected workers’ earnings by thousands of dollars per year, which explains why the department of labor continues to prioritize joint employer enforcement in staffing arrangements.
- Industry surveys of MSP buyers often report that more than 60 % of programs now include some form of independent contractor management, increasing the importance of accurate contractor classification and clear boundaries between employees and independent contractors.
- Compliance benchmarking studies frequently find that enterprises with formal MSP governance councils experience significantly fewer adverse findings in labor audits than peers without such structures, suggesting that proactive oversight materially reduces joint employer risk.
FAQ on joint employer liability in MSP staffing programs
How does the DOL’s joint employer framework affect typical MSP staffing models ?
The DOL’s framework treats MSP arrangements as classic vertical joint employment scenarios, where staffing firms supply employees and host employers direct daily work. If your managers set schedules, influence pay, and supervise temporary workers, the department of labor may view your organization as a joint employer alongside the staffing agency. That shared status can create liability for wage hour compliance, leave obligations, and other employment law duties.
Can contract language alone prevent a joint employer finding in an MSP program ?
Contract language helps, but it cannot override the reality of how work is organized and controlled. The DOL will look at both what agreements say and how staffing firms, clients, and employees actually behave in practice. If host employers exercise significant control over employment conditions, carefully drafted contracts will not fully shield them from joint employer status.
Why is reserved control in MSP contracts such a concern under the proposed rule ?
Reserved control refers to rights that a client holds in agreements, even if it rarely uses them. Under the proposed rule, those reserved rights can still count as evidence of joint employment, because they show that the host employer could influence hiring, firing, or pay if it chose to. Narrowing reserved control to what is operationally necessary can therefore reduce joint employer exposure.
How should enterprises treat independent contractors within MSP programs to manage risk ?
Enterprises should route independent contractors through a distinct review and approval process that tests contractor classification against legal standards. Contractors should not be managed like employees or temporary staffing resources, and they should retain control over how they perform the work. Clear separation in contracts, workflows, and supervision helps prevent misclassification and limits joint employer arguments.
What practical steps can MSP program owners take now to strengthen compliance ?
Program owners should audit MSP contracts for broad control clauses, review VMS configurations for points where managers influence employment conditions, and train supervisors on appropriate boundaries with temporary employees. Establishing a governance council that includes HR, procurement, legal, and key staffing firms can create ongoing oversight of contingent workforce risks. Documented reviews and aligned practices will put the program in a stronger position if the department of labor later examines joint employment questions.