Section 1983 civil‑rights complaints, element by element

Section 1983 provides that "Every person who, under color of any statute, ordinance, regulation, custom, or usage, of any State or Territory or the District of Columbia, subjects, or causes to be subjected, any citizen of the United States or other person within the jurisdiction thereof to the deprivation of any rights, privileges, or immunities secured by the Constitution and laws, shall be liable to the party injured in an action at law, suit in equity, or other proper proceeding for redress, …" The statute's main sentence is a long one, and the engine starts there, not with a summary of it.

Read closely, the text itself names the pieces a complaint has to address:

1. A person. The defendant must be a "person" within the meaning of the statute.

2. Under color of state law. The conduct must be "under color of any statute, ordinance, regulation, custom, or usage" of a State, a Territory or the District of Columbia.

3. Causation. The defendant "subjects, or causes to be subjected," the plaintiff to the deprivation.

   Each defendant is liable only for that defendant's own conduct: there is no vicarious liability under § 1983 (Ashcroft v. Iqbal, 556 U.S. 662, 676 (2009)), and the complaint must plead facts that make each claim plausible (id. at 678).

4. A deprivation of a federal right. The right must be one "secured by the Constitution and laws."

5. A remedy. The statute makes the defendant "liable to the party injured in an action at law, suit in equity, or other proper proceeding for redress."

The statute also carries its own limit on one kind of relief: "in any action brought against a judicial officer for an act or omission taken in such officer's judicial capacity, injunctive relief shall not be granted unless a declaratory decree was violated or declaratory relief was unavailable."

What each of those words means in practice, who counts as a "person," what "under color of" law requires, and how causation is proven against a supervisor or an entity, is defined by case law. The engine researches those definitions from the controlling opinions of the courts that bind the filing court, reads each opinion in full, and records each one in the Citation Ledger before it can support a paragraph. This page does not summarize that case law, because the answer depends on the court and on the most recent controlling statement.

Before research begins, the engine writes an element sheet: every legal element the claim must prove, each one marked unanswered until facts and authority fill it. For a Section 1983 claim, the sheet starts from the statute's text above and grows as research shows what the controlling courts require for the specific right asserted.

During verification, an element sweep confirms that each element is answered by four things that exist outside the model's own opinion:

• a paragraph in the draft that pleads it;
• a record file that supports it;
• a verified authority that states the rule, one that is not on the list of known-bad authorities;
• and facts actually stated in the pleading.

A draft with an unanswered element is blocked until the element is answered, or marked not applicable with a written reason. The check exists because a complaint can read well and still leave one element unpleaded, and that is often the element a motion to dismiss is built on.

Illustration, fictional matter.

Element	Defendant	Paragraph	Record	Authority	Status
Right secured by federal law	Officer (fictional)	¶ 22	R. 52–60	ledger row 7	answered
Under color of state law	Officer (fictional)	¶ 23	R. 12	ledger row 3	answered
Policy or custom	City of Example (fictional)	¶ 30	R. 31	ledger row 12	answered
Causation	City of Example (fictional)	¶ 31	none yet	ledger row 14	unanswered: draft blocked

Illustration, fictional matter.

ElementParagraphRecordAuthorityStatus

Right secured by federal lawOfficer (fictional)¶ 22R. 52–60ledger row 7answered

Under color of state lawOfficer (fictional)¶ 23R. 12ledger row 3answered

Policy or customCity of Example (fictional)¶ 30R. 31ledger row 12answered

CausationCity of Example (fictional)¶ 31none yetledger row 14unanswered: draft blocked

The Federal Rules of Civil Procedure set the pleading requirements. Rule 8(a) says a pleading that states a claim for relief "must contain: (1) a short and plain statement of the grounds for the court's jurisdiction ...; (2) a short and plain statement of the claim showing that the pleader is entitled to relief; and (3) a demand for the relief sought, which may include relief in the alternative or different types of relief."

For jurisdiction, 28 U.S.C. § 1343(a)(3) gives the district courts original jurisdiction of a civil action "To redress the deprivation, under color of any State law, statute, ordinance, regulation, custom or usage, of any right, privilege or immunity secured by the Constitution of the United States or by any Act of Congress providing for equal rights of citizens or of all persons within the jurisdiction of the United States." The engine drafts the jurisdictional statement from that text and the facts that bring the claim within it.

When a complaint needs to change, Rule 15(a)(2) governs amendment outside the matter-of-course window: "a party may amend its pleading only with the opposing party's written consent or the court's leave. The court should freely give leave when justice so requires." The engine treats a possible amendment as a real option in the plan, not an afterthought, because an amended complaint is often the best answer to a motion that identifies a curable gap.

The most common early threat to a civil-rights complaint is a motion to dismiss for "failure to state a claim upon which relief can be granted" under Rule 12(b)(6). The engine lists the known dismissal traps for the claim type and the court before strategy, and answers each one in the plan: which element the defense attacks, which paragraph and authority answer it, and what the fallback is if the court disagrees.

The draft is then attacked the way opposing counsel would attack it and read the way a hostile panel would read it. Arguments that do not survive are reframed or dropped, and the theories ledger records why. The mechanics of answering a motion, including the conversion rule and the summary-judgment standard, are on the page on motions to dismiss and summary judgment.

Research runs a loss-pattern sweep for the claim type, and at strategy each trap is answered in a table, trap by trap. In § 1983 matters the sweep commonly covers:

