Who Is the Correct Defendant? CFMG, Wellpath, County, Clinician, Supervisor, or Another Entity?

Scope and warning#

This roadmap explains how the question of the proper defendant is approached in California and federal claims connected to correctional healthcare and healthcare employment. It does not decide who should be named in any particular case. Naming the wrong defendant, or leaving out the right one, can lose a claim or a deadline, and the analysis below is general.

The factual situation this roadmap addresses#

The following situations are invented for illustration.

A nurse working at a county juvenile facility receives pay statements from one company, uses an email account branded with a second name, and is disciplined by a supervisor whose signature block names a third. The family of a man who died in a county jail sees "Wellpath" on medical forms, while the county's contract names a different entity, and nobody can say who employed the clinician on duty. A former detainee's records show that a specialist referral waited weeks, and the rule governing referrals appears in a manual whose author is unclear.

Each situation asks the same question in a different form: which person or organisation does the law attach to this duty and this conduct?

Governing law#

Defendant rules vary by cause of action. None of the rules below transfers automatically from one claim to another; each is stated for the claim it governs.

• FEHA (California employment discrimination, harassment and retaliation). Discrimination coverage generally begins at five employees, while harassment protections reach workplaces with even one employee or independent contractor; public employers and statutory exceptions require their own analysis (Cal. Gov. Code §§ 12926(d), 12940(j); California Civil Rights Department, Employment guidance). Courts assess a disputed employer relationship with attention to actual control (Vernon v. State of California (2004) 116 Cal.App.4th 114). Separately, a qualifying business-entity agent may be directly liable for its own FEHA-regulated activity performed for the employer (Raines v. U.S. Healthworks Medical Group (2023) 15 Cal.5th 268); that does not mean every affiliate, payroll processor or contractor becomes the employer. Individual supervisors generally are not personally liable for discrimination (Reno v. Baird (1998) 18 Cal.4th 640) or retaliation (Jones v. Lodge at Torrey Pines Partnership (2008) 42 Cal.4th 1158), but an individual harasser may be liable for harassment (Cal. Gov. Code § 12940(j)). (Grade: statute/CRD guidance and published authorities; precise entity coverage fact-specific.)
• California wage law. Whether an entity "employs" a worker under the wage orders turns on control over wages, hours or working conditions, on suffering or permitting the work, or on the common-law employment relationship (Martinez v. Combs (2010) 49 Cal.4th 35). (Grade: Settled.)
• ADA employment claims (Title I). The statute reaches employers with fifteen or more employees (42 U.S.C. § 12111(5)(A)), and individual supervisors are not personally liable under it in the Ninth Circuit (Walsh v. Nevada Dept. of Human Resources, 471 F.3d 1033 (9th Cir. 2006)). (Grade: Settled in the Ninth Circuit.)
• Professional negligence and other California torts. An employer can be liable for an employee's torts committed within the scope of employment (Lisa M. v. Henry Mayo Newhall Memorial Hospital (1995) 12 Cal.4th 291); the clinician remains answerable for his or her own negligence. (Grade: Settled.)
• 42 U.S.C. § 1983 (federal civil rights). The defendant must have acted under color of state law (42 U.S.C. § 1983); a physician under contract to provide medical care to people in state custody acts under color of state law (West v. Atkins, 487 U.S. 42 (1988)). A local government is answerable only for its own policy, custom or practice, not merely because it employed a wrongdoer (Monell v. Department of Social Services, 436 U.S. 658 (1978)), and the Ninth Circuit applies the same framework to private entities acting under color of state law (Tsao v. Desert Palace, Inc., 698 F.3d 1128 (9th Cir. 2012)). A single decision by an official with final policymaking authority can be such a policy (Pembaur v. City of Cincinnati, 475 U.S. 469 (1986)); state law determines who holds that authority (City of St. Louis v. Praprotnik, 485 U.S. 112 (1988)). (Grade: Settled; application to private contractors Prevailing in the Ninth Circuit.)
• State-law damages claims against a county. The Government Claims Act usually requires presentation of a covered money-or-damages claim before suit (Cal. Gov. Code §§ 905, 911.2, 945.4), subject to claim-specific exclusions and exceptions. FEHA causes of action against public employers are not subject to the ordinary Government Claims Act presentment requirement (Snipes v. City of Bakersfield (1983) 145 Cal.App.3d 861), although FEHA/CRD administrative exhaustion must be separately considered; related non-FEHA tort claims may still require presentment. The Act defines public "employee" without independent contractors (Cal. Gov. Code § 810.2). State notice-of-claim conditions cannot be imposed on federal § 1983 claims (Felder v. Casey, 487 U.S. 131 (1988)). (Grade: published Snipes, Felder; applications require theory-by-theory analysis.)
• Claims against a Chapter 11 debtor. Bankruptcy can materially alter who may be sued, how a claim proceeds, and what source of recovery remains available (11 U.S.C. § 362(a); 11 U.S.C. §§ 524(e), 1141(d)). Entity-specific bankruptcy analysis is addressed separately.

