Case Law Cheat Sheet

Building something you'll actually use during an exam or trial prep

The problem most people have with case law reference materials isn't that they don't exist. It's that the ones they end up making are useless when the pressure is on. I've seen students spend three weeks compiling dozens of case summaries, only to flip through them during a timed exam and realize half the entries were missing the holding altogether or were too vague to apply to a different fact pattern. A Case Law Cheat Sheet only works if you built it for actual retrieval under stress, not as an academic exercise in neat handwriting. Here's how the process actually goes. You don't start by highlighting everything in the casebook. You start by identifying which cases your professor or bar examiner actually tests on. In my contracts course, for example, I noticed that out of roughly 40 assigned cases, only about twelve kept showing up in exams, usually in slightly distorted fact patterns. That's the set you build around. Everything else gets a pass unless you have time to refine later.

Case Law Cheat Sheet

The format I ended up using consistently was a three-column layout on index cards or a tight spreadsheet. Left column: the case name and citation. Middle column: the one-sentence holding, not a summary of facts. Right column: the distinguishing factor—what factual change would flip the outcome. The distinguishing factor column is where most people fail. They'll write the holding correctly but won't capture what makes the rule flexible enough to apply to a new scenario. I ran into a specific issue with my evidence class that showed me why the standard approach breaks down. The professor kept testing on evidence rules using hypotheticals that combined two different exceptions in the same question—like hearsay and character evidence together. My original cheat sheet had each case isolated, so when the exam question blended them, I couldn't quickly see which rules interacted. The workaround was to add a cross-reference notation. Next to each key case, I flagged which other cases it commonly appeared alongside, and I made a separate mini-section listing these interaction pairs. It took about twenty minutes to reformat, and it cut my recall time on multi-issue questions significantly. The holding should never exceed one sentence. If you need more, you're summarizing the opinion instead of extracting the rule. For instance, writing "the court held that a promise supported by past consideration is unenforceable" tells you exactly what to do. Writing "the court discussed the history of consideration doctrine and concluded that past consideration does not serve as valid consideration" is wordy and forces you to translate during the exam. The first version is closer to what you actually need in the moment.

Citations matter more than people admit. Not for memorizing the volume and page number, but for knowing the jurisdiction and court level. A state supreme court case on contract formation behaves differently than a federal district court case on the same topic, even if the reasoning looks similar. I used to skip the court identifier and just write the year. That cost me two points on a midterm when I cited a 2018 New York case and the grader expected me to note it was a state decision applying New York common law rather than the Restatement. There's a trap with the distinguishing factor column that catches a lot of people. Beginners tend to write the obvious factual difference from the case itself. But the useful version describes a plausible real-world variation that isn't in the case at all. If the case turned on whether the goods were specially manufactured, don't just write "not specially manufactured." Write what that actually looks like in practice—standard inventory items, bulk commodity purchases, items already produced before the contract formed. That's what lets you apply the rule when the facts shift slightly. Timing is also a factor most people ignore. A cheat sheet built four weeks before an exam is not the same thing as one built four days before. The closer you get, the more you should be stripping content, not adding it. I've watched people try to cram new cases into an already full reference at the last minute, which usually just creates clutter. At that stage, the only productive move is deleting entries you haven't used in self-testing and tightening the language on the ones that remain.

The biggest limitation of this approach is that it doesn't help with cases you've never seen before. If the exam throws a completely unfamiliar precedent at you, the cheat sheet is irrelevant. It works best when the test is drawn from a recognizable pool of authority, which is true for most law school courses and many state bar subjects. For the bar exam specifically, you're better off relying on a prepared outline or MBE resource that's already been stress-tested across hundreds of questions. A self-made cheat sheet can supplement that, but it shouldn't replace it. I also found that the physical format changes how effectively you use it. Writing by hand on index cards forces brevity and makes it harder to copy entire paragraphs. But it's slow to create. Typing a spreadsheet is fast and searchable, but it tempts you to be verbose. The tradeoff depends on your timeline. If you have a week or more, hand-write the first draft and type it later if you need to revise. If you're short on time, type it straight through and then edit ruthlessly. The most useful thing I learned was that a good cheat sheet isn't defined by how much it contains. It's defined by how fast you can find what you need when you're stuck. Anything that takes more than three seconds to locate is taking up space it shouldn't. That usually means consistent formatting, bolded key terms, and a table of contents or quick-index page if you're using a document rather than loose cards. I stopped using color coding because I wasted more time picking colors than I saved searching. Black text with strategic bolding was faster and simpler.

If you're starting from scratch and want a template, the structure is straightforward. Case name and citation at the top. One-line holding. Distinguishing factor. Cross-references to related cases. That's it. Some people add a fourth column for the policy rationale behind the rule, but I'd skip that unless you're preparing for an essay exam where policy discussions carry significant weight. For multiple choice or quick recall, the policy column just adds noise. The main takeaway is that the document itself is almost secondary to the method of building it. The cases you choose to include, the way you phrase the holdings, and how often you self-test using the sheet are what determine whether it functions under pressure. A mediocre sheet built through repeated retrieval practice will outperform a meticulously crafted one that sits untouched until exam day.