What actually belongs on a Contracts flashcard?
A flashcard should test one retrieval, and the retrieval should be something you will have to do under time pressure on the exam. In Contracts, that is almost always one of four things: recite the elements of a doctrine, identify which body of law governs, apply a line-drawing test, or compute a damages number.
The front should be a prompt, not a topic. "Consideration" is a topic and it teaches you nothing. "What makes a promise supported by consideration under Restatement (Second) § 71?" is a prompt with a checkable answer: a performance or return promise that is bargained for, meaning sought by the promisor in exchange for the promise and given by the promisee in exchange for the promise. Write the back the way you would write it in an exam paragraph, in one or two sentences, so the card trains the sentence you will actually type.
Keep the back under roughly 40 words. If it runs longer, you are carding an outline entry, and you will start recognizing the card instead of recalling the rule. Split it: one card for the elements, one card for the leading exception, one card for the consequence when the element fails.
Which card types are worth making?
Five formats cover nearly everything in a first-year Contracts course. Build in this order, because the first two carry the most exam weight.
- Element cards: "Elements of promissory estoppel under R2d § 90?" — promise, reasonably expected to induce action or forbearance, that does induce it, and injustice avoidable only by enforcement; remedy may be limited as justice requires.
- Governing-law cards: "Contract for custom software plus two years of support — which law?" — hybrid, so apply the predominant purpose test; if goods predominate, UCC Article 2 governs the whole contract.
- Split cards: one card, two columns. "Modification without new consideration?" — common law: pre-existing duty rule bars it absent unanticipated circumstances (R2d § 89); UCC § 2-209(1): binding without consideration if made in good faith.
- Trigger cards: front is a fact, back is the doctrine. "Buyer's acceptance form adds an arbitration clause; both are merchants" → UCC § 2-207(2), additional term enters unless it materially alters, the offer expressly limits acceptance, or objection is timely.
- Formula cards: "Buyer's damages when buyer covers?" — UCC § 2-712: cost of cover minus contract price, plus incidental and consequential damages, less expenses saved.
Which doctrines deserve the most cards?
Weight your deck toward doctrines with multi-element tests and toward the places where the common law and Article 2 diverge, because those divergences are how professors build issues. Offer and acceptance deserves cards on R2d § 24's definition of an offer, the mailbox rule and its exceptions, option contracts under § 45 versus § 87(2), UCC § 2-205 firm offers (signed writing by a merchant, no consideration, three-month cap), and UCC § 2-206's permission to accept by prompt shipment.
Consideration needs cards on bargained-for exchange, the pre-existing duty rule, illusory promises and the good-faith cure of UCC § 2-306 output and requirements contracts, and past consideration including the material-benefit rule of R2d § 86. Defenses need one card per doctrine with its elements: mutual mistake (R2d § 152 — basic assumption, material effect, risk not allocated to the adversely affected party), unilateral mistake, duress, undue influence, misrepresentation, unconscionability as procedural plus substantive, and incapacity.
Statute of frauds is dense enough to justify a small sub-deck: the categories covered, the writing and signature requirements, UCC § 2-201(1)'s quantity term and $500 threshold, § 2-201(2)'s merchant confirmatory memo, and the § 2-201(3) exceptions for specially manufactured goods, admissions, and goods paid for or received. Parol evidence needs cards on total versus partial integration, merger clauses, the fraud and condition-precedent exceptions, and the interpretation split between the four-corners approach and the California approach.
Remedies should be the last quarter of your deck and the most drilled: expectation measured under R2d § 347, cost of completion versus diminution in value, reliance under § 349, restitution, the Hadley v. Baxendale foreseeability limit as codified in § 351, certainty under § 352, avoidability, liquidated damages under § 356 and UCC § 2-718, and the seller and buyer remedy sections 2-706, 2-708, 2-712, 2-713, 2-714, and 2-715.
How should you card cases without wasting hours?
In most Contracts courses cases are illustrations of rules, not authorities you must cite. So do not put briefs on cards. Put the fact trigger on the front and the doctrinal point on the back, in both directions if the case is a workhorse.
Front: "Builder installs Cohoes pipe instead of the specified Reading pipe; identical quality." Back: "Jacob & Youngs v. Kent — substantial performance; damages are diminution in value, not cost of completion, where the breach is trivial and innocent and completion cost is grossly disproportionate." Do the same for Hawkins v. McGee (expectation equals promised value minus value received), Lucy v. Zehmer (objective theory of assent), Hamer v. Sidway (forbearance from a legal right is consideration), Wood v. Lucy, Lady Duff-Gordon (implied promise of best efforts saves an apparently illusory promise), Drennan v. Star Paving (subcontractor bid irrevocable on reliance), Raffles v. Wichelhaus (latent ambiguity, no contract), Frigaliment (burden on the party asserting a trade meaning), Williams v. Walker-Thomas Furniture (unconscionability as absence of meaningful choice plus unreasonably favorable terms), Peevyhouse v. Garland Coal (economic waste), Krell v. Henry (frustration of purpose), and Transatlantic Financing (impracticability requires more than added expense).
You need only the case name and the point. Full Bluebook citations belong in a brief or a paper, not on a memory card, unless your professor requires citation in exam answers — a handful do, and if yours does, add the reporter cite and year to the back.
Does any of this change with an open-book exam?
It changes what you card, not whether you card. This varies by professor, so check the syllabus and any practice exam. If the exam is closed-book, you need verbatim-level recall of element lists and UCC section numbers your professor emphasized. If it is open-book with a code supplement, drop the pure-recitation cards for statutory text and build application cards instead: fact patterns on the front, correct doctrinal route on the back. Open-book exams reward speed of issue-spotting, and issue-spotting is exactly what trigger cards train.
Two other sources of variation matter. First, some professors teach a heavily Article 2 course and some barely touch it; the split cards only pay off in proportion to the coverage. Second, professors differ on whether they want Restatement section numbers cited. If yours drills § 90 and § 71 by number in class, card the numbers. If not, card the rule and skip the number — precision you were never asked for costs you review time.
How should you use AI to build the deck?
Use AI as a converter, not as a source. Paste in your own outline, your class notes, or the professor's slides and ask for cards drawn only from that text. This keeps the deck aligned with the version of the rule your professor teaches, which is the version that gets graded, and it eliminates the biggest risk of generic generation: a model producing a plausible but wrong or nonexistent citation. Contracts is a hallucination-prone subject because case names and Restatement section numbers pattern-match easily.
Verify every section number against the actual text of the Restatement (Second) or the UCC before the card goes into rotation. If a card cites a case you do not recognize from your syllabus, delete it rather than researching it — it is not on your exam anyway. Reject any card longer than a couple of sentences and any card whose front is a bare topic word.
Where AI genuinely adds value is volume of variation. Ask it to generate ten short fact patterns that turn on the predominant purpose test, or five variations on a § 2-207 exchange where the added term's materiality is the live question, and use those as the fronts of application cards. Ask it to produce distractors — near-miss fact patterns where the doctrine does not apply — because discriminating between close cases is what the exam tests. Then space your reviews and mix doctrines together rather than reviewing one chapter at a time; interleaved practice is the reason flashcards beat rereading.
What should you leave off?
Leave off procedural history, dissents your professor did not assign, and full statutory text. Leave off any rule you can already state cold — a deck of cards you always get right is a comfortable waste of an hour. Leave off policy rationales unless your professor grades on them, and if he does, card them as one-line hooks ("why the pre-existing duty rule? — hold-up risk in ongoing contracts") rather than paragraphs.
Also leave off anything you cannot state a rule for yet. Flashcards consolidate understanding; they do not create it. If you cannot explain why Hadley limits recovery, making a Hadley card just gives you a phrase you can recite and cannot use. Read, outline, then card.