Why one set of events can point to several defendants

Each body of law answers the defendant question for its own purposes, and the answers do not have to match. FEHA may ask which entity employed the claimant, which qualifying business-entity agent engaged in a FEHA-regulated function, and who personally committed actionable harassment (Raines; Reno; Jones). California wage law asks who controlled wages, hours or working conditions. Negligence law asks who owed and breached a duty of care, and whether the person who acted was an employee acting within the scope of employment. Section 1983 asks who acted under color of state law and, for an organisation, whether its own policy or custom caused the violation. The Government Claims Act asks whether the defendant is a public entity or public employee, because that decides whether a written claim had to come first.

Because the tests differ, the same company can be a proper defendant on one claim and an improper one on another. Take an invented example. A clinician employed by a private medical group treats a detainee in a county jail under a contract between the county and the group. On a negligence theory, attention falls on the clinician and on the clinician's employer (Lisa M. v. Henry Mayo Newhall Memorial Hospital (1995) 12 Cal.4th 291). On a § 1983 theory, the clinician may be answerable for his or her own conduct (West v. Atkins, 487 U.S. 42 (1988)), while the medical group and the county are each answerable only for their own policy or custom (Monell v. Department of Social Services, 436 U.S. 658 (1978); Tsao v. Desert Palace, Inc., 698 F.3d 1128 (9th Cir. 2012)). On a covered state-law tort damages claim against the county, a written government claim generally comes first (Cal. Gov. Code §§ 911.2, 945.4); this is not a universal condition of every California claim against a county, and FEHA and § 1983 have distinct rules (Snipes; Felder). Because the statutory definition of a public employee excludes independent contractors (Cal. Gov. Code § 810.2), whether and how a claim-presentation or immunity rule concerns contractor staff is a separate, theory-specific question. (Grade: Settled.)

Contracting out does not remove the public body's own obligations. The Supreme Court has said that contracting out prison medical care does not relieve the State of its constitutional duty to provide adequate medical treatment to those in its custody (West v. Atkins, 487 U.S. 42, 56 (1988)). That describes the State's duty. It does not by itself make a county liable for a contractor's act, which on a § 1983 theory still requires the county's own policy or custom (Monell v. Department of Social Services, 436 U.S. 658 (1978)). (Grade: Settled.)

Elements of the claim#

This page covers no single claim. In every claim, the defendant element is the same question asked five ways:

1. Who formally employed the person? The entity on the payroll, the offer letter and the tax forms.
2. Who performed the disputed act? The clinician, supervisor, administrator or department that actually did it.
3. Who held authority over the disputed decision? The person or body whose approval was required (Roadmap 005).
4. Who contracted to perform the relevant function? The party to the county contract or the management services agreement.
5. Which legal theory attaches that act to that defendant? Employment statute, respondeat superior (Lisa M. v. Henry Mayo Newhall Memorial Hospital (1995) 12 Cal.4th 291), § 1983 individual or entity liability, contract, or bankruptcy procedure.

The five answers may name five different parties. A defendant belongs in a claim only where the fifth question connects it to the first four.

