W-2 vs. 1099 Locum Arrangements: What Employers Need to Know About Liability, Malpractice, and Termination

Ask a hospital administrator who's on the hook if a 1099 locum gets sued, and you'll usually get one of two answers. Either "not us, they're a contractor," or a long pause.

Both answers should worry you a little. The first one is often wrong. The second one means nobody has actually looked at the contract.

Most of what's written about W-2 versus 1099 locum tenens covers the clinician's side: taxes, benefits, take-home pay. That's useful if you're the one filling out the 1099-NEC. It tells you almost nothing about what you're exposed to as the employer signing the check. This is the employer-side version.

The quick answer

Classifying a locum as a 1099 independent contractor does not automatically protect your organization from malpractice liability. Courts in most states can still hold a facility vicariously liable for a contractor's negligence under the doctrine of apparent (or ostensible) agency, if the facility didn't clearly disclose the physician's independent contractor status to the patient.

Tail coverage responsibility is a negotiated contract term, not a default rule, and it shifts depending on how the arrangement ends. Termination rights differ sharply between W-2 and 1099 structures, but that gap narrows fast if a "1099" locum is actually functioning like an employee.

Here's what each of those means in practice.

1099 status doesn't end your malpractice exposure

The classic rule is that employers aren't vicariously liable for the negligence of a true independent contractor. That rule still exists. It just has a large, well-established exception that swallows a lot of it in healthcare: apparent agency.

Under apparent agency (sometimes called ostensible agency), a court can hold a hospital or clinic liable for an independent contractor physician's negligence if the patient reasonably believed the physician was an employee or agent of the facility, and the facility didn't put them on notice otherwise. Courts look at whether the facility "held itself out" as the provider of care: same badges, same intake paperwork, same scheduling system, no clear disclosure that the treating physician bills and practices independently. Illinois adopted this doctrine in Gilbert v. Sycamore Municipal Hospital, and versions of it now exist in the majority of states, including California, Pennsylvania, Texas, and Maryland.

In plain terms: if your patients can't tell the difference between your W-2 hospitalist and your 1099 locum, a court may decide the difference doesn't matter for liability purposes either.

This is separate from, and in addition to, your own corporate negligence exposure for how you vetted and credentialed the locum in the first place. Weak credentialing documentation gets discovered in litigation regardless of how the physician was classified for tax purposes. A credentialing process built for compliance, not just speed, is one of the few parts of this that's fully within your control before a claim ever exists.

The practical fix isn't complicated. Disclose independent contractor status in writing, at intake, somewhere the patient will actually see it. Document that disclosure. It won't eliminate apparent agency risk, but it's the single strongest fact pattern for defeating it.

Who pays for tail coverage depends on how you wrote the contract

Most malpractice policies today are claims-made, meaning they only cover claims filed while the policy is active, not claims tied to incidents that happened years earlier under a lapsed policy. When a claims-made policy ends, someone needs to buy an extended reporting endorsement, commonly called tail coverage, or claims from that coverage period go uninsured. Occurrence policies avoid this problem by covering any incident from the policy period regardless of when the claim surfaces, but they're less common in locum arrangements because they cost more upfront.

For W-2 physicians, tail responsibility is almost always spelled out in the termination section of the employment agreement, and it's frequently tied to why the relationship ended. A common structure: the employer covers tail if it terminates without cause, the physician covers it if they resign or are terminated for cause. Tenure sometimes affects it too, with longer-serving physicians getting more employer-paid tail coverage than someone six months in.

For 1099 locums working through a staffing agency, the agency typically carries a continuous claims-made policy that covers all current and past locums back to a fixed retroactive date. As long as the agency keeps renewing that policy, no individual tail purchase is needed. The risk shows up if the agency stops renewing, goes out of business, or if the locum was working directly with your facility rather than through an agency, in which case tail responsibility needs to be an explicit line in your contract rather than an assumption. Clarifying who provides malpractice coverage before the assignment starts, not after a claim arrives, is standard advice for a reason.

