Legal Mind Master does not just give you a score. It highlights every section of your essay with color-coded ratings and delivers a full IRAC model answer so you can see the difference between your work and exam-quality analysis.
Below is a first-attempt practice essay on a Torts fact pattern and every comment the grader attached to it — the highlighted passages, the per-issue checklist, and an excerpt of the model answer. Nothing is edited except the student's name.
Sarah, a delivery driver for QuickShip, was texting while driving her company van at 45 mph in a 35 mph zone. She ran a red light and struck pedestrian Marcus, who was jaywalking outside the crosswalk. Marcus, who has a rare bone condition, suffered fractures that would have been minor bruises in a healthy person. His medical bills totaled $80,000.
Jordan demonstrates a solid foundational understanding of negligence structure and correctly identifies the core elements, but this essay has two critical gaps — negligence per se and vicarious liability — that would significantly hurt a bar exam score, as both are heavily signaled by the facts. Additionally, the eggshell plaintiff rule was framed as a defense argument rather than a plaintiff-protective doctrine, which is a substantive legal error that must be corrected. Jordan's next steps should be: (1) memorize the negligence per se two-part test and practice spotting statutory violations in fact patterns; (2) always ask 'who is the employer?' when a tortfeasor is acting in a work capacity; and (3) practice writing rule statements with authority citations before applying them to facts, rather than jumping straight to conclusions.
AI-estimated IRAC component performance
Jordan's essay — annotated feedback
This is a significant missed issue. Sarah violated at least two traffic statutes — speeding (driving 45 mph in a 35 mph zone) and running a red light — and likely a distracted driving statute (texting while driving). Negligence per se is a doctrine that substitutes statutory violation for the common-law breach element when the plaintiff is in the class of persons the statute was designed to protect and the harm suffered is of the type the statute was designed to prevent. This is highly testable and the facts scream for it.
Rule: Under the negligence per se doctrine (Restatement (Second) of Torts § 286; majority rule), a defendant's unexcused violation of a statute establishes breach as a matter of law if: (1) the plaintiff is within the class of persons the statute was designed to protect, and (2) the harm suffered is within the class of risks the statute was designed to prevent. Some jurisdictions treat statutory violation as only evidence of negligence (minority/some states).
In one line: Sarah violated traffic statutes prohibiting speeding, running red lights, and texting while driving; because Marcus is a pedestrian within the class of persons these statutes protect and his injuries are the type of harm they were designed to prevent, Sarah is negligent per se — breach is established as a matter of law.
Full treatment: The issue is whether Sarah's statutory violations establish breach through negligence per se. Under the majority rule (Restatement (Second) of Torts § 286), a defendant's unexcused violation of a statute constitutes negligence per se when the plaintiff belongs to the class of persons the statute was designed to protect and the harm is of the type the statute was designed to prevent. Here, Sarah violated at least three statutes: the speed limit (45 in a 35 zone), the traffic signal law (running a red light), and likely a distracted driving/texting statute. All three statutes are designed to protect road users — including pedestrians like Marcus — from exactly the type of collision that occurred. Therefore, Sarah's breach is established as a matter of law under negligence per se, without needing to apply the reasonable person standard. Even under the minority view treating statutory violation as mere evidence of negligence, the three simultaneous violations would be highly probative of breach.
This is a significant missed issue. The fact pattern explicitly states Sarah is a delivery driver for QuickShip and was driving a company van. These facts are a classic setup for respondeat superior vicarious liability, which would make QuickShip jointly and severally liable for Marcus's damages. This is highly testable and the facts are unambiguous — Jordan must address it.
Rule: Under the doctrine of respondeat superior (Restatement (Third) of Agency § 7.07), an employer is vicariously liable for the tortious acts of an employee committed within the scope of employment. An employee acts within the scope of employment when the conduct is of the kind the employee was hired to perform, occurs substantially within the authorized time and space limits, and is motivated at least in part by a purpose to serve the employer. Frolic vs. detour: a minor deviation (detour) does not take the employee outside scope; a major deviation (frolic) does.
In one line: As Sarah's employer, QuickShip is vicariously liable under respondeat superior because Sarah was driving the company van in the course of her delivery duties — squarely within the scope of her employment — when the accident occurred.
Full treatment: The issue is whether QuickShip is vicariously liable for Sarah's negligence under respondeat superior. Under this doctrine (Restatement (Third) of Agency § 7.07), an employer is liable for an employee's torts committed within the scope of employment. An act is within scope when it is of the kind the employee was hired to perform, occurs within authorized time and space, and serves the employer's purpose. Here, Sarah was a delivery driver operating QuickShip's company van — she was doing exactly what she was hired to do at the time of the accident. Her negligent manner of driving (texting, speeding, running a red light) does not take her outside the scope of employment; the frolic/detour doctrine only removes liability for substantial personal departures, not negligent performance of job duties. Therefore, QuickShip is jointly and severally liable for Marcus's $80,000 in damages. Marcus should name QuickShip as a defendant, as it likely has deeper pockets and insurance coverage.
In the app, each missed issue links to its place on the mind map and is flagged for spaced-repetition review automatically.
Model IRAC answer — excerpt (1 of 8 issues)
Issue 6: Eggshell Plaintiff Rule
Rule: Under the eggshell plaintiff (or "thin skull") rule, a defendant takes the plaintiff as they find them. A defendant is liable for the full extent of the plaintiff's injuries, even if those injuries are far more severe than what a normal, healthy person would have suffered, provided the type of harm was foreseeable. Restatement (Second) of Torts § 461 provides that a negligent actor is subject to liability for harm that is more serious than expected due to the plaintiff's pre-existing physical condition. The rule requires only that some physical harm was foreseeable, not that the precise extent of harm was foreseeable.
Application: Marcus suffers from a rare bone condition that caused him to sustain serious fractures from an impact that would have caused only minor bruising in a healthy person. His medical bills totaled $80,000 — far exceeding what a typical plaintiff might incur from a similar collision. Under the eggshell plaintiff rule, Sarah cannot escape liability for the full $80,000 simply because Marcus's injuries were more severe than anticipated. It was entirely foreseeable that striking a pedestrian with a motor vehicle would cause some physical injury. The fact that Marcus's condition magnified those injuries is irrelevant to Sarah's liability. Sarah must take Marcus as she found him — a person with a rare bone condition — and is liable for the full extent of his damages.
Conclusion: Under the eggshell plaintiff rule, Sarah is liable for Marcus's full $80,000 in medical bills despite the role of his pre-existing condition in amplifying his injuries.
The full model answer covers all 8 issues in the same Rule / Application / Conclusion form.
Most essay feedback tells you what you got wrong at a high level. You receive a score, maybe a paragraph of comments, and a model answer to compare against. But comparing your essay to a model answer is like comparing a rough draft to a finished painting — you can see the gap, but you cannot see where each brushstroke went wrong.
What you actually need is feedback inside your essay — on your words, your analysis, your rule statements. You need to know which sentence was strong, which paragraph missed a key element, and which conclusion jumped ahead without applying the facts.
That is exactly what Legal Mind Master's inline feedback provides.
When you submit a practice essay, the AI analyzes your writing section by section and returns your essay with color-coded annotations:
Sections where your issue identification, rule statement, and fact application meet or exceed exam expectations.
Sections that demonstrate understanding but lack depth — a rule stated without all elements, or analysis that could be more thorough.
Sections with missing issues, conclusory analysis, incorrect rule statements, or facts not applied to the rule.
Each highlighted section includes a specific comment explaining why it received that rating and what you could improve. This is not a vague "good job" or "needs improvement" — it is targeted, actionable feedback on your actual writing.
See how the AI highlights your essay section by section with color-coded ratings and specific comments on your analysis.
Watch how the AI identifies every issue spotted and missed, then maps your gaps to the interactive mind map.
After reviewing your inline feedback, you receive a complete IRAC model answer for the same fact pattern. This is not a generic outline — it is a fully written analysis structured the way a passing bar exam essay should be structured:
Every legal issue present in the fact pattern is identified and framed as a clear question — including issues you may have missed entirely.
The applicable legal rule for each issue, stated with all required elements. MBE subjects use federal and common law rules; California subjects reference state-specific codes.
Each fact from the pattern is applied to each element of the rule. This is where most students lose points — the model shows you what thorough fact application looks like.
A clear conclusion for each issue, supported by the analysis above. The model demonstrates how to reach a definitive answer while acknowledging counterarguments.
Having both your annotated essay and the model IRAC answer side by side creates the most effective learning loop: see what you wrote, understand where it fell short, and see exactly what exam-quality analysis looks like for the same fact pattern.
| Feedback Type | Model Answer Only | Score + Comments | Legal Mind Master |
|---|---|---|---|
| Inline annotations on your essay | |||
| Color-coded section ratings | |||
| Full IRAC model answer | Sometimes | ||
| Identifies missed issues | Indirectly | Sometimes | |
| Maps gaps to visual framework | |||
| Instant feedback |
Legal Mind Master's feedback is personalized — the AI uses your name throughout its analysis, not generic labels like "the student." This makes the feedback feel like working with a dedicated tutor who knows your work, not a faceless grading machine.
The AI is also jurisdiction-aware. When you practice MBE subjects, the model answer uses federal and common law rules. When you practice California-specific subjects like Community Property or Professional Responsibility, it references the relevant California codes and standards.
Stop guessing whether your analysis is good enough. Get instant, section-by-section feedback with a full IRAC model answer to learn from.
One free AI essay grading trial included. Upgrade for unlimited access.