Why Every Chief Needs to Understand This Case
There’s a comforting assumption that drifts around command staff in most law enforcement agencies: if an officer does something wrong, the agency pays, the officer gets disciplined, and command stays out of the personal liability picture. The doctrine of respondeat superior — “let the master answer” — doesn’t apply in federal civil rights cases, so the chief isn’t automatically responsible for what officers do in the field.
That comforting assumption is half correct. Chiefs aren’t automatically liable. But they can be personally liable when they fail to train or supervise in a way that creates the “affirmative link” between their conduct and the constitutional deprivation an officer causes. McClelland v. Facteau is the case that defined that affirmative link and opened the door to personal liability claims against police command staff under 42 U.S.C. § 1983.
If you are a police chief, sheriff, training commander, or any supervisor with authority over officer training and discipline, this case is not abstract. It is the legal basis on which plaintiffs name you personally as a defendant in federal civil rights lawsuits.
What Happened
In the late 1970s, Cecil McClelland was arrested for speeding in New Mexico. What happened next formed the basis of a civil rights lawsuit. During his arrest and custody, McClelland alleged he was denied phone calls, not informed of his constitutional rights, not brought before a magistrate, and ultimately beaten by the arresting officer while in custody. The incidents involved a New Mexico State Police officer, a state police lieutenant, and a Farmington City Police Department jailer.
McClelland filed suit under § 1983 against five defendants. Three — the officers directly involved in his arrest and custody — settled. Two remained: Martin E. Vigil, Chief of the New Mexico State Police, and Robert L. Schmerheim, Chief of the Farmington City Police Department. The claim against the chiefs wasn’t that they had directly violated McClelland’s rights. It was that they had failed to adequately train and supervise the officers who did.
The district court granted summary judgment to both chiefs. McClelland appealed. The Tenth Circuit’s decision on that appeal became a foundational case in the law of supervisory liability.
What the Court Held
The Tenth Circuit began by confirming what was already established: respondeat superior does not apply in § 1983 cases. A supervisor cannot be held liable simply because they employ someone who violated constitutional rights. That would turn every agency head into an insurer for every officer’s conduct.
But the court then articulated the principle that made McClelland a landmark case. A supervisor can be personally liable under § 1983 when there is an “affirmative link” between their conduct and the constitutional deprivation. That affirmative link exists when the supervisor has personally participated in, acquiesced in, or failed to correct misconduct that they had notice of — or when they neglected their duty to train subordinates and establish department procedures.
In the court’s own framing: a police chief could be held liable if he neglected his duty to train subordinates and establish department procedures designed to protect constitutional rights, and if he failed to exercise appropriate supervision to correct misconduct of which he had notice.
McClelland established two pathways to personal supervisor liability: (1) failure to train subordinates and establish protective procedures, and (2) failure to supervise and correct misconduct after being put on notice. Both pathways require an affirmative link between the chief’s conduct and the constitutional violation — but that link is easier to establish than many chiefs realize.
The Notice Requirement — and How It’s Met
One of the key issues in McClelland was whether the chiefs had been adequately put on notice of prior misbehavior. Both Vigil and Schmerheim denied knowledge of wrongdoing by their subordinates. McClelland countered with evidence that he argued put the chiefs on notice: newspaper articles indicating rights violations at the Farmington jail and by State Police Officer Facteau, affidavits corroborating those reports, and evidence that Chief Schmerheim had been a party in two prior lawsuits involving deaths of prisoners at the Farmington jail.
The court was careful to distinguish real notice from background noise. “Distant rumors that are too vague to prompt action by reasonable persons, or information that is reasonably believed to lack credibility, do not provide sufficient notice.” But credible reports, documented complaints, and prior lawsuits — those meet the notice threshold. And once a chief has notice of a pattern or a problem, the duty to act activates.
The practical implication is significant: chiefs don’t have to personally witness misconduct to be on notice of it. Civilian complaints, internal affairs records, prior litigation, news reports, and even credible patterns of behavior can constitute notice. Once a chief knows — or should have known — that a subordinate or a systemic issue is creating constitutional risk, they have an affirmative duty to act.
How McClelland Applies to Firearms Training
McClelland wasn’t a firearms case. But its supervisory liability framework applies directly to firearms training management. Consider the parallel scenarios:
Scenario 1: A chief has access to a qualification tracking system that shows three officers with expired firearms qualifications. The chief takes no action. One of the three officers is later involved in a fatal shooting. Under McClelland, the chief’s inaction after being put on notice of the expired qualifications — combined with their duty to ensure officers are properly trained and equipped — creates an affirmative link that can support personal liability.
Scenario 2: A chief knows the agency’s firearms training program consists only of annual marksmanship qualification, with no documented judgment-based training. Years go by with no program change. When an officer is involved in a questionable shooting, the plaintiff argues the chief had knowledge of the training deficiency (documented through budget reviews, training division reports, or even published departmental summaries) and failed to correct it. That’s the McClelland pattern applied to modern firearms training.
This is why readiness visibility matters beyond operational convenience. A dashboard showing real-time qualification status isn’t just an efficiency tool — it’s the affirmative demonstration that the chief is monitoring officer readiness and can act on deficiencies as they surface. The dashboard is evidence that the chief fulfilled their supervisory duty.
The Tuttle Connection
McClelland is often cited alongside Tuttle v. City of Oklahoma City, 471 U.S. 808 (1985), which addressed what single incidents can (and cannot) establish about a supervisor’s liability. Tuttle held that a single incident generally isn’t enough to establish municipal liability for inadequate training — unless the need for training is so obvious that failure to provide it is itself evidence of deliberate indifference. That “obvious need” concept is what Canton v. Harris formalized four years later for firearms training specifically.
Taken together, McClelland, Tuttle, and Canton form the framework that defines both municipal and personal supervisory liability in training failure cases. McClelland provides the affirmative link test for chiefs. Tuttle limits single-incident municipal liability except where need is obvious. Canton identifies firearms training as an area where the need is obvious by definition.
What Chiefs Should Do
The practical guidance that flows from McClelland is direct, and every chief should operate accordingly.
Know your officers’ training status. If someone asked you today whether every officer under your command is currently qualified with every authorized weapon, you should be able to answer with confidence — not by calling the training coordinator but by looking at a dashboard. This is the affirmative act that demonstrates you’re fulfilling your supervisory duty.
Act on notice when you get it. Complaints, civilian feedback, prior lawsuits, and audit findings all constitute notice under McClelland. Document what you received, what you did about it, and when. An absence of action after notice is what the court called a “deliberate breach” of basic supervisory duty.
Establish and document procedures. The McClelland court specifically identified the duty to “establish department procedures designed to protect constitutional rights” as part of the chief’s supervisory responsibility. That includes firearms training policies, remedial training procedures, and qualification tracking systems. The existence of the policies isn’t enough — you have to be able to show they’re being followed.
Document your own supervisory engagement. Attendance at training division meetings, review of qualification reports, signed policy approvals, response to audit findings — these create the affirmative record that demonstrates you’re actively engaged in training oversight. A chief with an affirmative record of engagement is a chief with a McClelland defense.
The comforting assumption that chiefs stay out of the personal liability picture is exactly wrong. Plaintiffs name chiefs personally as defendants in failure-to-train cases as a matter of routine — because McClelland opened that door in 1979 and it has never closed. The affirmative link the court requires isn’t hard for a plaintiff’s attorney to construct. It’s much harder to defend against without proof of active supervisory engagement.
For the broader framework of how supervisory liability connects to training documentation, see our training documentation pillar. For the operational tool that creates the affirmative record of engagement McClelland requires, see our officer readiness guide.
How exposed is your department?
Take our free 4-minute Training Liability Risk Assessment to find out where your documentation creates exposure — and how to fix it.
Take the Assessment