The Performance Test: Task Memo, File, and Library

The task memo is the single most important document in the packet, and it should be the first thing you read and the last thing you re-check. It is typically a memorandum from a supervising attorney that tells you precisely what to draft, for whom, and under what constraints. Read it slowly and annotate it as a set of marching orders.

Pull out five things: (1) the product type, whether it is an objective interoffice memorandum, a persuasive brief, a client letter, a demand letter, an opinion letter, a discovery plan, or a closing argument; (2) the audience and tone, because a partner expects neutral analysis, a court expects advocacy, and a client expects plain English; (3) the questions presented or specific tasks the supervisor wants answered, which become your large-scale outline; (4) any formatting or scope instructions, such as 'do not draft a statement of facts,' 'address only the negligence claim,' or 'follow the firm's standard format';

and (5) explicit weighting or sub-tasks, because the memo often signals that one issue carries more points than another.

The California PT is graded against a model answer that closely tracks the task memo, so an examinee who silently changes the product type or skips a requested sub-task forfeits easy points no matter how well they write. There is sometimes a second 'memo to file' or set of guidelines (a drafting guide) that supplies format rules; obey it literally. When the task memo says 'persuasive,' you must argue; when it says 'objective,' you must give both sides honestly, including the weaknesses of your own client's position.

The Library contains the only law you are allowed to use, even if it conflicts with what you learned in bar review. Do not import outside doctrine; if the Library's rule differs from the 'real' rule, the Library controls for that exam. Work the Library before the File so that you know what facts matter. For each authority, extract a clean, applicable rule statement. With a statute, identify the operative elements and any defined terms, exceptions, or effective dates. With a case, capture four things: the issue, the holding, the legally significant facts that drove the result, and the reasoning or test the court announced.

The Library is rarely a single clean rule; it is usually two or three authorities you must reconcile. A statute may set out elements while a case interprets one ambiguous element; an older case may state a general rule and a newer one may carve an exception. Your job is rule synthesis: combine them into one operative framework with elements or factors you can march through. Watch for a case that is factually close to your File (an 'analogous case' the examiners planted so you can argue 'like' or 'unlike') and for a case that cuts against your client (so you can distinguish it).

Building this synthesized rule outline before writing is what separates a passing PT from a fact dump, because the rule outline tells you exactly which File facts to harvest and where each one belongs in your answer.

The File is your evidence locker: client interviews, witness statements, deposition excerpts, contracts, emails, police reports, medical records, pleadings, and the supervising attorney's notes. Resist reading it as a narrative. Instead, read it with your synthesized rule in hand and tag each fact to the element or factor it proves or disproves. Annotate in the margin (for example 'duty,' 'breach,' 'notice,' or 'reasonableness factor 2') so that when you write you can drop the right facts under the right heading instantly.

Crucial File-reading discipline: dates and chronology often decide statute-of-limitations or notice issues, so build a quick timeline; documents frequently contain the dispositive admission or contradiction, so quote precise language; and the File deliberately seeds distractor facts that look important but prove nothing, which you should recognize and skip. Most importantly, harvest the bad facts. The File always contains facts adverse to your client. In an objective product you must analyze them honestly; in a persuasive product you must confront and neutralize them, not pretend they do not exist.

The reading phase is not passive; it is an active sort of every document into the rule framework you built from the Library.

How the Three Packet Components Interlock

Run the same intake routine on every PT so the unfamiliar fact pattern never throws you. Step one: read the task memo and write down the product type, audience, and the list of questions or tasks, which forms your skeleton outline. Step two: skim the table of contents or the first line of each Library and File document to map the universe and see how many authorities and how many fact documents you are dealing with. Step three: read the Library closely and write a synthesized rule outline with explicit elements or factors. Step four: read the File closely, tagging facts to those elements and flagging the adverse ones.

Step five: convert your rule outline into a CRAC- or IRAC-style answer skeleton with headings that mirror the task memo. Only then do you begin drafting. This front-loaded reading and organizing typically consumes nearly half of the 90 minutes, and that investment is correct, because examinees who start writing immediately produce disorganized answers that miss requested tasks. Two recurring traps live in this phase: changing the called-for product (writing a brief when a client letter was requested) and using outside law instead of the Library. Both are avoidable if you obey the task memo and confine yourself to the supplied authorities.

A disciplined intake also prevents the panic that comes from a dense, unfamiliar File, because you are no longer trying to understand a story; you are simply filing facts under rules you already extracted.