Working through the five questions: an illustration

Return to the invented nurse described above. Pay statements come from one company, the email account carries a second name, and the supervisor who signed the discipline uses a signature block naming a third. The five questions sort those clues.

Who formally employed the nurse? California requires each wage statement to show the name and address of the legal entity that is the employer (Cal. Lab. Code § 226, subd. (a)(8)). That line, read for every pay period at issue, is usually the best single starting record. The W-2, the offer letter and the personnel file should agree with it; where they do not, the disagreement is itself a fact to record.

Who performed the disputed act? The supervisor did, and the supervisor's own employer may be a different company. A decision made by someone on another company's payroll is a common sign that a joint-employment question exists. It does not answer that question.

Who held authority over the decision? Discipline policies, approval emails and human-resources records show whose sign-off was required. Roadmap 005 sets out how to trace that chain.

Who contracted to perform the function? The county contract in force on the date of the discipline names the contracting party. It may differ from both the payroll entity and the supervisor's employer, for example where a contractor works through a professional corporation or a staffing company.

Which theory connects an act to a defendant? For a FEHA discrimination claim, the question is which entity or entities were the employer under a test that looks at the whole relationship (Vernon v. State of California (2004) 116 Cal.App.4th 114); the supervisor is not personally liable for discrimination (Reno v. Baird (1998) 18 Cal.4th 640). For FEHA harassment, the supervisor can be personally liable (Cal. Gov. Code § 12940, subd. (j)(1), (3)). For a wage claim, the question is who controlled wages, hours or working conditions (Martinez v. Combs (2010) 49 Cal.4th 35). For an ADA Title I claim, the employer must have fifteen or more employees (42 U.S.C. § 12111(5)(A)).

The first four answers are facts collected from records. The fifth is a legal question, and it can come out differently for each claim. The illustration shows a method; it does not show who would be liable on any real facts.

Potentially relevant defendants#

Individuals: clinicians, supervisors and administrators

Under § 1983 there is no vicarious liability: each defendant, whatever the title, is liable only for his or her own misconduct (Ashcroft v. Iqbal, 556 U.S. 662, 676 (2009)). A supervisor can be liable where personally involved in the violation, or where there is a sufficient causal connection between the supervisor's own wrongful conduct and the violation (Starr v. Baca, 652 F.3d 1202, 1207 (9th Cir. 2011)). A title, a place on an organisational chart or a copy line on an email is not that connection. (Grade: Settled.)

The California employment statutes divide differently. Individual supervisors are not personally liable for FEHA discrimination or retaliation, but can be for harassment, as set out under Governing law. California wage law permits personal liability under specified provisions only where § 558.1's requirements are met: the covered non-employer defendant must be a natural person who is an owner, director, officer or statutory managing agent and who violated or caused a covered wage-and-hour violation (Cal. Lab. Code § 558.1(a)–(b); Usher v. White (2021) 64 Cal.App.5th 883). A managerial title alone is not proof of prohibited conduct, but substantial operational oversight or influence on a wage policy can support causation even without personally issuing every paycheck (Espinoza v. Hepta Run, Inc. (2022) 74 Cal.App.5th 44); Usher illustrates the defense where the individual lacked sufficient involvement. (Grade: 2025 statutory reproduction and published opinions through identified reproductions; current official codification and complete negative history not independently authenticated.) In professional negligence, the clinician remains answerable for his or her own care whatever the employer's liability (Lisa M. v. Henry Mayo Newhall Memorial Hospital (1995) 12 Cal.4th 291).

