A Civil Procedure outline that works is a set of flowcharts wearing a document's clothes. The course is sequential, every doctrine is a station on the litigation line, and the exam runs the line as a funnel, so the outline's job is to make the sequence executable: yes or no questions, in order, with rule numbers attached.

The general method, the five part module, the weekly cadence, the compression pipeline, lives in how to outline and the template spec. This page is the Civ Pro specific build: the skeleton, the exemplar module, and the mistakes this course punishes.

The skeleton

Ten sections, in the order the funnel runs them, which is usually close to your syllabus order:

• Personal jurisdiction, built as a decision tree
• Subject matter jurisdiction: diversity, federal question, supplemental, removal
• Venue and transfer
• The Erie doctrine, as a short question sequence
• Pleadings: the complaint, plausibility, Rule 12 motions, amendment and relation back
• Joinder of claims and parties
• Discovery: scope, tools, sanctions
• Disposition without trial: summary judgment, judgment as a matter of law
• Preclusion: claim and issue, as parallel element checklists
• Appeals and the final judgment rule

Each section is a flowchart or checklist first and prose never; if a topic cannot be run as a series of questions, it is not finished, which is the standing test from the Civ Pro hub.

The exemplar: personal jurisdiction as a decision tree

Write the course's biggest unit exactly like this, and the shape teaches you what every other unit wants. Question one: is there a traditional basis, presence when served, domicile, consent? If yes, done.

If no: does the forum's long arm statute reach the claim? If no, done, no jurisdiction. If yes: minimum contacts analysis, purposeful availment first, did the defendant direct conduct at the forum, with the stream of commerce split noted as an argue both sides flag.

Then relatedness: does the claim arise out of or relate to those contacts? Then reasonableness, the fairness factors, as a short list the defendant almost never wins alone. Running beside the tree, a two line general jurisdiction branch: essentially at home only, place of incorporation and principal place of business, and a note that stretching it is a red flag.

Every node carries its authority, International Shoe at contacts, the modern cases at their specific moves, and the whole tree compresses to six lines in the attack outline. That is the format: questions in order, cases as one line handles at the node they control, traps flagged inline.

Rule numbers are a column, not a garnish

Civ Pro is the course where citing the rule by number earns visible points and speeds your writing, so build the habit into the document: every doctrine that lives in the Federal Rules carries its number in a consistent spot, the 12(b) grounds enumerated, 56 at summary judgment, the discovery scope rule, the joinder rules your course covered. By finals the numbers should surface with the doctrine automatically, which only happens if the outline pairs them from week one.

What survives compression

The attack outline for this course is famously clean: the funnel on page one, personal jurisdiction tree compressed, SMJ checklists, venue, Erie's question sequence, and the endgame doctrines on page two, pleadings standards through preclusion, each as element keywords with rule numbers. If your professor's exams lean somewhere specific, discovery sanctions, class actions, the attack version inherits the weighting, which is exactly what profiling their past exams through the protocol in the Civ Pro exam guide establishes before you compress.

The structural mistakes

Organizing by case chronology instead of by the line, which produces a reading diary rather than a tool. Separating supplemental jurisdiction from the rest of SMJ, when on the exam it is always a bolt on question to a diversity or federal question analysis. Burying Erie in prose, when it runs as three or four questions and dies as a paragraph.

Writing minimum contacts as a definition instead of a sequence. And flattening issue preclusion into a single line, skipping the defensive versus offensive use distinction, which professors test precisely because outlines skip it. A ready made shell with the tree structures pre drawn is in the template library.

FAQ

How long should a Civ Pro outline be?

Lean, by this course's standards: thirty to forty pages of trees and checklists for the master, two for the attack version. Prose inflation is the tell that case stories are leaking back in.

Should the outline include the Federal Rules text?

Key language from the rules you cite constantly, yes, especially where the professor tests the exact words, the 26(b)(1) scope phrase, the 56 standard. Wholesale rule dumps, no; the rulebook already exists.

Flowcharts in what tool?

Whatever you will maintain weekly: indented question lists in a document work exactly as well as drawn diagrams, and they compress and search better. The tree is the logic, not the graphics.

Written by Ali, Georgetown Law, founder of Lovare Institut.

Book a call