https://kpsgill.com/research/cfmg-wellpath-california/roadmaps/005-decisionmaker/ · Roadmap 005

Roadmap 005Supporting roadmapBegin here

Identifying the Actual Decisionmaker

Law current as of
Last reviewed
Published
Not recorded on this page
Last modified
Not recorded on this page

Who this page is for

Readers who need to show who actually made or influenced an employment or care decision.

What question this page answers

Who made the decision, and what records show it?

What this page does not establish

That any decision was unlawful; identifying the decisionmaker is a step, not a conclusion.

OrientationWhat this page is, and when to act now

In plain words#

The person who delivers bad news is often not the person who decided it. A supervisor may hand over a termination letter that someone else approved. A human-resources office may run a leave process without any authority over medical questions. A medical director may recommend something without authority over employment. A county may monitor a contract without making any particular decision under it.

Many claims depend on who actually decided. This page breaks a decision into six stages, shows the records that tend to reveal each stage, and explains why titles and copied emails prove less than they seem to.

Urgent

Stop and get a lawyer now if a decision is still being made and could be influenced lawfully; a deadline may be near (Roadmap 008); or records that show the decision chain may be deleted under a routine retention schedule (Roadmap 007).

Deadline

Deadlines. Some claims subject to the California Government Claims Act have a claim-presentation period as short as six months (Cal. Gov. Code § 911.2), but not every claim involving a county is subject to that rule. FEHA/CRD, federal EEOC, contract and other claims have different prerequisites and clocks. The date of notice, the decision, implementation and actual injury may differ. Identify each possible cause of action and defendant before calculating deadlines; see Roadmap 008.

Scope and warning#

This roadmap explains a method for identifying who made a decision. It applies to employment decisions (discipline, leave, reinstatement, termination) and to clinical-administrative decisions (referrals, transfers, policy). It does not identify the decisionmaker in any actual event.

The factual situation this roadmap addresses#

The following situation is invented for illustration. A licensed vocational nurse at a county reentry program is removed from the schedule. The scheduler says the order came from "corporate". A regional manager signs the removal notice. An email chain shows a human-resources partner, a director of nursing and a county liaison copied. Weeks later, a different manager signs a letter describing the removal as the nurse's own resignation. Who decided, and when?

On this page — 21 sections
  1. Orientation
    1. In plain words
    2. Scope and warning
    3. The factual situation this roadmap addresses
  2. Working analysis
    1. Governing law
    2. Elements of the claim
    3. Potentially relevant defendants
    4. Administrative prerequisites
    5. Limitation periods
    6. Evidence
    7. Records to obtain
    8. Favorable and adverse facts
    9. Likely defenses
    10. Causation
    11. Damages and remedies
    12. Discovery
    13. CFMG/Wellpath-specific relevance
  3. Research depth
    1. Primary authorities
    2. Related roadmaps
    3. Research expansion — proving decision authority without guessing from titles
    4. What this page cannot do
    5. Important legal-information notice

Working analysisLaw, evidence and procedure

Governing law#

  • FEHA. A plaintiff alleging discrimination must show that the protected characteristic was a substantial motivating factor in the decision (Harris v. City of Santa Monica (2013) 56 Cal.4th 203), and a decision can be tainted where a biased person influenced the formal decisionmaker (Reeves v. Safeway Stores, Inc. (2004) 121 Cal.App.4th 95). (Grade: Settled.)
  • Federal statutes. The Supreme Court recognised an influenced-decisionmaker ("cat's paw") theory under a different federal employment statute (Staub v. Proctor Hospital, 562 U.S. 411 (2011)); whether and how it applies under each statute in this series is beyond the scope of this page. (Grade: Prevailing.)
  • § 1983 entity claims. An entity is answerable only for its own policy (Monell v. Department of Social Services, 436 U.S. 658 (1978)), and a single decision by an official with final policymaking authority over the subject can be that policy (Pembaur v. City of Cincinnati, 475 U.S. 469 (1986)); state law determines who holds the authority (City of St. Louis v. Praprotnik, 485 U.S. 112 (1988)). (Grade: Settled.)
  • Professional judgment. California Business and Professions Code §§ 2052 and 2400 and Medical Board guidance distinguish clinical discretion from nonclinical administration. The Board identifies clinical-competency hiring/firing, referral, treatment and certain practice-setting decisions as matters potentially implicating physician control. An administrative sign-off or management services agreement alone proves neither unlawful clinical interference nor the identity of the clinician whose judgment was actually used. Statutory exceptions and the precise acts require separate analysis. (Grade: Restriction established; application fact-specific.)

