How to write an IRAC answer.

IRAC is a writing structure, not a style. A well-written IRAC answer can be conversational or formal, brief or detailed — what matters is that each section does its distinct job. The Issue frames the legal question. The Rule states the governing law. The Application maps the rule onto the specific facts. The Conclusion answers the Issue directly. Strip any section out and the analysis collapses.

Law students often get the first two sections right early on. They can identify an issue and cite a rule. The grades are made and lost in the Application — typically the longest section and where most of the rubric points live. A weak Application restates the rule or summarizes the facts without connecting them. A strong Application says: 'Here, [specific fact from the problem] establishes [element of the rule] because [reason], but [counterargument]...' It uses the facts as evidence for a legal conclusion.

The Conclusion is not the place for new analysis. Its job is to answer the Issue in one or two sentences — 'Therefore, a contract was formed' or 'Therefore, Pat's claim for negligence will likely fail on the breach element.' If you find yourself adding reasoning in your Conclusion, move it to Application.

Most exam fact patterns contain several issues, not one — so real exam answers are not a single IRAC but a chain of them, often nested. You'll see this written as IRAAC (two competing applications), CRAC (conclusion-first, common in legal writing), or MIRAT, but they are all the same skeleton: name the question, state the law, argue the facts both ways, answer. The variation that matters most for exams is breaking a big claim into its elements and running a mini-IRAC on each contested element. Negligence isn't one issue; it's duty, breach, causation, and damages — and the professor has usually made only one or two of them genuinely arguable.

Issue-spotting is what actually separates grades, and it happens before you write a word. Strong exam-takers read the fact pattern twice: once to understand the story, once with the rule structure in mind, flagging every fact that triggers an element or an exception. A fact placed in a hypo on purpose is almost always doing legal work — the wet floor, the 'I was joking,' the two-day delay. If a fact doesn't map to a rule, ask why the professor included it. Missed issues score zero no matter how polished your writing; this is why allocating the first few minutes to a margin issue-list outscores diving straight into prose.

Allocate words by where the points are. The Rule should be tight — state it correctly and move on; you don't get extra credit for a paragraph of black-letter law. The Application is where the rubric concentrates its points, so it should be the longest section and should argue both sides of every genuinely contested element. A useful discipline under time pressure: budget your minutes per issue in proportion to how many elements are actually in dispute, and write the Application for the closest calls first, since that's where partial credit is densest.

Issue-spotting is a skill you practice, not a talent you either have or lack. The best training is working through past exams for the specific course with a professor's model answer in hand, then comparing your issue list to theirs. You will quickly find your personal pattern — most students consistently miss the same category of issue, whether that's defenses, procedural prerequisites, or issues buried in the last paragraph of the fact pattern. Identifying your blind spots and drilling against them is more efficient than writing unguided practice answers, because each targeted repetition fixes a specific gap.

The CRAC variation — Conclusion, Rule, Application, Conclusion — puts a one-sentence answer at the top, before the analysis. This is common in legal writing courses and professional memos because readers want the bottom line first. On exams, whether IRAC or CRAC is preferred depends on the professor; some reward leading with a tentative answer, others want you to build toward it. When in doubt, use standard IRAC — it is never wrong. If you use CRAC, keep the opening conclusion short and hedged ('Probably liable for negligence') and move immediately to the Rule; the opening conclusion is not a substitute for analysis.

A practical pre-writing system for IRAC under time pressure: (1) Read the call of the question first — 'Discuss Alex's potential liability' tells you the scope before you read the facts. (2) Read the facts once for story, once for legal triggers. (3) List every issue, grouped by claim. (4) Rank them by how much is genuinely in dispute — contested elements get full IRAC, clear elements get one sentence. (5) Write in issue order, not fact order. This sequence keeps the answer organized even when the fact pattern is designed to confuse and prevents the most common exam failure: writing beautifully about the wrong things.

The Rule section is where precision pays off. A vague rule — 'negligence requires a breach of duty that causes harm' — is technically not wrong but earns partial credit because it omits the elements the professor will check against. A complete rule names the test, its elements, and where they come from: 'A defendant is liable for negligence if they owed a duty of reasonable care to a foreseeable plaintiff, breached that duty by falling below the reasonable person standard, and the breach was both the but-for and proximate cause of a cognizable harm.' That sentence is a checklist. The professor reads it and sees that you know the doctrine precisely enough to walk each element, which is what earns full points before you've written a word of Application.

Knowing which issues to give full IRAC and which to dispatch in a sentence is the efficiency skill that separates B+ answers from A answers under time pressure. An issue deserves a full IRAC — including a counterargument — when there is a genuine argument on both sides given the specific facts in the problem. An issue deserves one sentence when it is clear: 'Duty is undisputed — the defendant owned the premises and owed a duty of care to all invitees.' Professors do not reward lengthy analysis of uncontested elements; they reward recognizing the close call and unpacking it. Train yourself to decide, before you write, whether each element is clear, close, or unclear — and allocate your words accordingly. This three-tier sorting, done in your issue list before you begin writing, is what keeps your answer from spending two paragraphs on something no one disputes and three sentences on the element the whole exam hinges on.

Use the Application to do real legal work on both sides, not to pick a winner immediately. The structure that earns the most points is: state the best argument for the plaintiff/prosecutor, state the best counterargument for the defendant, then explain why one side is stronger and why. 'Here, the defendant failed to post a warning sign (plaintiff's argument). Defendant may contend ten minutes was too short to respond (defendant's argument). However, the better view is that actual notice of a specific, fixable hazard requires immediate action, not a wait-and-see approach (resolution with reasoning).' That three-part structure — argue, counter, resolve — applied to each contested element is what a high-scoring Application looks like.