Case Cub Logo

Study Skills Guides

The Attack Outline

The 5-15 page exam-day version of your outline: what it is, exactly what survives the condensation and what gets cut, a worked example, and how to actually use one when the clock is running.

Last updated: August 2026.

Why the Attack Outline Exists

A law school exam gives you three or four fact patterns and about an hour each. Your full outline, the 40-page document you spent the semester building, is a liability in that room: every minute spent scrolling it is a minute not spent writing. The attack outline solves this by pre-deciding what exam-you will actually need: the issue list, the element checklists, the tests too structured to trust to adrenaline, and the things your professor telegraphed.

The open secret is that the document is half the value. The other half is the condensation itself. Deciding what earns a line in twelve pages forces you to rank every rule in the course by testability, and that ranking exercise is among the best final review that exists. This is why the constant r/LawSchool refrain (how do I know what to give up for the attack outline?) has a reassuring answer: the struggle to decide is the studying. Nobody can make the cuts for you, and you would not want them to.

What to Keep, What to Cut

Issue triggers

KEEP

The fact-pattern signals that raise each issue (two contracts formed by mail: mailbox rule; defendant is out of state: personal jurisdiction sweep). These are the highest-value lines in the document because issue spotting is where most exam points are won or lost.

Element checklists

KEEP

Every rule compressed to its numbered elements, because exams award points element by element and a checklist stops you from forgetting to argue damages when you are twenty minutes from time.

Tests you might blank on

KEEP

Multi-factor tests and flowcharts (UCC 2-207, Asahi reasonableness factors, res ipsa requirements). Anything with four-plus moving parts earns its lines; under adrenaline, structured recall fails first.

Professor flags

KEEP

Every PROF note from the full outline survives condensation. If the professor telegraphed it in class, checking for it on the exam takes ten seconds and can be worth a full issue.

Case explanations

CUT

Keep a case name only where the name itself triggers the rule for you (Palsgraf, Erie, Tarasoff). Everything else about the case (facts, procedural posture, reasoning) was scaffolding; the rule already absorbed it.

Rules you know cold

CUT

If you can recite it without looking, it earns one checklist line, not a paragraph. The attack outline is for what you will reach for, and you will not reach for what you already know.

Background, history, policy discussion

CUT

Unless your professor explicitly awards policy points (some do; check the flags), narrative content has no exam-day retrieval value. Cut it without mercy. If policy IS tested, compress each debate to a two-sided one-liner.

Watch a Section Condense (Interactive)

The same negligence material at both altitudes. Step through the three stages to see exactly what condensation removes and why:

C. BREACH
   1. Objective reasonable person standard
      a. Kids: age/intelligence/experience std,
         EXCEPT adult activity (driving)
      b. Physical disability counted; mental not
   2. Custom: evidence of reasonableness, never
      conclusive (T.J. Hooper: whole industry
      can lag)
   3. Negligence per se: unexcused statute
      violation where P in protected class +
      harm of type statute prevents
   4. Res ipsa: (1) accident type doesn't
      happen w/o negligence, (2) instrumentality
      in D's control. Effect: gets P to jury.

The section as it reads in the full outline at the end of the semester: 14 lines.

Fourteen lines become three. The rules you know cold became trigger words; the res ipsa elements kept their count because two-part tests get fumbled under pressure; the case names vanished except where the name is the trigger. Multiply this across every section and 40 pages becomes 10. For the full-outline context this condenses from, see the annotated outline examples (which include four complete real outlines as free PDFs).

Using It During the Exam

1. First five minutes: run the issue checklist against the fact pattern.

Before writing anything, sweep the checklist page against the facts and mark every issue that appears. This converts the attack outline from a reference document into an issue-spotting instrument, which is its real job.

2. Navigate by structure, not by search.

Because the attack outline mirrors your full outline's skeleton, you should know roughly where everything lives without reading. If you catch yourself scanning page by page mid-exam, that section failed condensation; it was too long.

3. Write from the checklist, glance for the tests.

The rhythm that works: state the issue and elements from memory, glance down only for multi-factor tests and exact rule language, keep writing. Students who transcribe from their outline run out of time; the outline supports the answer, it is not the answer.

4. Practice with it before exam day, at least once, timed.

An attack outline used for the first time during the real exam is a liability; you will not know its geography under pressure. One timed practice exam per course with the document open is the minimum. Fix every navigation fumble the same night.

Condensing for finals?

Case Cub builds structured outlines from your class notes and generates practice questions from them, so you can test which rules you actually know cold before deciding what your attack outline can safely cut.

FAQ

What is an attack outline in law school?+
An attack outline is the condensed, exam-day version of a full course outline, typically 5-15 pages. It strips the full outline down to issue triggers, numbered element checklists, multi-factor tests you might blank on under pressure, and professor-emphasis flags. Its purpose is speed: during a timed exam, it functions as an issue-spotting checklist and a fast-lookup reference, while the full 25-60 page outline stays home. The name comes from how it is used: it is the document you attack the fact pattern with.
How long should an attack outline be?+
5-15 pages per course is the working range, and shorter is generally better as long as every issue in the course appears at least as a checklist line. Some students compress further to a 1-2 page pure issue checklist and staple it to the front. If your attack outline is over 20 pages it has not finished condensing, and you will pay a navigation tax during the exam every time you reach for it.
What is the difference between an outline and an attack outline?+
The full outline (25-60 pages) is the complete synthesis of the course, built progressively across the semester; creating it is how you learn the material. The attack outline (5-15 pages) is condensed from the full outline during reading period and is built for exam-day speed: same skeleton, but only element checklists, issue triggers, hard tests, and professor flags survive. You study from the full outline; you sit the exam with the attack outline.
How do I decide what to cut when making an attack outline?+
Cut by retrieval value: keep what you will actually reach for under time pressure (issue triggers, element checklists, multi-factor tests, professor emphases) and cut what you already know cold or will not need mid-exam (case facts and reasoning, background and history, rules you can recite from memory). The deciding question for every line is: would I look this up during the exam? The difficulty of making these cuts is the point; ranking what matters is high-quality final review in disguise.
Do attack outlines work for closed-book exams?+
Yes, with a changed role: for a closed-book exam the attack outline becomes the memorization target rather than the exam-day reference. Its compression is what makes memorization tractable; most students drill the attack outline until they can reproduce the issue checklist from memory, then write that checklist on scratch paper in the first minutes of the exam. The build process is identical either way.

Related Guides

Related Case Cub Tools