When an individual's name is not known, two procedural rules matter. California allows a defendant whose name is unknown to be sued under a fictitious name, with the true name substituted when it is discovered (Cal. Code Civ. Proc. § 474); courts have required that the plaintiff was genuinely ignorant of the defendant's identity or of the facts giving rise to the claim (Woo v. Superior Court (1999) 75 Cal.App.4th 169). In federal court, Rule 15(c)(1)(A) also preserves relation-back routes supplied by the applicable limitations law; under Rule 15(c)(1)(C), changing parties ordinarily also requires the same occurrence, notice to the newly named party within the Rule 4(m) service period without merits prejudice, and knowledge that a mistake about the party's identity led to the omission (Fed. R. Civ. P. 15(c)(1)(A)–(C); Krupski v. Costa Crociere S.p.A., 560 U.S. 538 (2010)). A California Doe substitution under Code Civ. Proc. § 474 and a federal Doe amendment are not automatically interchangeable. (Grade: federal rule confirmed on U.S. Courts website; application fact-specific.) Neither rule is a safety net for an unidentified defendant once a deadline approaches (Roadmap 008).

Organisations: employer, contractor, manager and parent

Corporate separateness is the starting point. A parent corporation is not liable for the acts of its subsidiaries merely because it owns them (United States v. Bestfoods, 524 U.S. 51, 61 (1998)). California disregards an entity's separate existence only where there is such unity of interest and ownership that the separate personalities no longer exist, and where treating the acts as those of the entity alone would produce an inequitable result (Sonora Diamond Corp. v. Superior Court (2000) 83 Cal.App.4th 523). (Grade: Settled.) Shared branding, shared officers or a shared address can form part of that inquiry, but none of them establishes it.

A management company stands in a different position from an owner. Its liability, if any, rests on what it did or controlled. The management agreement shows the powers granted; personnel, policy and decision records show which powers were exercised, by whom and when. Joint-employer status under FEHA or wage law requires its own statute-specific control inquiry (Vernon; Martinez), not a label or parent-subsidiary relationship. Separately, Raines allows direct FEHA liability of an appropriate business-entity agent for its own regulated activities; an agency-services contract is a lead to investigate, not a finding of agency status or wrongdoing.

Public entities and their contractors

A county is a different kind of defendant. For covered state-law money-or-damages claims, a written claim must generally be presented to the public entity before suit (Cal. Gov. Code §§ 905, 911.2, 945.4), but that statement does not encompass FEHA causes against a public employer (Snipes v. City of Bakersfield (1983) 145 Cal.App.3d 861). FEHA administrative exhaustion is an independent requirement. Punitive damages are not available against a public entity (Cal. Gov. Code § 818). For § 1983, a county is answerable for its own policy, custom or practice, and a single decision by an official with final policymaking authority over the subject can be such a policy (Pembaur v. City of Cincinnati, 475 U.S. 469 (1986); City of St. Louis v. Praprotnik, 485 U.S. 112 (1988)). Contracting out medical care does not remove the county's own constitutional obligations (West v. Atkins, 487 U.S. 42, 56 (1988)), but liability for a contractor's act still runs through the county's own policy or custom, not through the contract alone. (Grade: Settled.)

Administrative prerequisites#

Defendant identity shapes the steps that must come before suit, but there is no universal naming/exhaustion rule. For a covered California public-entity tort claim, present a government claim to the legally responsible public entity under applicable requirements; a contractor's receipt does not automatically meet public-entity presentment (Cal. Gov. Code §§ 905, 911.2, 945.4). A FEHA claim against a public employer ordinarily follows the CRD charge/right-to-sue route instead of Government Claims Act presentment (Snipes; CRD Employment guidance), while federal Title VII/ADA employment claims follow the EEOC administrative process and charge-scope doctrines (42 U.S.C. §§ 2000e-5, 12117(a); Sosa v. Hiraoka, 920 F.2d 1451 (9th Cir. 1990)). Check the actual charge, named respondent, amendment history, agency notice, related-party theories and timely civil suit separately; the employee's employer, a business-entity FEHA agent, a county and a contractor should not be presumed identical.

A bankruptcy proof-of-claim debtor-selection rule and bar date cannot be inferred from branding or an unsourced docket summary. Earlier manuscript references to purported Wellpath bar-date documents (Dkts. 491 and 776) remain research leads: the cited claims-agent PDFs were inaccessible in this review and were not authenticated. Counsel should verify the actual notice, plan, debtor-specific claims-register treatment and any later orders before stating claimant classes, exact deadlines or filing consequences.

