Managing Co-Employment Risks in Contingent Workforce Programs: An Enterprise Compliance Guide

What Is Co-Employment in the Contingent Workforce?

Co-employment is a legal condition where two separate organizations both function as an employer of the same worker, sharing rights and obligations such as direction of work, discipline, and termination. In a contingent workforce program, the staffing supplier usually holds the formal employment relationship (payroll, benefits, tax withholding), while the enterprise client directs the work itself. Co-employment risk attaches when that direction crosses into territory the law treats as employer control.

The Joint Employer Standard Explained

Federal agencies use a control-based test to decide whether an enterprise has become a joint employer. In February 2026, the National Labor Relations Board reinstated its 2020 standard, which requires “substantial direct and immediate control” over essential terms of employment: wages, benefits, hours, hiring, discharge, discipline, supervision, and direction. Control that is indirect, sporadic, or contractually reserved but never exercised does not, on its own, meet that bar.

The Department of Labor proposed a parallel standard for the Fair Labor Standards Act, the Family and Medical Leave Act, and the Migrant and Seasonal Agricultural Worker Protection Act in April 2026. As of this writing, that rule remains a proposal rather than a final regulation, so wage and hour joint employer determinations still draw on a mix of agency guidance and court precedent. Confirm current status with counsel before relying on it, since rulemaking timelines shift.

The practical takeaway: the current federal posture rewards enterprises that can show their staffing suppliers, not internal managers, control scheduling, discipline, and pay. State law and individual court decisions can still apply a broader standard, so a favorable federal rule does not eliminate the need for operational discipline.

How Co-Employment Differs from Direct Employment and Independent Contracting

Three worker relationships are often confused enough that it is worth separating them clearly.

• Direct employment: your organization is the sole employer of record. You control the work and carry full liability for wage, tax, and benefit compliance.
• Independent contracting: the worker operates their own business and controls how the work gets done. Misclassifying an employee as a contractor creates its own wage and tax exposure, separate from co-employment.
• Co-employment: two organizations share employer-like control over the same worker, most often an enterprise client and a staffing supplier. Both can carry liability if a regulator or court finds the enterprise crossed the control threshold.

A contingent workforce program can touch all three relationships at once, which is exactly why the operational triggers below matter more than the label on the contract.

Key Co-Employment Risks for Modern Enterprises

In this section: unintended enrollment in benefit plans, wage and hour exposure under the FLSA, workers’ compensation and safety liability, and tax withholding and audit risk. Each risk grows with the size and tenure of your contingent workforce.

Unintended Benefit Plan Liability

Courts have found that workers labeled as contractors or agency temps qualified as common-law employees under ERISA and were owed access to retirement and welfare plans, most notably in the long-running Vizcaino v. Microsoft litigation. The lesson has held up for three decades: plan documents that define eligibility by worker label, rather than by the actual working relationship, create exposure the moment a contingent worker’s day-to-day treatment starts to resemble that of a direct employee. Retroactive plan participation claims can span years of contingent labor spend, not just the current engagement.

Wage and Hour Violations under FLSA

Wage and hour enforcement has intensified, not eased. The DOL’s Wage and Hour Division recovered more than $259 million in back wages for nearly 177,000 workers in fiscal year 2025, an average of $1,465 per worker and the highest annual recovery since 2019. Misclassification and joint employer findings are recurring fact patterns behind these recoveries. When an enterprise directs overtime, sets schedules, or approves pay rates for supplier-sourced workers, it can become jointly liable for unpaid minimum wage, overtime, and recordkeeping violations under the FLSA, on top of whatever the supplier owes.

Workers’ Compensation and Workplace Safety Exposure

Most states apply some version of a “dual employer” or “borrowed servant” doctrine to workers’ compensation. If your organization directs a contingent worker’s daily tasks, supervises safety practices, and controls the work environment, a state workers’ compensation board may treat you as a co-employer for coverage purposes, and in some cases extend the exclusive remedy protection (or the liability) that comes with it. OSHA applies a similar multi-employer worksite framework, which can hold the host employer responsible for hazards it controlled, independent of who signs the worker’s paycheck.

Tax Withholding and Audit Liabilities

The IRS uses a common-law test built around behavioral control, financial control, and the relationship between the parties to determine who the true employer is for tax purposes. An enterprise that dictates how, when, and where work gets done, provides the tools, and integrates the worker into its operations looks more like an employer than a client in the IRS’s eyes, regardless of what the staffing contract says. A reclassification finding can trigger back withholding, penalties, and interest, and it often surfaces during an unrelated audit rather than a targeted one, which makes documentation discipline a year-round requirement, not a once-a-year task.

