Scriba
Guides·Exams·8 min read·Updated July 2026

Law School Exam Strategy: How to Write for the Rubric

Law-school exams are rubric-graded, not read for style. The professor made a list of issues, assigned points to each, and is scanning your answer for the sentence structures that map onto that list. Once you internalize that, exam writing stops being about eloquence and starts being about coverage.

The rubric mindset

Imagine a spreadsheet. Each row is an issue the professor built into the hypo. Each row is worth 3–8 points. You get points for (1) spotting the issue, (2) stating the rule, (3) applying the rule to the facts, and (4) reaching a defensible conclusion. Miss the issue, get zero. Spot the issue, state the rule, and stumble through the analysis, get most of the points.

Partial credit dominates

A weak analysis on a correctly spotted issue outscores a beautiful analysis on the wrong issue. Coverage beats depth on the margin.

IRAC per issue, always

Structure every issue as a mini-IRAC: one sentence stating the issue, one stating the rule, two to four applying the rule to the facts, one concluding. Then a hard paragraph break, and start the next issue. Long undifferentiated paragraphs make graders miss your points — literally.

The four sentence starters graders look for

  1. 'The issue is whether…' — signals to the grader that you've identified an issue. Zero ambiguity.
  2. 'Under [doctrine/case name], the rule is…' — signals that you know the source of the rule, not just the vocabulary.
  3. 'Here, the facts show…' — signals that you're applying, not restating. Do this even if the application is obvious.
  4. 'Therefore, [party] likely [wins/loses]…' — a conclusion that acknowledges uncertainty is preferred over a bare declarative. Real practice is probabilistic; exam answers should sound like it.

Time budget

On a three-hour exam, spend the first 15 minutes reading and issue-spotting on scrap paper. Sketch the IRAC skeleton for every issue you see before writing a word of prose. Then divide the remaining time proportionally to the point value of each issue, if disclosed. If not disclosed, weight roughly by fact-density.

The counterargument move

For any issue where the analysis is close, add one sentence starting with 'However, [opposing party] would argue…' followed by their strongest counterargument, and then resolve it. This is the sentence that separates B+ answers from A- answers.

What not to do

  • Don't restate the fact pattern. The grader wrote it. Every word restating it is a word you didn't spend on analysis.
  • Don't editorialize. 'This is a fascinating question' is negative signal. So is any policy detour that isn't asked for.
  • Don't cite cases the professor didn't teach. It reads as memorized outline rather than in-class engagement.
  • Don't skip conclusions. A missing conclusion loses the conclusion points even if the analysis is perfect.

Where Scriba fits in

Scriba's exam simulator generates hypos in the same IRAC-per-issue format 1L professors use, grades them against a four-part rubric (issue spotting, rule accuracy, analysis, conclusion), and shows you which axis you lose points on. After a dozen practice runs, you'll know whether your weak spot is spotting, stating, or applying — and you'll fix the right one.

Frequently asked

How much time should I spend on practice exams?

One full practice exam per subject in the final two weeks, taken under real time constraints, is worth more than 20 hours of re-reading your outline.

Should I memorize case names for the exam?

Yes — enough to identify the rule's source. Professors reward accurate case attribution and penalize made-up cases.

Is it OK to conclude 'it depends'?

Yes, if you show what it depends on. 'The result depends on whether the fact-finder concludes the reliance was reasonable, and the stronger argument is…' is a strong answer. Bare 'it depends' is not.

Turn this into your workflow.

Scriba is a notebook-style desktop workspace for law students. 7 days free, cancel any time.

Start free trial
More guides
How to Brief a Case: The FIRAC Method (Examples)
A step-by-step FIRAC walkthrough using Palsgraf v. Long Island Railroad — what to cut, what to keep, and how to build a brief you can actually use in class.
IRAC vs FIRAC vs CREAC: Which Should a 1L Use?
Three formats, one honest comparison. When each works, when each fails, and why FIRAC is the default for reading briefs while CREAC belongs on your exam.
How to Read Cases Faster in Law School
A three-pass reading protocol that cuts your case-reading time in half — orient, hunt, brief — plus the passages you can safely skim.
Using AI in Law School Within Your Honor Code
What ABA Model Rule 5.3 and most law-school honor codes actually say about AI, the four uses that are almost always safe, and the three that get people in trouble.
Outlining a 1L Course Without Losing Your Mind
The seven-step outlining workflow used by top 1Ls — from syllabus scaffold to attack sheet — and the three shortcuts that quietly cost you points.
Cold-Call Preparation: What to Actually Do the Night Before
A calm 20-minute checklist that beats re-reading the whole case — issue, rule, holding, and the two follow-ups your professor will ask.
Spaced Repetition for Law Students (Beyond Flashcards)
Why elements-based cards beat definition cards, the D1/D3/D7/D14/D30 review schedule, and how to build a deck that survives finals.
Bluebook Basics for 1Ls: The 20% That Covers 80% of Cites
Case names, reporters, pinpoints, short forms, and signals — the compact reference every 1L needs before their first memo.
How to Take Law School Notes You'll Actually Use
Note-taking systems built for outlining: the two-column method, why verbatim capture hurts recall, and where AI transcription helps (and where it doesn't).
Case Brief Template (With FIRAC Example)
A reusable case brief template in the FIRAC format, plus a full worked example. Copy the structure, adapt it to your professor's expectations, and stop rewriting the wheel for every reading assignment.