Performance tasks carry roughly 30% of your NextGen bar exam score — the single heaviest item type — and every session ends your three hours with one. Yet most candidates practice them least, because a 60-minute writing task is the hardest thing to make yourself do on a Tuesday night.
Here's the method: what a PT actually is, a minute-by-minute budget that survives contact with a real packet, and the drafting habits graders reward. It's deliberately boring. Boring is repeatable, and repeatable is what minute 150 of a session demands.
What's in the packet
Every performance task is a closed universe with three parts:
- The task memo — a supervising attorney tells you exactly what to produce: the document type (objective memo, client letter, persuasive brief section), the audience, and the specific questions to answer.
- The File — the facts: correspondence, deposition or interview transcripts, contracts, police reports, business records. Some of it is deliberately irrelevant; real files have noise.
- The Library — the law: statutes, cases, regulations. This is all the law that exists for this task. Your memorized doctrine is not just unnecessary — where it conflicts with the Library, it's wrong.
The legal-research variant (the LRPT) keeps the closed universe but swaps the long draft for targeted research questions with short written answers — more below.
If you knew the MPT, this is its direct descendant; the method transfers almost intact. If you didn't, no loss — the method below assumes nothing.
The 60-minute budget: 10 / 15 / 25 / 10
The failure mode of every unpracticed PT is identical: over-read, under-write, submit a strong first half of an answer. A pre-committed budget is the fix.
Minutes 0–10 — Orient: task memo, then File skim
Read the task memo twice. It is the rubric in disguise: it names your deliverable, your audience (which sets tone — objective for a memo to a partner, persuasive for a brief), and usually enumerates the exact questions to answer. Write those questions at the top of your outline; they are your section headings.
Then skim the File in document order — 30 seconds a document — recording only what each document is and one line of what it contains. You're building a map, not mastery. You'll return with specific questions in hand.
Minutes 10–25 — Extract the law from the Library
Now read the Library properly, one authority at a time, and for each one write a working rule: elements, factors, exceptions, and which party each element favors on your quick sense of the File.
Two disciplines here:
- Statutes first, then cases. Cases usually interpret the provided statute; reading them in that order tells you what each case adds (a test for an element, a factor list, an exception).
- Steal the structure. If a Library case analyzes four factors, your product analyzes four factors. The Library is showing you the rubric's skeleton.
Minutes 25–50 — Draft, application-first
Write in the format the task memo ordered, one enumerated question at a time: brief rule statement, then application — the File's facts pushed through the Library's law — then a one-sentence conclusion per issue.
The habits that separate scoring drafts:
- Cite as you go. Name the File document ("Under the March 12 email…") and the Library authority ("…§ 4(b) requires…") in nearly every paragraph. Graders scan for exactly this tethering.
- Argue the counter, briefly. One sentence acknowledging the other side's best fact — then why it loses — earns application credit twice.
- Spend words proportionally. Two issues, roughly equal points: don't spend forty minutes on the first. The budget inside the draft matters as much as the budget around it.
- No introduction throat-clearing. A memo that opens by restating the assignment for a paragraph has spent 5% of its clock earning zero points.
Minutes 50–60 — Verify against the task memo
Reread the task memo one final time and check your product against it literally: every enumerated question answered? Format and audience right? Then fix only what's broken — a missing conclusion, an uncited assertion, the paragraph you know is mush. Polishing prose in minute 57 is procrastination; closing a gap is points.
The legal-research variant
The LRPT hands you the same closed universe but asks short, targeted research questions — which authority controls, what standard applies, whether a claim survives — answered in a few sentences each, points attached per question.
Method adjustments: the 10/15/25/10 budget compresses (orientation is faster; there's no long draft to structure), answers get anchored to a specific authority by name and section, and length discipline is everything — a 2-point question wants two tight sentences, not a paragraph. It's the same skill provided-resource questions train, which is why the practice compounds: how provided-resource testing works.
How to practice PTs without a grader
The classic objection: essays get graded, PT practice just… ends. Self-grading against a rubric fixes it, if the rubric is honest. The loop we built into BARGO's performance task player:
- Draft on a real 60-minute clock (pausable in practice mode, hard in exam mode — and grading stays shut until the clock says so).
- Score yourself issue by issue: rules accuracy 0–4, application quality 0–4 per issue, with the rubric text in front of you.
- Only then read the model outline — and diff it against what you wrote. The gap is the lesson: which issue did you miss, which File fact did you never use?
- Log it and repeat weekly. PT skill is cumulative; ten self-graded tasks beat thirty read-about ones.
One task a week from the start of prep — not a PT cram in the final fortnight — is the schedule that matches the format's 30% weight. (Our free study plan interleaves exactly this.)
The checklist version
- Task memo twice; enumerate the questions asked
- File skim: map, don't master (30 sec/doc)
- Library: statutes → cases; working rule per authority; steal the structure
- Draft application-first; cite File + Library constantly; counter-argue in one sentence
- Final pass against the task memo, literally
- Self-grade against a rubric; diff against the model; log the gap
Sixty minutes, every session, thirty percent of the score — and unlike doctrine, this skill doesn't decay by exam week. Start with the free task on BARGO and run the loop.