Evaluating Your Co-Employment Risk Profile: Common Operational Triggers

Co-employment risk rarely comes from the staffing contract itself. It comes from the day-to-day behavior of managers who never see that contract. Three patterns account for most of the exposure we see in enterprise programs.

Direct Supervision vs. Outcome-Based SOW Oversight

Managing a contingent worker’s daily task list, correcting their work in real time, and running them through your internal performance process all look like direct supervision to a regulator. Outcome-based Statement of Work (SOW) engagements shift the conversation to deliverables and milestones instead, with the supplier’s own supervisor managing how the work gets done. The distinction is not cosmetic. It is the single biggest factor in most control-based legal tests.

Performance Reviews, Discipline, and Direct Offboarding

Placing a contingent worker into your standard performance review cycle, issuing written warnings directly, or making the call to end an engagement without routing it through the supplier all signal employer-level control. Even well-intentioned management, like praising a contractor in the same system used for full-time staff, can become evidence in a misclassification claim.

Providing Company Equipment, Email Addresses, and Perks

A contingent worker with a company email address, a badge that grants the same building access as staff, and an invitation to the holiday party looks, on paper, like an employee. None of these perks are inherently unlawful, but stacked together they build a fact pattern that undercuts the “independent supplier relationship” your contracts describe. Configurable access and identity policies, distinct from those used for direct staff, are one of the more overlooked ways to reduce this exposure.

Building an MSP and VMS Compliance Framework

The Role of Managed Service Providers (MSPs) in Mitigating Risk

A Managed Service Provider (MSP) sits between your organization and your supplier network, standardizing intake, onboarding, and offboarding so that no single manager can improvise a process that creates co-employment exposure. Workwell North America’s MSP model is technology-agnostic, meaning we operate on whatever VMS platform your organization already runs, including Beeline, so program governance is not tied to a single tool. The MSP layer gives you one point of accountability for compliance across every supplier, instead of leaving each business unit to manage risk on its own.

Vendor Management System (VMS) Configuration for Tenure Tracking

A Vendor Management System (VMS) is only as protective as its configuration. Tenure caps, automated alerts at 90 and 180 day thresholds, and mandatory supplier reassignment rules all reduce the chance that a contingent engagement quietly turns into a de facto permanent role. Talient, our proprietary VMS, builds these controls into requisition and worker lifecycle workflows so tenure limits are enforced automatically instead of tracked in a spreadsheet someone forgets to update.

SOW Governance: Shifting Control from Labor Hours to Deliverables

The strongest structural protection against co-employment is a genuine shift from hours-based staffing to deliverables-based Statement of Work management. That means contracts define outcomes, not headcount, the supplier’s own lead manages the work, and your organization pays for milestones rather than approving timesheets. Rogue, unmanaged SOW spend is one of the fastest ways a program loses this distinction, since informal task assignments tend to accumulate the same control markers as staffing engagements.

Co-Employment vs. Employer of Record (EOR): Structural Protection

When to Use an MSP vs. an EOR Solution

An MSP reduces risk by standardizing how you manage existing supplier relationships. An Employer of Record (EOR) removes the co-employment question for a given worker by becoming that worker’s legal employer outright, handling payroll, tax withholding, and statutory benefits directly. Enterprises typically reach for an EOR when hiring in a state or country where they have no legal entity, when converting a long-tenured contractor to a compliant arrangement, or when a role’s day-to-day control requirements make an outcome-based SOW impractical. If your organization is building the internal case for adding EOR to your program, our guide to making that case walks through the argument stakeholders usually need to see. For a look at how providers in this space compare, see our guide to the best EOR providers in 2026.

Operational Checklist: 5 Steps to Audit Your Contingent Workforce Today

Map Workforce Visibility & SOW Rogue Spend

Pull a complete inventory of every contingent worker and SOW engagement across every business unit, including any spend that never routed through procurement or your VMS. You cannot manage co-employment risk in a population you cannot see.

Audit Day-to-Day Managerial Control Protocols

Interview a sample of hiring managers about how they actually assign, correct, and review contingent workers’ work, not just what the policy says. The gap between policy and practice is where most exposure lives.

Enforce Strict Systemic Tenure Limits

Set a firm tenure ceiling for contingent engagements, configure your VMS to enforce it automatically, and require a documented business case and supplier or role change for any extension.

Audit Vendor & MSP Contractual Indemnification

Review supplier and MSP agreements for indemnification language covering misclassification, wage and hour claims, and benefit plan liability, and confirm the coverage actually applies to how the program runs today.

Standardize Offboarding and Technical Access Controls

Build a single offboarding checklist that revokes system access, email, and building credentials the same day an engagement ends, regardless of which supplier or manager initiated it.