A procurement lead at a Douglasville packaging company sent us her proposed staffing agreement last spring and asked us to take a look before she signed. The contract was 11 pages. The co-employment section was half a paragraph.
That paragraph said the agency was the "sole employer of record" for all placed workers and that the client had no employment relationship with any temporary personnel. She asked whether that protected her company.
It doesn't. Not the way she was thinking.
A staffing contract's co-employment clauses determine which party absorbs liability when a claim arises. The ones worth requiring: fault-based mutual indemnification, a worker direction clause that defines the client-agency supervision split, an assignment duration clause with a convert-or-exit decision point, and an insurance verification requirement naming the client as certificate holder. The ones worth refusing: indemnification language that holds either party harmless regardless of fault, a "sole employer" declaration with no operational support, and any clause giving the client unilateral authority to extend assignments indefinitely without a review.
What the 'Sole Employer' Clause Actually Does
The "sole employer" language shows up in almost every staffing agreement. It's there to make clear that placed workers are on the agency's payroll, not the client's. And that's accurate. The agency runs payroll, files the W-2, carries workers' compensation, and manages statutory benefits. The client doesn't.
But "sole employer of record" is an employment classification, not a liability shield.
Courts and federal agencies don't look at who signed the W-2 when evaluating a co-employment claim. They look at who actually ran the work. Who gave the worker daily instructions. Who decided when the worker's hours started and ended. Who told the worker to stay late on a Thursday because a shipment ran over.
The DOL's proposed FLSA joint employer rule (published April 22, 2026, comment period closed June 22) makes this explicit. Its four-factor test asks whether the potential joint employer hires or fires workers, supervises and controls schedules or conditions, determines pay rates, and maintains employment records. A client company that directs daily tasks on the floor can satisfy multiple factors while the contract says "sole employer" on page 3.
None of that makes the clause worthless. A well-drafted sole employer declaration, paired with an operational section that clarifies what supervision the agency handles, does reduce the risk of ambiguity if a claim arises. The problem is treating it as the end of the co-employment conversation rather than the beginning of it. We've seen clients walk into a claim confident they were protected by that clause, and discover that the clause didn't speak to what actually happened on their floor.
How Indemnification Should Be Written (And What Makes It One-Sided)
The indemnification section is where most agreements get it wrong, and it's also where the real liability exposure lives.
Standard national template language often includes a clause that holds the agency responsible for any claim arising from the engagement, without regard to which party actually caused the problem. That language leads to this scenario: a client's floor supervisor mishandles a performance conversation with a placed worker, the worker files a harassment claim, and the agreement points to the agency to handle the defense, even though the agency had nothing to do with the conversation.
The reverse version shows up too. Some client-drafted templates hold the agency harmless for any claims that come from the client's own worksite decisions. Either structure is a problem.
A fair indemnification clause runs both directions and ties liability to fault. The agency indemnifies the client for harms that stem from the agency's own acts or omissions: placement errors, inaccurate credential verification, payroll tax failures, workers' compensation non-compliance. The client indemnifies the agency for harms that stem from the client's own acts or omissions: worksite conditions the client controls, supervisory decisions made by the client's staff, and labor law violations that come from how the client directs work on the floor.
Georgia courts treat indemnification obligations as requiring clear, specific language to be enforceable. A clause saying "client shall indemnify agency for all claims arising from any placed worker's activities at client's facility" is broad enough to create disputes about whether the clause covers situations the parties never discussed. Specificity is what makes it useful.
When you're reviewing a proposed agreement, look for whether the indemnification clause names categories of liability on each side. If it's written in a single direction, or if it uses catch-all language, that's the clause to bring back to the agency before signing.
The Work Direction Clause: Where Most Agreements Fall Short
Most staffing agreements are explicit about who employs the worker on paper. They're nearly silent about who can tell the worker what to do on the floor.
That silence is where co-employment exposure builds.
A work direction clause defines the boundary between what the client can communicate directly to placed workers and what has to go through the agency. Three things it should address explicitly.
Performance management. If a placed worker isn't meeting production standards, the client's site contact tells the agency, not the worker directly. The agency handles any counseling, discipline, or assignment change. What this looks like in practice: your floor supervisor flags a performance concern to your FNSG site contact by end of shift, and we handle the conversation. It adds one step to a process most supervisors do automatically. It matters enormously if a termination claim arises later.
Removal requests. If a client wants a specific worker pulled from an assignment, that request goes to the agency as a request to reassign. The client doesn't deliver that message to the worker directly. A client company that tells a placed worker their assignment is over has made an employment decision that belongs to the agency, and courts treat that as a meaningful indicator of joint employer status.
Schedule changes. Shift adjustments, overtime requests, and scheduling modifications for placed workers go through the agency's scheduling contact, not through the client's floor supervisors directly. Task-level instructions during a shift are fine. Managing the employment relationship as if the worker reports directly to you is what creates the exposure.
The tighter this clause is drafted, the less ambiguous the situation is if a claim comes up later. We've started adding an operational annex to our agreements that lists the communication protocol by scenario, not just the general principle. It takes a day to negotiate and prevents months of confusion.
Assignment Duration and Conversion Language
This is the clause most clients skip negotiating, and the one we end up wishing they had addressed.
Long-duration placements with no defined review point carry quiet risk. A placed worker who's been on your floor for 14 months looks, to a federal agency evaluating a wage claim, like someone whose real employer might be the client regardless of what the agreement says. The length alone doesn't trigger joint employer status under any current standard. But it builds the factual record that supports the argument, and across our Georgia accounts, we've seen claim narratives where assignment length became a meaningful detail in the record.
An assignment duration clause with a conversion review point addresses this by design. It says that any assignment running past a defined threshold triggers a mutual review to decide whether the role should convert to a direct hire, continue under the current structure, or close out.
Ninety days is a common threshold. One hundred eighty days is also workable for roles where the work genuinely demands longer temp arrangements. The point isn't to force conversions; it's to make the decision actively rather than letting the assignment run indefinitely by default.
The temp-to-perm conversion fee schedule should be in the same clause. The standard structure is 10% to 20% of first-year base compensation, sliding down based on hours already worked as a temp, reaching zero somewhere between 480 and 720 hours (roughly 12 to 18 weeks of full-time work). If the agreement is silent on conversion fees, you'll negotiate them at the moment you've decided you want to hire someone, which is the worst possible time for that conversation.
One thing worth being honest about: shorter assignment durations don't function as a legal safe harbor from co-employment exposure. The actual-control analysis applies on day 30 the same way it does on day 300. The review clause helps you make active decisions; it doesn't eliminate the exposure by itself.
Clauses Worth Crossing Out Before You Sign
A few clause types show up in standard agreements often enough that it's worth knowing what you're looking at.
Broad indemnification regardless of fault. Any clause that holds one party responsible for claims arising from the other's conduct, without tying liability to which party actually caused the problem, should be rewritten before signing. This is the most common problematic clause we see in national-template agreements that clients bring to us for review. The fix is specific language: each party indemnifies for their own acts, not each other's.
"Sole employer" declaration with no operational section. The declaration itself is fine. The problem arises when it stands alone, with no worker direction clause and no section defining how supervision actually works. A standalone declaration is an attempt to disclaim co-employment legally without addressing it operationally, and it won't hold up the same way a complete agreement does.
Open-ended assignment extension by either party unilaterally. Assignments that can be extended indefinitely without requiring mutual consent, or without triggering any review, create a long-term placement arrangement by default. Push for language requiring mutual written agreement to extend beyond the initial assignment period, with a conversion review at the defined duration threshold.
Client right to terminate individual workers directly. If the agreement gives the client company authority to end a specific worker's assignment without going through the agency, it places an employment decision with the client that belongs to the agency. Courts have treated unilateral client termination authority as a meaningful joint employer indicator in wage and hour cases. Requests to remove a worker from an assignment should go to the agency as a staffing request, not to the worker.
For more on how these clauses fit into a complete staffing agreement, the staffing agency SLA guide covers fill rate targets, replacement guarantees, markup transparency, and the full contract structure. The co-employment risk guide for Georgia employers gets into the 2026 NLRB and DOL regulatory shifts and how the actual-control analysis works across specific types of claims.
If you're reviewing a proposed staffing agreement in Georgia and want to see how we structure our co-employment language before you sign, Schedule a Call. We staff warehouse, recycling, light industrial, and hospitality operations across Gwinnett, Hall, Douglas, Cobb, Henry, and DeKalb counties and can walk through the contract clauses that matter before anything gets executed.