Why the decisionmaker matters to each kind of claim

Employment discrimination. FEHA cases are usually analysed in stages: the employee makes a basic showing, the employer states a legitimate reason, and the employee then has the chance to show that the stated reason was a pretext or that discrimination was the real reason (Guz v. Bechtel National, Inc. (2000) 24 Cal.4th 317). Each stage is about a particular decision and the people who made it. The employer's reason need not be wise or correct, only free of unlawful motive (Guz v. Bechtel National, Inc. (2000) 24 Cal.4th 317). For a FEHA discrimination claim within Harris, a protected characteristic must have been a substantial motivating factor; a proven same-decision defense prevents damages, backpay and reinstatement for that decision but does not erase liability and may leave appropriate declaratory or injunctive relief and discretionary reasonable fees and costs (Harris v. City of Santa Monica (2013) 56 Cal.4th 203). Do not extend that remedial holding automatically to FEHA retaliation, accommodation or another statute. (Grade: Settled for the discrimination question decided.)

Retaliation. A FEHA retaliation claim requires protected activity, an adverse action and a causal link between them (Yanowitz v. L'Oreal USA, Inc. (2005) 36 Cal.4th 1028). Proof of relevant knowledge is central, but must be traced through everyone who materially caused the decision: an innocent final signatory does not necessarily end a properly supported subordinate-influence theory (Morgan v. Regents of University of California (2000) 88 Cal.App.4th 52; Reeves v. Safeway Stores, Inc. (2004) 121 Cal.App.4th 95). Federal Title VII retaliation uses but-for causation (University of Texas Southwestern Medical Center v. Nassar, 570 U.S. 338 (2013)); the precise FEHA and other statutory causation instructions must be analyzed separately, not imported from Nassar or Harris without qualification. The question is who knew, who supplied what, and whether that information caused the action. (Grade: Claim-specific.)

Influenced decisions. Where a biased subordinate supplies the information or recommendation on which a formal decisionmaker acts, the subordinate's motive can be attributed to the decision in some circumstances. The Supreme Court framed the test under the federal statute before it in terms of proximate cause: an act by a supervisor motivated by bias and intended to cause the adverse action, which is a proximate cause of it (Staub v. Proctor Hospital, 562 U.S. 411 (2011)). An independent investigation by the decisionmaker does not automatically break that chain. Before Staub, the Ninth Circuit had recognised a similar subordinate-bias theory where the biased subordinate influenced or participated in the decision (Poland v. Chertoff, 494 F.3d 1174 (9th Cir. 2007)). California recognizes material participation in a FEHA decision, not merely the name on the termination letter: Hoglund v. Sierra Nevada Memorial-Miners Hospital (2024) illustrates reliance on an influential supervisor's account. The counterexample matters: Choochagi v. Barracuda Networks, Inc. (2021) rejected a cat-paw inference where the alleged retaliator was not shown to have influenced the termination decision. The operative question is a proved causal bridge, not a copied email or suspicious title (Reeves v. Safeway Stores, Inc. (2004) 121 Cal.App.4th 95). (Grade: Case- and statute-specific; precise reporter citation and later treatment require final cite check.)

Section 1983 entity claims. First identify a specific federal right and conduct under color of state law; a contract with a county does not by itself resolve whether a private entity's challenged action was state action. For private corporations, Tsao v. Desert Palace, Inc., 698 F.3d 1128 (9th Cir. 2012), requires both qualifying state action and an unconstitutional corporate policy/custom causing the injury; respondeat superior alone is insufficient. For municipal liability, the court determines final policymaking authority for the relevant subject under state law (Jett v. Dallas Independent School District, 491 U.S. 701 (1989); City of St. Louis v. Praprotnik, 485 U.S. 112 (1988)); discretion to approve personnel decisions is not necessarily final policy authority. Ratification is not mere awareness or failure to reverse: the final policymaker must approve both the subordinate decision and its basis (Christie v. Iopa, 176 F.3d 1231 (9th Cir. 1999)). (Grade: Settled framework; application to an entity/event unproved.)

Section 1983 individual claims. Each individual is answerable only for his or her own conduct (Ashcroft v. Iqbal, 556 U.S. 662 (2009)). The decision chain identifies who did what; Roadmap 003 explains how that connects to individual liability.

Elements of the claim#

This page covers no single claim. It supplies one element to many: the identity, authority and motive of the actual decisionmaker. The six stages:

  1. Originated. Who first raised the issue?
  2. Recommended. Who proposed the action?
  3. Reviewed. Who examined the evidence or recommendation?
  4. Approved. Who held, and used, the authority to decide?
  5. Communicated. Who told the affected person?
  6. Implemented. Who changed access, payroll, schedules or status?

These may be six different people, in more than one organisation. Two further questions complete the chain: who could have reversed the decision, and did the person said to be the decisionmaker change over time?

Reading the six stages

Originated. The first written mention is often an email, incident report, complaint, audit finding or chart note. The originator matters most where the claim is retaliation or influenced decision-making: a person with a motive who started the process can matter even if someone else approved the result.

Recommended. Recommendations are often written ("I recommend termination", "I suggest removing her from the schedule") and are frequently made by a supervisor or human-resources partner. A recommendation adopted without independent review is a common path for an influenced-decision theory.

Reviewed. Review can be real or nominal. Records of what the reviewer actually looked at, such as the investigation file, interview notes or the documents attached to the request, show which. A review that relied only on the recommender's summary leaves the recommender's account at the centre of the decision.

Approved. Approval is the stage most often confused with others. The approver is the person whose authority made the action happen, which is usually shown by a delegation-of-authority document, a policy, a job description or the approval record itself. A title alone does not show it.

Communicated. The person who signs the letter or delivers the news is easiest to identify and least likely to be the approver. Communication records still matter: their date can bear on timing, and their wording fixes the reason given at the time.

Implemented. Payroll changes, badge or system access changes and schedule edits show when the decision took practical effect and which organisation's systems carried it out. In a structure involving a professional corporation and a management company, implementation often runs through the management company's systems even where the decision belonged elsewhere.

Could reverse, and changes over time. Identifying who could reverse a particular employment action helps locate review authority; it does not alone establish who sets final government policy for § 1983. Changes in the identified decisionmaker or stated reason are facts requiring contemporaneous-source verification. Evidence that an employer's stated reason is false can, with the rest of the case, allow an inference of unlawful motive (Reeves v. Sanderson Plumbing Products, Inc., 530 U.S. 133 (2000)), and the Ninth Circuit has treated fundamentally different justifications for the same decision as raising a genuine factual dispute (Washington v. Garrett, 10 F.3d 1421 (9th Cir. 1993)). (Grade: Settled as to falsity; Prevailing as to shifting explanations.)

The invented example, stage by stage

Take the nurse removed from the schedule. On the facts given, the matrix might read like this, and the gaps are as informative as the entries.

Originated: unknown; "corporate" is a description, not a person. Recommended: possibly the director of nursing or the human-resources partner, both copied on the email chain; being copied proves neither. Reviewed: no record yet. Approved: unknown; the regional manager signed the notice, which shows communication, not authority. Communicated: the regional manager, on the date of the notice. Implemented: the scheduler, and whoever changed payroll and system access. Could reverse: unknown. Changes over time: the later letter describes a resignation, which conflicts with the removal notice.

That reading points to the records that would fill the gaps: the delegation document for schedule removals, the full email chain with metadata, the human-resources case file, and the payroll and access logs. It does not show who decided, why, or whether anything unlawful occurred.

Potentially relevant defendants#

Identify legally distinct defendants by cause of action, not everyone appearing in a decision chain. Under FEHA, ordinary individual supervisors are generally 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); harassment and other independent torts require separate analysis. A qualifying business-entity agent with at least five employees that itself carries out FEHA-regulated activities for an employer may be directly liable under Raines v. U.S. Healthworks Medical Group (2023) 15 Cal.5th 268. Mere corporate affiliation or processing a form does not establish those facts. For § 1983, distinguish personally participating state actors from entities subject to policy/custom and state-action requirements (Roadmap 003).