The naming rule for administrative charges has limits in both directions. The Ninth Circuit has allowed a Title VII suit against a party not named in the charge where that party was involved in the acts giving rise to the claims, or where the agency or the party itself should have anticipated that the party would be named (Sosa v. Hiraoka, 920 F.2d 1451 (9th Cir. 1990)). (Grade: Prevailing in the Ninth Circuit.) Those exceptions are argued case by case; they do not make it safe to leave an identifiable respondent out of a charge. They also do not create personal Title VII or ADA employment liability merely because an administrator participated in conduct, nor do they dispense with FEHA's distinct employer/agent tests or CRD exhaustion. Entity identity, actual notice, timeliness and legally permissible defendant classes must be examined separately.

Limitation periods#

This page states no limitation period. Changing the defendant can change the clock: a county claim, a § 1983 claim and a FEHA claim against the same events run on different periods with different triggers. Each is stated with its five components in Roadmap 008.

Evidence#

Records to obtain#

Lawful routes only. Employees and former employees may request their personnel records (Cal. Lab. Code § 1198.5), wage statement records (Cal. Lab. Code § 226, subd. (b)) and copies of signed employment instruments (Cal. Lab. Code § 432). Patients may request their own health records (Cal. Health & Saf. Code § 123110). Many county contracts and amendments may be requested under the California Public Records Act (Cal. Gov. Code § 7920.000 et seq.), subject to exemptions, redactions and access disputes; a public-record request is not a guarantee of production. Bankruptcy filings may be obtained from the bankruptcy docket or an operating claims-agent site, but the specific Epiq links cited below were inaccessible in this review. Preserve only lawfully possessed evidence, never circumvent security controls, and do not acquire other patients' health information or privileged employer/legal files outside authorized procedures. A lawful route to one document does not authorize redistribution of protected portions.

Favorable and adverse facts#

Favorable facts

• A document issued by the defendant entity that directly concerns the disputed act.
• Contemporaneous approval records showing who decided.
• Consistent identification of the same entity across payroll, contract and policy records for the same period.
• A wage statement naming the same legal entity as the defendant for the period at issue (Cal. Lab. Code § 226, subd. (a)(8)).

Adverse facts

• Records naming different entities at different times, with no document tying the relevant period to one of them.
• Reliance on branding, email domains or titles alone.
• A defendant shown by authenticated case records to have been a Chapter 11 debtor on the operative petition date, where the relevant claim's accrual, classification and any later plan provisions require bankruptcy-specific treatment; the inherited 11 November 2024 date is a docket-verification lead here, not a substitute for a certified entity record.
• An administrative charge or government claim that named a different party.
• A defendant first identified after a deadline, where the conditions for relation back are not met (Fed. R. Civ. P. 15(c)(1)(C); Cal. Code Civ. Proc. § 474).

Likely defenses#

• The defendant was not the employer, or did not make the decision.
• No action under color of state law, or no entity policy, for § 1983 claims.
• Failure to present a required government claim to the correct public entity for a covered state-law cause of action (Cal. Gov. Code § 945.4), without importing that defense into a FEHA or § 1983 count (Snipes; Felder).
• A respondent omitted from the administrative charge.
• Corporate separateness: ownership, affiliation or shared branding alone does not make a parent or affiliate liable (United States v. Bestfoods, 524 U.S. 51 (1998); Sonora Diamond Corp. v. Superior Court (2000) 83 Cal.App.4th 523).
• For a § 1983 supervisor: no personal involvement and no causal connection (Starr v. Baca, 652 F.3d 1202 (9th Cir. 2011)).
• For a defendant added later: the claim does not relate back under any applicable route, including Rule 15(c)(1)(A) and (C) or genuinely applicable California Doe law, and is untimely; check new-party notice, mistake, state relation-back and accrual before adopting the defense.
• For an identified debtor: the applicable period of automatic stay, a proven discharge or the operative plan/order may alter this claim; stay, discharge, debtor identity, insurance treatment and nondebtor relief are separate issues (11 U.S.C. §§ 362(a), 524(e), 1141(d); Harrington).

