How to build a law school outline.

A full outline captures everything. Every case you've briefed contributes its rule. Every class discussion adds a nuance or a professor emphasis. Every statute gets its elements listed. You don't write this outline for a reader — you write it for your future self in late November who needs to find the proximate cause test instantly. It is organized by doctrine, not by the chronological order topics appeared in class. All the material on consideration goes together, regardless of whether it came from week two or week ten.

A condensed outline strips the full outline down to the rules, elements, and exceptions you need to recall under exam pressure. It might be fifteen to twenty-five pages for a semester-length course. A condensed outline is what you read the week before the exam to load the doctrine back into working memory. An attack outline is one to three pages of checklists: if I see these facts, check for these issues in this order. It is optimized for speed. These three documents exist in a hierarchy — you build the full outline first, condense it later, and crystallize it into an attack outline last.

The most reliable outlining strategy is incremental. Thirty minutes after a Contracts class — while the discussion is fresh — is worth three hours in December when you've forgotten what the professor thought was important. Students who wait until finals to start building outlines do so under the worst possible conditions: exhausted, behind schedule, and no longer able to distinguish what the professor actually emphasized from what the textbook said. Build as you go.

The unit of a good outline is the rule with its elements broken out, not the case. For every doctrine, write the black-letter rule, then list its elements as a checklist, then attach the exceptions and the leading cases as sources underneath. When the rule is a multi-part test — the elements of negligence, the requirements for an enforceable contract, the factors for personal jurisdiction — the outline should make that structure visually obvious, because that structure is exactly what you'll walk through on the exam. An outline that reads as prose paragraphs is hard to scan; one built as nested rule → elements → exceptions is something you can navigate in seconds.

Use your professor's emphasis, your syllabus, and your past exams as the blueprint — not the casebook's table of contents. Casebooks include material your professor will skip and omit framing your professor stressed; the exam tests your professor's course, not the book. Two signals are worth more than any commercial outline: what the professor spent disproportionate class time on, and what shows up on their old exams (often on file at the library or with student orgs). Build your attack outline directly from those past fact patterns — they tell you which issues this specific professor likes to hide and in what combinations.

Borrowing an upperclassman's outline is fine as a reference and dangerous as a substitute. The value of an outline is almost entirely in the act of making it — synthesizing a semester of material into your own structure is the studying. A handed-down outline can orient you to a professor's emphasis and save lookup time, but reading someone else's synthesis is not the same as building your own, and it will be organized around how that student thought, not how you do. Use it to check your coverage, never to replace the work.

The condensation step — going from full outline to condensed — is where most of the actual learning happens, and students who skip it pay for it in the exam room. Condensing forces you to decide which rules you know cold and which still need reinforcement. Every rule you can drop from the condensed outline is one you've genuinely internalized; every rule that still feels uncertain stays in. Do this condensation work two to three weeks before finals, not the night before, so you have time to use the gaps it reveals. Reading your condensed outline is also a faster and more effective review loop than re-reading casebook chapters because it is organized for retrieval, not for first-time learning.

The attack outline is a different cognitive tool from the other two. It is not a reference document — it is a performance script. A Torts attack outline might read: 'Negligence: duty (foreseeable plaintiff?) → breach (reasonable person would have? foreseeability of risk? cost of precaution?) → actual cause (but-for?) → proximate cause (foreseeable harm? intervening cause?) → damages.' That sequence is what you walk in the exam room knowing by heart, so that when you see a fact pattern you can run the checklist automatically and catch every element. Write your attack outline after your first practice exam — not before — because you do not yet know which elements this professor likes to make the hard issue.

A note on commercial outlines and study aids: Emanuel, E&E, and Barbri are useful for understanding doctrine you find confusing in the casebook, but they are not substitutes for your own outline. Commercial outlines are organized around a generic national curriculum; your exam is on your professor's course. They are also frequently over-inclusive — full of rules your professor will never test and missing the emphasis on the specific cases your professor chose and the angles they stressed in class. Use them to clarify, not to replace. The student who reads Emanuel but never builds their own outline is gambling on a generic answer to a specific exam.

Different 1L subjects reward different outline structures. Torts is best organized by claim type — negligence, intentional torts, strict liability — with elements listed under each and defenses grouped at the end. Contracts is linear: formation, defenses, performance and breach, remedies — because exam fact patterns follow the life of a contract in sequence. Civ Pro is best organized as a decision tree: personal jurisdiction before subject-matter jurisdiction, pleadings before joinder, because the questions are procedurally ordered and so are the issues. Con Law works well as a standards-of-review index: for each right or power, record which test applies and what it requires. Matching your outline's structure to how the subject tests is the invisible advantage that makes the document useful under exam pressure.

Professor emphasis is the hardest thing to capture in an outline and the most valuable. It lives in the moments when a professor lingers — 'This case is doing something subtle that most people miss' — or when they return to a doctrine more than once, or when they pose a hypo that extends a rule past its obvious limits. These signals are lost if you are not writing them down in the moment. A one-line margin note — 'Prof said this is always tested' or 'returned to this on day 3 — knows it cold' — added to your class notes immediately after class is the input that turns a generic outline into a course-specific one. Two weeks into finals preparation, you will not remember which cases the professor cared most about unless you recorded it when they showed you.

How to tell when your outline is actually working: test it against a practice hypo without looking at your notes first. If you can run the relevant issue checklist from memory, your outline has served its purpose — it organized the doctrine in a way that transferred into recall. If you find yourself flipping through pages during the practice hypo, your outline is a reference document but not yet a memory scaffold. The fix is usually condensation and repetition: read the relevant section of your condensed outline aloud twice, close it, and try again. Retrieval practice is more effective than re-reading; the outline is the scaffold for that practice, not the endpoint of it.