Administrative prerequisites#

For Title VII and ADA employment claims, the administrative charge ordinarily identifies the respondent and frames the conduct investigated (42 U.S.C. §§ 2000e-5(e)(1), (f)(1), 12117(a)). A civil suit against an unnamed entity can raise an exhaustion/notice dispute; recognized exceptions and the charge's reasonable investigative scope are fact- and circuit-specific, so naming is not an automatic universal bar or safe harbor. Preserve the actual charge, amendments, intake narrative, notices, and the exact legal names of proposed respondents; Roadmap 008 covers filing clocks.

Limitation periods#

This roadmap does not compute a deadline. Record separately the internal approval date, effective date, unequivocal notice date, any later reconsideration or implementation, administrative charge date, and receipt date. Different claims apply different accrual and exhaustion rules; a hidden internal decision may not be the operative notice, and later consequences do not automatically restart time (Roadmap 008).

Evidence#

Decisionmaker Matrix.

StageName and titleOrganisationDateRecord showing itAuthority source
Originated
Recommended
Reviewed
Approved
Communicated
Implemented
Could reverse

Documentary signals: complete email approval chains (who wrote "approved", not who was copied); HR case files; document metadata (author, created, modified, time zone, export method); personnel records; medical-director communications; dated job descriptions; contemporaneous delegation policies; executed bylaws and management agreements; organisational charts; meeting minutes; termination forms; electronic access and payroll-change logs. For every matrix entry record direct observation / attributed allegation / inference, exact custodian, exhibit identifier, time-zone normalization and whether the underlying document was reviewed in full. Missing documents remain "not established", not negative proof.