Causation#

Identity and causation travel together. The defendant's own conduct, decision or policy must connect to the injury (for § 1983 entity claims; Monell v. Department of Social Services, 436 U.S. 658 (1978)); naming an entity whose only link is a shared brand supplies no causal chain.

For individuals, causation is personal: a § 1983 defendant must have participated in, or have a sufficient causal connection to, the deprivation (Starr v. Baca, 652 F.3d 1202 (9th Cir. 2011)). For an employer sued in negligence on a respondeat superior theory, the question is whether the employee's act fell within the scope of employment (Lisa M. v. Henry Mayo Newhall Memorial Hospital (1995) 12 Cal.4th 291), not whether the employer itself caused the injury.

Damages and remedies#

Remedies depend on the claim and the defendant, and the claim roadmaps address them. Two points belong here. Naming an entity that is not responsible can leave a judgment against a party that is not liable, and a California public entity is not liable for punitive damages (Cal. Gov. Code § 818). Bankruptcy can also affect what source of recovery remains (11 U.S.C. § 362(a); 11 U.S.C. §§ 524(e), 1141(d)); entity-specific bankruptcy guidance is in development.

Discovery#

Defendant identity is itself a discovery subject: interrogatories asking each defendant to identify the employer of named clinicians and the author of named policies; corporate disclosure statements required by federal Rule 7.1 for their defined disclosure purposes (not a substitute for a historical ownership or joint-employer finding); and an organisational deposition on the entity's role.

In California, a deposition notice directed to an entity can require it to produce the officers, directors, managing agents, employees or agents most qualified to testify on described matters (Cal. Code Civ. Proc. § 2025.230); the federal counterpart is Rule 30(b)(6) (Fed. R. Civ. P. 30(b)(6)). Records held by people or companies that are not parties are obtained by subpoena (Fed. R. Civ. P. 45). Requests framed around a date and a decision, such as who employed the nurse on duty on a stated shift, tend to produce clearer answers than requests framed around a brand.

CFMG/Wellpath-specific relevance#

Bankruptcy and the identity of the defendant

Bankruptcy makes exact entity identity decisive. The automatic stay operates on actions against the debtor (11 U.S.C. § 362(a)). The discharge of a debtor's debt does not affect the liability of any other entity on that debt (11 U.S.C. §§ 524(e), 1141(d)). In the specific Chapter 11 nonconsensual nondebtor-discharge context, Harrington v. Purdue Pharma L.P., 603 U.S. 204 (2024), rejected a plan provision effectively discharging third-party claims without affected claimants' consent. The Court expressly reserved questions involving genuinely consensual third-party releases, what counts as consent, and certain other forms of orders; its holding is not a self-executing ruling on any Wellpath plan or defendant. (Grade: Supreme Court official slip opinion; plan-specific application unverified.)

Those rules keep three questions separate. Was the entity a debtor on the relevant date? That requires the filed petition, any amended debtor list, precise legal name, case number and later orders—not branding or a secondary chronology. Did a plan, confirmation order or other order release, channel or enjoin claims against particular non-debtors, and on what terms? That turns on the text of those documents, which this page does not interpret. Does the claim run against an entity in its own right, or only through a debtor? That is a merits question under the law governing the claim.

The documentary investigation on this site sets out the public records on these entities; this page does not restate or evaluate its conclusions.

Primary authorities#

Bankruptcy verification targets (inherited references, not independently authenticated here):

Related roadmaps#

CFMG and Wellpath Corporate Structure for Litigation Purposes; Identifying the Actual Decisionmaker; Statutes of Limitation, Administrative Deadlines and the Danger of Waiting; When a Private Correctional Healthcare Company Can Be Liable Under §1983; Monell Liability Against Private Correctional Healthcare Contractors.

What this page cannot do#

It cannot tell anyone whom to sue, whether a claim exists, or whether a deadline has passed. It does not establish the employer, contracting party or debtor status for any particular person or period. Where those questions matter, a licensed attorney should review the actual records.