The companion page, how to outline, covers the method: when to build, the weekly assembly line, what stays out. This page is the document specification: what a working outline looks like on the page, module by module, so that under exam pressure it behaves like the decision tool it is supposed to be. The governing test for every structural choice is scan speed, can you find the rule, its elements, and its traps in seconds, because an outline is consulted at speed or memorized from, never read.

The header block

Page one, before any doctrine: course and professor, exam date, format as stated, hours, question count if known, and the materials rule, open, closed, or limited, because the format drives the compression target per open vs closed book. Then the professor's exam signals collected all semester, rewards depth or coverage, wants case names or not, always includes a policy question, transcribed from your notes' right column. This block is the operating manual for the specific exam the outline serves, and most outlines omit it, which is like building a tool without reading the job.

The body: syllabus order, standard modules

Organize by the professor's syllabus sequence, not the casebook's and not a commercial outline's, because their order is the architecture the exam will assume. Within it, every doctrine gets the same five part module. The rule, stated as transportable law with elements enumerated, visually set off, bolded or boxed, so the eye lands on it first.

The cases, as one line handles attached to the elements they define, name plus clause, nothing more. The exceptions and limits, attached directly to the rule they modify rather than orphaned in their own section.

The application notes, watch for transferred intent, applies only to goods, distinguish from the neighboring doctrine, which are the traps and boundary lines that separate answers under the curve. And the hypos, class hypotheticals with the professor's resolutions, the layer no purchased document contains and the closest thing to exam questions you possess.

Formatting rules that earn their keep

Three heading levels maximum, topic, doctrine, element; a fourth level is the document telling you to restructure. Consistent visual grammar throughout: one treatment for rules, one for case names, one marker for traps, chosen once and never varied, so that scanning becomes pattern matching. White space is a feature, dense pages read slowly under adrenaline.

Past forty pages, add a table of contents and page numbers, which cost five minutes and save five per consultation. Digitally, one file per course with dated saves, searchable, in whatever tool you will actually open weekly, and mind the exam constraint: if the exam permits printed materials only, the outline must live happily on paper, tabs and all.

How the structure changes down the pipeline

The three stage compression from the method page changes what modules keep. The master outline, twenty to fifty pages, carries all five parts. The attack outline, two or three pages, keeps only the checking order, elements as keywords, and trap flags, rules compress to prompts, cases to bare names, hypos disappear, because its job is issue coverage under time, per issue spotting.

The memory sheet, one page, is the attack outline's skeleton, reproducible on scratch paper in the exam's first five minutes per exam strategy. Each stage is validated the same way, by running practice exams against it and restoring anything you reached for and missed.

Course specific variants

The module structure holds everywhere; the body's shape flexes by course. Civ Pro and Property want flowcharts for their sequential machines, Contracts and Crim want the two column common law versus code layout, Torts wants element tables, Con Law wants the framework selector as page two, right after the header block. Each course hub specifies its variant, and ready made shells for all seven, header block included, are in the template library.

FAQ

Should the outline include policy discussion?

Only where it crystallized into something usable: a professor's stated position, or a prepared paragraph for a course whose exams historically include a policy question. Free floating policy musing is note material, not outline material.

Word processor, Google Docs, or a notes app?

Whichever you will open every Friday, with two constraints: it must search well, and it must export cleanly to whatever format the exam rules permit. The tool matters far less than the weekly appointment with it.

How exact do rule statements need to be?

Exam exact: written the way you would put them in an answer, in the professor's phrasing where it differs from the casebook's. An outline of paraphrases trains paraphrase recall, and precision points are cheap to bank now and expensive to improvise later.

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

Book a call