Inference limit

What this fact does not prove

  • Being copied on an email does not prove participation in the decision.
  • A title such as "director" or "regional manager" does not prove authority over this decision.
  • Signing the notice proves who communicated it, not necessarily who approved it.
  • A management agreement that grants a power does not prove the power was used here.
  • A county liaison on the thread does not prove the county decided.
  • A Wellpath email domain does not prove which entity the sender acted for.

What would change the analysis

  • A delegation document or bylaw assigning authority to a different person or body.
  • Metadata or a later admission showing the recorded approver was not the real decider.
  • Testimony that the decision was reversed or re-made by someone else.
  • A court finding identifying the final policymaker.

Records to obtain#

Cal. Labor Code § 1198.5 provides qualifying current and former employees access to maintained personnel records relating to performance or grievances, including education/training records under SB 513 effective January 1, 2026; it does not guarantee the whole HR investigation, every manager email, or records exempted by statute. The request right has statutory conditions (including exclusions and a litigation-pendency suspension for covered personnel matters). Cal. Labor Code § 432 addresses instruments the employee signed relating to obtaining/holding employment; § 226(b) concerns specified wage/employment records, not every internal payroll database. County public records may be requested under the CPRA (Gov. Code § 7920.000 et seq.), subject to confidentiality, privacy and exemption rules; private vendors' internal records are not automatically public. Formal discovery and preservation may be necessary for complete chains (Roadmap 007).

When tracing clinical decisions, do not export patient charts, access records outside authorized care duties, or circulate identifiers merely to demonstrate management involvement. Counsel should evaluate HIPAA/California confidentiality and lawful discovery or authorization; a minimum-necessary de-identified decision log may suffice for initial analysis. Preserve source existence and custodian without acquiring records unlawfully.

Evidence

Evidence to look for

  • The delegation-of-authority document or policy that governs the type of decision, in the version in force on the date.
  • The complete email chain, including forwarded and earlier messages, with dates and the words used by each participant.
  • What the reviewer actually had: the investigation file, interview notes and attachments.
  • The first written statement of the reason, and every later statement of it.
  • Payroll-change, schedule and system-access logs showing when the decision took effect and who entered it.

Favorable and adverse facts#

Favorable facts

  • An approval record made at the time, naming the approver.
  • Consistency between approval, notice and implementation—probative of the true chain but not inherently favorable to either side.
  • Statements by the approver about the reason, made at the time.
  • Evidence that the approver knew of the protected activity before deciding (Morgan v. Regents of University of California (2000) 88 Cal.App.4th 52).
  • Different reasons given for the same decision at different times (Washington v. Garrett, 10 F.3d 1421 (9th Cir. 1993)).

Adverse facts

  • Only the communicator is identifiable.
  • Shifting accounts of who decided, without records to resolve them.
  • Records deleted under a routine schedule before preservation was requested.
  • A documented genuinely independent review using evidence untainted by an allegedly biased recommender, and a supported alternative reason that existed at decision time (Choochagi; contrast Hoglund).
  • A delegation document placing authority with someone the claim does not reach.

