A Contracts outline lives or dies on one structural decision: the two column layout, common law on the left, UCC Article 2 on the right, run through every topic where the regimes diverge. Contracts is a two regime course, the exam hides goods contracts inside service shaped facts, and an outline that buries the divergences in footnotes trains exactly the blindness the professor is testing for. The general build method is in how to outline; this page is the Contracts specific architecture: the skeleton, the two exemplar modules, and the traps.

The skeleton

Seven sections, and the first one is the gate everything else runs through:

• Applicable law: the classification module, goods or not, predominant purpose for mixed deals, stated as a two question gate at the very top of the document
• Formation: offer, acceptance, consideration, promissory estoppel, all two column
• Defenses to formation: misrepresentation, duress, unconscionability, mistake, incapacity
• Terms: statute of frauds, parol evidence, interpretation, and the battle of the forms under 2-207
• Performance and breach: conditions as a flowchart, substantial performance versus perfect tender, anticipatory repudiation
• Remedies: as formulas with worked numbers, never as prose
• Third parties: beneficiaries, assignment, delegation

The classification gate sits first because it is analytically first: every exam answer opens by walking through it, per the Contracts hub, and an outline that mirrors the answer's order rehearses the answer every time you review.

Exemplar one: a two column module

Acceptance, written the way every divergent topic should look. Left column, common law: the mirror image rule, an acceptance varying the offer's terms is a counteroffer, and the last shot doctrine on performance.

Right column, UCC 2-207: a definite expression of acceptance operates as acceptance despite additional terms; between merchants, additional terms enter the contract unless they materially alter it, the offer limits acceptance to its terms, or objection follows; different terms trigger the knockout rule in the jurisdictions that use it, an argue both sides flag. Two columns, one topic, and the divergence is visible at a glance under exam time, which is the entire point of the layout.

Exemplar two: remedies as formulas

The remedies section should read like a worksheet. Expectation damages: loss in value of the promised performance, plus other loss, minus cost avoided, minus loss avoided. Then the limits stacked beneath as a checklist: foreseeability under Hadley for consequential loss, certainty, and the duty to mitigate, each one line with its trigger.

Then the alternatives, reliance and restitution, with one line each on when a plaintiff prefers them, and liquidated damages with its two part enforceability test. Add one fully worked number example per formula, built from a class hypo, because doing the arithmetic once in the outline is what makes it automatic in the room, where professors bury real numbers and award points for the math shown.

What survives compression

The attack outline keeps the classification gate verbatim at the top, then the issue checklist in transactional timeline order, formation questions, terms questions, performance questions, remedies, with the two column divergences compressed to flag words, mirror image versus 2-207, perfect tender versus substantial performance. The remedies formulas transfer intact; they are already compressed. Weight the checklist by your professor's demonstrated patterns, established through the Contracts exam guide before compression begins.

The structural mistakes

Burying UCC divergences in notes under common law rules, which is how the classification reflex dies. Writing remedies as narrative, which converts exam arithmetic into improvisation. Scattering the statute of frauds categories instead of listing them as the closed set they are, with the exceptions attached.

Treating promissory estoppel as an afterthought rather than the standing backup theory it is, one line at the end of every formation analysis. And omitting the conditions flowchart, condition or promise, express or constructive, satisfied, excused, or waived, which is the performance section's entire operating logic. The pre built two column shell is in the template library.

FAQ

How long should a Contracts outline run?

Forty to fifty pages at the master stage is normal for this course's rule density; the attack version compresses to three because the two column flags and formulas carry most of the information.

Do I outline the UCC sections themselves?

The handful you cite by number, 2-207, 2-201, the warranty and tender provisions your course covered, with their key language. The number plus a five word gist per section is the working format.

Where do the cases go?

As one line handles at the rule they define, Lucy at objective assent, Hadley at consequential damages, exactly as in every other course. Contracts cases are shorter levers than Con Law's; the rules do the work.

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

Book a call