• Qualified immunity. Officials performing discretionary functions are generally shielded from damages unless their conduct violated clearly established rights a reasonable person would have known (Harlow v. Fitzgerald, 457 U.S. 800, 818 (1982)). Courts may decide the two parts of that inquiry in either order (Pearson v. Callahan, 555 U.S. 223, 236 (2009)).
• Municipal liability. A city or county is liable under § 1983 only when its own policy or custom caused the injury, not merely because it employs a wrongdoer (Monell v. Department of Social Services, 436 U.S. 658, 694 (1978)).
• Claims that attack a conviction. A damages claim that would necessarily imply the invalidity of a conviction or sentence is not cognizable unless the conviction has been invalidated (Heck v. Humphrey, 512 U.S. 477, 486–87 (1994)).
• Timing. Section 1983 borrows the forum state's limitations period for personal-injury torts (Wallace v. Kato, 549 U.S. 384, 387 (2007)), so the clock differs from state to state. The engine dockets it from the facts at intake.
• Prison conditions. A prisoner must exhaust available administrative remedies before suing over prison conditions (42 U.S.C. § 1997e(a)); see prisoner Section 1983 complaints.

This list is general information about common issues, not an analysis of any case.

Immunity defenses, including qualified immunity for individual officials, are among the most litigated questions in civil-rights practice, and they are defined almost entirely by case law. The engine does not state them from memory. It researches the controlling decisions of the U.S. Supreme Court and of the courts that bind the filing court, reads each one in full, and searches in both directions for authority that cuts against the claim. If controlling authority against the theory turns up, the line stops until a recorded pivot: a different theory, a different defendant, honest distinguishing, or an informed decision to proceed.

That candor matters to the lawyer who signs. A complaint built on authority that has been overruled, or that ignores a directly adverse controlling decision, is a risk to the client and to the lawyer. The research ladder and the adverse sweep are described on the controlling authority first page.

Federal statutes add requirements for suits about prison conditions, and the engine checks for them at intake because they can end a case before the merits are reached: exhaustion of the grievance process under 42 U.S.C. § 1997e(a), screening of the complaint under 28 U.S.C. § 1915A, the physical-injury rule of § 1997e(e) and the three-strikes rule of 28 U.S.C. § 1915(g). Failure to exhaust is an affirmative defense, and a prisoner is not required to plead exhaustion in the complaint (Jones v. Bock, 549 U.S. 199, 216 (2007)). Each rule is quoted from the statute on the page on prisoner Section 1983 complaints.

Many civil-rights matters involve rights under both the U.S. Constitution and a state constitution or statute. The engine preserves each right under both state and federal law where both apply, and keeps a preservation map that shows where each claim must be raised now to stay alive in every court above. A state-law claim that is not pleaded may be lost; a federal question that is not raised may never reach federal review. The map is explained on the page on how the preservation map works, and the route to review after a ruling is on the appeals page.

Section 1983 borrows the forum state's limitations period for personal-injury torts (Wallace v. Kato, 549 U.S. 384, 387 (2007)), so the clock differs from state to state. Section 1983's text states no limitations period of its own. The period that governs a given claim, and when it begins to run, is a research question that the engine answers from controlling authority for the filing court and records with its source. Like every deadline, it is computed twice by default, from the rule text and the facts, and when the computation is ambiguous, the engine takes the earlier reading. The result is posted to the docket manager as a dated deadline, with the source of the rule attached.

Under 42 U.S.C. § 1988(b), in an action to enforce Section 1983 and the other provisions the subsection lists, "the court, in its discretion, may allow the prevailing party, other than the United States, a reasonable attorney's fee as part of the costs," subject to an exception the statute states for actions against judicial officers. The engine includes the fee request in the demand for relief where the firm directs it, and flags the judicial-officer exception when a defendant is one.

The same element-by-element method builds the engine's other civil complaints. The elements come from the statute, rule or recognized claim that creates the cause of action, read from primary law in the engine's own library. Each element is tied to a numbered paragraph, a stated fact and a verified authority, and the court's own pleading rules for that complaint are pulled and checked before drafting. The preservation map, the attack on the draft and the final read run exactly as they do for a Section 1983 claim.

Filing on your own? The engine prepares the complaint for self-represented filers too. You read it, sign it and file it yourself, and you decide what to file. Representing yourself explains how it works without a lawyer.

Every case citation is pulled from the primary source, read in full, and verified before it can appear in a filing. A case citation that is not in the verified ledger cannot reach the page. Each one must meet the same four-part standard: from the primary source, read in full, supporting the point it is cited for, and still good law. The statute and rule citations on this page and in a complaint are exempt from the ledger block, and that exemption is declared. Statute text is required from the source before reliance, and the engine retrieves it from the source. How the ledger works is on the unverified-citation rule page, and the terms used here, including element, color of law and qualified immunity, are defined under elements and immunity terms in the glossary.

By default, you approve twice, and the whole filing gets a final read before it ships; each approval, or the client's recorded standing instruction to proceed, is stamped in the record. The standing instruction never lifts a hold, and the candid analysis still runs. For a law firm, the attorneys of record supervise the work, sign the complaint, and remain responsible for it. The engine is built to support those duties; it never discharges them.

Examples on this site use fictional courts and fictional parties. Nothing here describes a real matter.

What is a § 1983 claim? A federal claim for damages or other relief against a person who, acting under color of the law of a State, a Territory or the District of Columbia, deprived someone of a right secured by the Constitution and federal laws (42 U.S.C. § 1983). This is general information, not legal advice.

Can a city be sued under § 1983? A local government can be liable when its own policy or custom caused the violation (Monell, 436 U.S. at 694). It is not liable merely because it employs someone who caused the harm.

How long is there to file? Section 1983 borrows the state's personal-injury limitations period (Wallace, 549 U.S. at 387), so it depends on the state. The engine dockets the limitations clock at intake from the facts of the matter.

Start a request (opens the main site) on Legal Ops Depot's main site. Legal Ops Depot is not a law firm and does not give legal advice.

Related: Motions · Appeals · Glossary: qualified immunity