Likely defenses#

  • The decisionmaker had no knowledge of the protected activity or condition.
  • The decision was independent of any biased input.
  • The named person lacked final authority (for § 1983 entity claims).
  • The decision was a professional judgment, not an employment action, or the reverse.

These defenses test the chain stage by stage. No knowledge matters to direct retaliation causation (Morgan v. Regents of University of California (2000) 88 Cal.App.4th 52), but does not substitute for checking knowledgeable material contributors. A documented independent decision should be tested against what the reviewer actually examined and whether a possibly biased source shaped the evidentiary file; a formal HR investigation is not automatically a superseding cause under Staub (562 U.S. 411 (2011)). Choochagi shows the counterargument where a concrete influence chain was not proved. Same decision anyway limits FEHA remedies where proved (Harris v. City of Santa Monica (2013) 56 Cal.4th 203). No final authority answers a § 1983 entity claim unless ratification or delegation of policymaking authority is shown (City of St. Louis v. Praprotnik, 485 U.S. 112 (1988); Christie v. Iopa, 176 F.3d 1231 (9th Cir. 1999)).

Causation#

Causation must be proved for the specific actionable decision. A motive held by an outsider without material influence ordinarily does not supply the link; a biased individual who materially shaped the decision may (Reeves v. Safeway Stores, Inc. (2004) 121 Cal.App.4th 95; Staub v. Proctor Hospital, 562 U.S. 411 (2011)). For the FEHA discrimination theory decided in Harris, the protected characteristic must be a substantial motivating factor (Harris v. City of Santa Monica (2013) 56 Cal.4th 203). Do not substitute that exact instruction for FEHA retaliation, Labor Code whistleblower, federal Title VII retaliation, or § 1983 without examining the controlling claim-specific standard.

Damages and remedies#

Not addressed here; see the claim roadmaps.

Discovery#

Interrogatories identifying every person at each stage; requests for approval chains with metadata; depositions of the approver and the communicator; an organisational deposition on delegation of authority.

Human-resources investigations raise a privilege distinction: routine factual inquiries, underlying preexisting evidence, counsel communications and attorney work product are not interchangeable. Wellpoint Health Networks, Inc. v. Superior Court (1997) 59 Cal.App.4th 110 discusses an at-issue waiver where an employer affirmatively relies on adequacy of an attorney investigation as a defense; counsel involvement alone neither immunizes all facts nor automatically waives every privileged communication. Counsel should test asserted privilege, purpose, actual defense reliance and waiver scope before requesting production. Stage-specific discovery (what the approver actually reviewed) is more informative than a broad demand for all communications.

CFMG/Wellpath-specific relevance#

Where a professional corporation contracts for management services, a decision chain can cross organizations: physicians may exercise clinical authority while management personnel perform administrative tasks. An inherited draft attributes an "administrative services to professional entities" description to bankruptcy Bar Date Notice Dkt. 776 and Order Dkt. 491, with dates January 2, 2025 and December 18, 2024, respectively. Those document identities, dates, quotation and entity coverage were not independently authenticated during this revision and remain research leads, not established findings. Obtain the complete signed docket entries and governing agreements before quoting, attributing or relying on them. No branding, email domain, affiliation or agreement by itself proves which entity actually exercised a decision power.

A county can appear as contract monitor, site-access authority, custody provider, purchaser of services or actual decision participant. Notice to a county liaison does not alone prove county employment control, clinical direction, state action for every private act, or municipal policy. For a § 1983 county claim, the identified constitutional deprivation must be causally linked to a county policy/custom, a relevant final policymaker's act, or a qualifying ratification of decision and basis (Pembaur v. City of Cincinnati, 475 U.S. 469 (1986); Christie v. Iopa, 176 F.3d 1231 (9th Cir. 1999)). Preserve evidence tending to disprove county involvement as carefully as favorable evidence.

Research depthAuthorities, related pages and limits

Primary authorities#