Either way, tail coverage is not the kind of detail to leave implied. Get it in writing, specific to the scenario (resignation, termination for cause, termination without cause, non-renewal), before anyone signs.

Termination looks nothing alike under each structure, until it does

W-2 physician employment agreements almost always include a notice period for termination without cause, commonly 60 to 180 days. Termination for cause is usually immediate but requires the employer to define "cause" narrowly enough to survive a dispute. If the reason for termination touches on clinical competence or conduct, and it followed a professional review action, the facility may have an obligation to report it to the National Practitioner Data Bank, a step that follows medical staff bylaws and peer review procedures, not the employment contract. Medical staff privileges and employment are legally separate tracks. Ending someone's employment doesn't automatically end their privileges, and pulling privileges triggers its own due process requirements under most hospital bylaws, regardless of how the physician was classified.

1099 independent contractor agreements are governed almost entirely by their own terms. Notice periods tend to be shorter, sometimes as little as a shift or two for locum assignments, and termination for breach can be immediate. Independent contractors generally fall outside protections like wrongful termination claims under most state employment statutes, unemployment insurance, and ADA coverage, because those protections attach to employees.

That gap closes fast under misclassification. If a "1099" locum works a fixed schedule you set, uses your EMR exclusively, follows your clinical protocols, and has worked solely for your facility for an extended stretch, a court, the IRS, or a state labor agency can disregard the 1099 label and treat the relationship as employment. States including California have been particularly aggressive here since AB 5, and the DOL has flagged healthcare specifically as an enforcement priority in recent years. When that happens, the termination protections you assumed didn't apply can suddenly apply retroactively, along with back taxes, unpaid overtime exposure, and benefits liability. The contract label is a starting point for a court, not the end of the analysis.

Before you sign: a five-point check

• Does the contract state, in writing, who pays for tail coverage under each termination scenario (resignation, for-cause, without-cause, non-renewal)?
• Is there a written patient-facing disclosure of independent contractor status, and can you produce it if asked?
• Does the day-to-day working relationship actually match the 1099 label, or does it look like employment in substance?
• Is medical staff privileging handled as a separate process from the employment or engagement contract, with its own notice and due process terms?
• Does the notice period reflect how much lead time your facility actually needs to cover the gap, not just a template default?

Most of this gets caught by thorough credentialing and documentation at the start of the relationship rather than a scramble at the end of it.

FAQ

Does 1099 classification protect a healthcare employer from malpractice liability?Not fully. Under apparent (ostensible) agency doctrine, courts in most states can hold a facility vicariously liable for a contractor physician's negligence if the facility didn't clearly disclose the contractor relationship to the patient.

Who pays for tail coverage when a locum tenens contract ends?It depends on the contract. For W-2 physicians, it's usually tied to whether termination was with or without cause. For agency-supplied 1099 locums, the agency's continuous claims-made policy typically eliminates the need for an individual tail, unless the agency stops renewing or the arrangement was direct rather than through an agency.

Can a hospital terminate a 1099 locum physician without notice?Generally yes, more easily than a W-2 employee, since 1099 terms are governed by the contract rather than employment statutes. But if the relationship functions like employment in practice, courts can disregard the 1099 label and apply employee protections anyway.

Does misclassifying a locum as 1099 create risk beyond back taxes?Yes. Reclassification can trigger unpaid overtime and benefits liability, unemployment insurance exposure, and in some states, wrongful termination exposure that wouldn't otherwise apply to a contractor.

Is medical staff privileging affected by whether a physician is W-2 or 1099?Not directly. Privileging runs through medical staff bylaws and peer review, separate from the employment or contractor agreement, and applies regardless of classification.

Getting the classification, coverage, and termination terms right before a locum starts is a lot cheaper than sorting it out after a claim. If you want a second set of eyes on how your current arrangements hold up, talk to DirectShifts, which supports both W-2 and 1099 staffing models depending on what actually fits your risk profile, unlike platforms built almost entirely around one classification. For more on evaluating staffing partners generally, see how DirectShifts compares to AMN, or browse the rest of the employer resources library.

‍