Cases 23

  • Unverified inherited bankruptcy docket lead—not an authenticated primary authority in this candidate: purported Bar Date Notice Dkt. 776 / Order Dkt. 491 and purported document URL (external site). Verify official docket/certified copies, parties, dates and quoted language before relying on it.
  • Monell v. Department of Social Services, 436 U.S. 658 (1978)
  • Pembaur v. City of Cincinnati, 475 U.S. 469 (1986)
  • City of St. Louis v. Praprotnik, 485 U.S. 112 (1988)
  • Staub v. Proctor Hospital, 562 U.S. 411 (2011)
  • Reeves v. Safeway Stores, Inc. (2004) 121 Cal.App.4th 95
  • Harris v. City of Santa Monica (2013) 56 Cal.4th 203
  • Guz v. Bechtel National, Inc. (2000) 24 Cal.4th 317
  • Yanowitz v. L'Oreal USA, Inc. (2005) 36 Cal.4th 1028
  • Morgan v. Regents of University of California (2000) 88 Cal.App.4th 52
  • University of Texas Southwestern Medical Center v. Nassar, 570 U.S. 338 (2013)
  • Poland v. Chertoff, 494 F.3d 1174 (9th Cir. 2007)
  • Jett v. Dallas Independent School District, 491 U.S. 701 (1989)
  • Christie v. Iopa, 176 F.3d 1231 (9th Cir. 1999)
  • Ashcroft v. Iqbal, 556 U.S. 662 (2009)
  • Reeves v. Sanderson Plumbing Products, Inc., 530 U.S. 133 (2000)
  • Washington v. Garrett, 10 F.3d 1421 (9th Cir. 1993)
  • Wellpoint Health Networks, Inc. v. Superior Court (1997) 59 Cal.App.4th 110
  • Hoglund v. Sierra Nevada Memorial-Miners Hospital (2024) [verify reporter citation before publishing] (judicial-text reproduction (external site))
  • Choochagi v. Barracuda Networks, Inc. (2021) [verify reporter citation before publishing] (judicial-text reproduction (external site))
  • Raines v. U.S. Healthworks Medical Group (2023) 15 Cal.5th 268 (judicial-text reproduction (external site))
  • Reno v. Baird (1998) 18 Cal.4th 640; Jones v. Lodge at Torrey Pines Partnership (2008) 42 Cal.4th 1158
  • Tsao v. Desert Palace, Inc. (9th Cir. 2012) 698 F.3d 1128 (judicial-text reproduction (external site))

Statutes 8

  • Cal. Gov. Code § 911.2 (source (external site))
  • 42 U.S.C. §§ 2000e-5(e)(1), (f)(1), as applied by § 12117(a)
  • Cal. Lab. Code § 1198.5
  • Cal. Lab. Code § 226, subd. (b)
  • Cal. Lab. Code § 432
  • Cal. Gov. Code § 7920.000 et seq.
  • Cal. Bus. & Prof. Code §§ 2052, 2400
  • Cal. Lab. Code § 1198.5, as amended by SB 513 (effective January 1, 2026; statutory reproduction (external site))

Other authorities 1

Before: correct defendant and corporate structure. Timing: deadlines. Additional roadmaps are in development.

Research expansion — proving decision authority without guessing from titles#

The six-stage matrix above distinguishes origination, recommendation, review, approval, communication and implementation; the separate ability to reverse is an additional inquiry, not a substitute for proof of the particular decision. A person may supervise the employee who delivers a termination letter without having decided that termination was warranted. Conversely, an executive may direct a result through a subordinate who appears as the signatory. The records should show who initiated the request, what rule was invoked, the approval chain, who possessed discretion to decline the decision and whether the final action tracked or departed from the written recommendation.

The source record must separate employer identity from decisionmaking responsibility. A payroll entity may issue an employee's wages without being the only organization that participated in job assignments or policy creation. A professional corporation may be the formal employment or contracting party while a separate management organization provides administrative support. Neither arrangement conclusively establishes a joint-employer theory or unlawfully delegated clinical authority. The applicable legal test turns on the particular cause of action, statutory definition and proved facts, not a brand appearing in an email signature. An auditor should keep the exact entity names as recorded and avoid rewriting them to fit a preferred interpretation.

In employment matters, an authority map can include the job description, delegation-of-authority document, approval matrix, contemporaneous HR notes, supervisor recommendation, medical or occupational health recommendation, board or committee action if applicable, and dated notice to the affected person. The timeline should identify which person had which information when the decision was taken. An email copying an executive may establish delivery or notice; it does not automatically establish that the executive ordered the outcome. A committee's acknowledgment may be informational rather than a vote. A professional title may have clinical significance without control over payroll or employment policies.

A useful falsification test asks what documentary trail would be expected if the apparent signatory was merely implementing another person's instruction. Conversely, what record would be expected if the manager actually possessed independent authority and rejected alternative recommendations? If the answer depends on bylaws, delegated powers or an executed management agreement unavailable to the public, the Roadmap should say that final authority is unresolved. It should not infer it from a photograph, marketing title, company hierarchy diagram or attorney argument.

The same method applies to custody healthcare. The official approving a staff budget may be different from the clinician ordering an urgent transfer and different again from the custody officer arranging transport. A county can have contract oversight without automatically making each medical decision; a contractor can employ clinicians without automatically controlling security movement. A decision-specific matrix—rather than a universal label of “who controlled everything”—allows readers to see which facts would make an institutional-liability theory stronger or weaker.

Where two organizations offer competing descriptions of authority, quote or paraphrase their positions with exact attribution. A filing asserting legal separateness is evidence of the party's position; an executed contract establishes its terms; a court order establishes what the court decided. None should be silently promoted into proof that a disputed real-world chain of control worked precisely as claimed. The right conclusion may be that formal rights are clear but practical operation remains unverified.

Negative controls for the decisionmaker inquiry

The strongest test of an apparent decisionmaker may be evidence that the person lacked authority to produce the outcome. A delegation letter, board resolution, job description or documented veto by another official can disprove an inference based on title alone. A public account should describe that contrary evidence as prominently as emails showing managerial involvement. A person receiving notice can be different from the person determining the result, and the document should preserve that distinction even where it complicates the narrative. Authority is proved decision by decision, not transferred wholesale from one documented interaction to every subsequent action.

What this page cannot do#

It cannot identify who decided anything in a real case, and it cannot say whether a decision was lawful. It offers a structure for reading records.

About this page. This roadmap is part of a free public-education series on claims and accountability mechanisms connected to correctional healthcare and healthcare employment in California. It is general information about the law, current as of the date shown, and the law may have changed since. It is not legal advice and is not a substitute for advice from a licensed attorney who knows the facts of a particular situation. Reading this page, or contacting its author, does not create an attorney-client relationship, and communications with the author are not confidential or privileged. Please do not send case documents, medical records, privileged communications, Social Security numbers, or other sensitive personal information; the site does not accept them. The author does not recommend particular lawyers, receives nothing of value from any referral, and charges nothing for this material. Descriptions of lawsuits refer to allegations unless a court has made a finding, and a legal theory described here does not mean that any person or entity is liable. The author's interest in the subject is described in the series' statement of interest.

Version 1.1 · Corrections log

KPSGILL.com is not a law firm. No one at KPSGILL.com is a lawyer, and no person associated with the website provides legal advice through these Roadmaps.

The CFMG–Wellpath Claims & Accountability Roadmaps are provided for general educational, research, public-interest, and informational purposes. They explain legal concepts, statutes, cases, procedural issues, evidence considerations, and publicly available records in general terms.

Nothing on KPSGILL.com creates an attorney-client relationship. Reading the website, using a worksheet, following a Roadmap, sending information to the website, or communicating with anyone associated with KPSGILL.com does not make that person your lawyer and does not create attorney-client privilege or confidentiality.

The Roadmaps do not determine whether any particular person has a valid legal claim, who should be sued, what claims should be brought, what defenses apply, what a case is worth, or when an individual filing deadline expires.

Laws, regulations, court decisions, procedural rules, and filing deadlines can change and can depend upon facts, jurisdiction, custody status, employment status, the identity of the parties, and other circumstances. A general limitation period or procedural rule described on this website should never be treated as a calculation of an individual's actual deadline.

Anyone considering a legal claim, responding to a lawsuit, facing a filing deadline, deciding whether to preserve or disclose records, or making another decision with legal consequences should consult a qualified licensed attorney in the appropriate jurisdiction.

Primary sources should be reviewed independently. Where a Roadmap discusses CFMG, Wellpath, counties, clinicians, employers, or other entities, the discussion should not be understood as establishing liability merely because an entity or legal theory is discussed.

Search KPSGill.com

Search the full publication — patient guides, policy, investigations, enforcement records and research.