Should You Write an LSAT Addendum for a Lower Score?

June 23, 2026 :: Admissionado Team

What law schools will see (and what a lower retake actually signals)

Retook the LSAT and scored lower? Law schools will likely see that reportable score history, so stop treating this like a magic trick where the dip disappears. In most cases, it won’t. The real question isn’t whether you can hide it. It’s whether a short addendum changes how a reader understands it. The goal is to manage interpretation, not to argue with the score or pretend it isn’t there.

Admissions readers rarely treat an LSAT history as one isolated number. They usually read it as one important signal inside a broader file—grades, course rigor, writing, recommendations, work, timing. In a holistic review, the application gets judged as a whole. A lower retake can point to several plausible stories: an off day, normal variation, changed testing conditions, a poor retake strategy, or genuine inconsistency. A later increase can also signal persistence and learning. Different readers and schools weigh those patterns differently, so assume a human being is drawing the most likely conclusion from incomplete information.

That’s where an addendum can help—but only sometimes. The score is the signal. An addendum, at its best, explains the condition behind the signal when the raw record would otherwise invite the wrong conclusion. It can’t bargain a score upward, and it shouldn’t read like a defense brief. If the lower retake doesn’t create a meaningful risk of misunderstanding, silence is usually fine. If there was a concrete disruption or condition that makes the dip more understandable, a brief explanation may improve the read. The rest of this guide is about telling the difference.

Do you need an LSAT addendum for a lower second score? A practical decision rule

Most of the time: no, you don’t need an addendum for a lower second score.

An addendum is only worth it when you can offer a specific, believable, one-time reason that changes the obvious reading of the pattern. If a fair-but-not-gullible reader looks at the dip and thinks, “yeah, that’s just ordinary variation,” then silence is usually the stronger move.

A workable rule

Run this quick three-question check:

• Was the drop actually out of character for your testing history—rather than a minor wobble? Small movement often needs no comment.
• Can you name a concrete event on or around test day (illness, family emergency, documented disruption, tech failure) that plausibly affected performance?
• Is it clearly contained—not part of an ongoing issue?

If the answer is yes to all three, an addendum can reduce confusion.

If any answer is no, skip it. Vague explanations like “test anxiety,” “bad test taker,” or “a lot going on” usually don’t help because they don’t give the reader new information.

Also: the downside is real. An unnecessary addendum can:

• put a spotlight on the dip,
• sound defensive,
• or read like you’re blaming circumstances for normal variation.

Worried silence will look suspicious? Usually it won’t. It only starts to look weird when the score pattern strongly suggests there’s a hidden story. Otherwise, silence often reads like professional restraint.

One final filter: if you can’t clarify the situation in under 200 words, it’s probably not worth adding. An addendum doesn’t fix the score; it just helps the reader interpret it more accurately.

If you do write one, keep it bare-bones—something like: A specific, unusual circumstance affected that test administration; it has resolved and does not reflect usual performance.

Is your score drop ‘normal variation’ or a true anomaly? How to think about magnitude and patterns

A lower retake can mean two very different things: ordinary score wobble, or a pattern that asks for context. The separator is rarely the dip itself. It’s what the rest of your testing record suggests.

Here’s the restraint rule: explain the drop only if you can connect it—credibly and specifically—to a limited disruption. If you can’t, silence usually beats a story. Guessing invites the reader to guess along with you.

So don’t panic. Read the pattern.

One weaker result after a stronger score often lands as normal testing noise. A jagged sequence of big swings, or a slide across multiple attempts, can land differently. In that situation, a reader might start wondering about things like uneven preparation, burnout from too many retakes, test-day pressure, or performance that shifts a lot under tight timing.

Three useful checks

• Did something materially change on or right before the exam? Sudden illness, a family emergency, a major technical issue, or another documented disruption is easier to understand than “the day felt off.”
• Was the issue discrete and bounded? A clean, contained event reads more credible than a broad claim that the test “didn’t reflect” ability.
• Did your practice work line up with one score more than the other? If practice was steady and this dip is the outlier, a brief explanation can help. If practice was also erratic, an explanation can start to sound like you’re reverse-engineering a reason.

An addendum’s job is to narrow the range of reasonable explanations—not litigate the exam and not promise what you “would have scored.” If there’s no specific cause you can point to, with some support, the cleaner move is often to let the record stand.

Good reasons vs. weak reasons: what belongs in a score-decrease addendum

A score-decrease addendum has one job: clarify a one-off dip. Not plead your case. Not litigate the testing universe.

Strong addendums point to a specific, checkable disruption that clearly hit one test sitting—and doesn’t look like the new normal. Weak ones drift into fog: generalized stress, frustration, or finger-pointing. Admissions readers are typically scanning for a clean explanation that’s concrete, bounded, and proportionate.

Use this four-part credibility test:

• What happened?
• When did it happen?
• How did it affect performance (in that sitting)?
• Why was it temporary?

Potentially credible buckets include: an acute illness, a family emergency, a major test-site disruption, a technical failure, or an administrative issue outside your control. Buckets—not promises.

What usually doesn’t work: “I was stressed,” “the test was unfair,” or “standardized tests aren’t my strength.” Even if true, those lines don’t explain a one-time drop. Same problem with blaming proctors or the testing organization—if there aren’t dates, concrete facts, and a direct link to performance, it reads like noise.

If documentation exists, name it briefly (doctor’s note, incident report, rescheduling record) and keep moving. The addendum usually shouldn’t turn into a folder of exhibits unless a school asks for more. And keep medical info high-level: what happened and the functional impact—not a diagnosis narrative. If it was real but undocumented, say so with extra restraint and avoid sounding overly certain.

If the real driver was preparation or strategy, think twice. An addendum can accidentally spotlight poor judgment—especially when it sounds like blame. Better is simple ownership:

On [date], [event] affected test conditions and performance during that administration. The disruption was limited to that sitting. Since then, [change], and recurrence is not expected.

How to write the addendum: structure, tone, and length (with a simple template)

You’ve decided to include an LSAT addendum. Great—now make it boring. The best ones are short, factual, and built to explain one thing: an anomaly. In holistic review it’s a clarifying note, not a feature article, so a tight paragraph or two is usually plenty.

Use a four-beat sequence—event, impact, resolution, close.

• Event: Name what happened and pin it to the exact test date.
• Impact: Describe the functional effect in plain terms (acute illness, family emergency, a documented testing disruption, or another temporary issue). Don’t wander into plot.
• Resolution: Say what changed. This is where the reader relaxes.
• Close: One clean line that ties it off.

When you talk about cause, stay measured. “This likely affected performance” reads credible. “This definitively explains the score” reads like you’re trying to litigate the number.

Keep the tone restrained

Neutral beats defensive. Skip exclamation points, accusations, “it wasn’t fair,” and emotional pleas. Skip the adjective buffet. This isn’t where you rehash your study plan, argue that a lower score should be discounted, or explain why you want law school. If it takes pages of backstory to make the point land, it probably doesn’t belong in an addendum.

If documentation exists, a single sentence—available upon request—is enough. Usually no need to attach a dossier.

Simple template

On [test date], [specific event] occurred. As a result, performance was affected in [brief, concrete way]. This was temporary and has been resolved. [Optional: Documentation is available upon request.] [Optional: Other LSAT score(s) better reflect typical performance.]

What not to say: the most common addendum mistakes (and why they hurt)

The #1 addendum mistake: writing like you’re trying to win a case.

If your explanation reads like a defense brief, a rant, or a 12-page “here’s everything that ever happened” file, it usually hurts more than it helps. A strong addendum is boring on purpose: restrained, factual, and tightly aimed at two things—what happened, and how it plausibly affected the score. That’s it.

Remember who’s reading. This person is not deciding whether your anger was justified. They’re typically trying to evaluate a lot of applications efficiently and fairly. So anything that creates work without creating clarity can start to look like the problem.

That’s why the usual offenders—over-defensiveness, blame, long timelines, and extra detail—backfire. Push harder, and you can end up sounding less reliable.

Less helpful: “The proctor was incompetent, the room was chaotic, and the whole process was unfair.”
More helpful: “A testing disruption affected concentration during the exam; the issue was reported at the time.”

Less helpful: “Based on practice tests, the score would have been much higher.”
More helpful: “The score was affected by the disruption described above.” If a later score exists, that result usually does more than speculation ever could.

Same rule for personal material: you rarely need a full medical history, detailed family conflict, or a document dump. Include only what explains timing, duration, and impact. And check consistency—if your addendum clashes with dates or facts elsewhere, it stops adding context and starts raising questions.

Quick scenario guide + final checklist: when to submit, when to skip, and how to sanity-check your draft

Here’s the standard. Submit an LSAT addendum only if it clarifies a specific, unusual score result and reduces the odds a reader misreads it. If the change is small, the reason is fuzzy, or the draft starts sounding like a closing argument—skip it. The job is context, not persuasion. Normal score movement usually doesn’t deserve narration.

Fast decision guide

• Small drop, no distinct disruption: usually skip. Yes, schools can see score histories—but “visible” doesn’t mean “needs explaining.”
• Clear disruption on the lower-score date: consider a short addendum. Illness, a family emergency, or a testing-day administrative problem can justify a brief note when it’s specific, dated, and limited.
• Several takes with uneven results: write only if one administration has a concrete explanation. If not, don’t try to narrate every fluctuation.
• Retook strategically and scored lower: usually skip unless a real event interfered. Don’t use an addendum to spotlight avoidable planning errors.

A restrained template is enough:

On [date], [specific event] materially affected testing conditions for that administration. The issue was temporary or has been resolved, and the remainder of the application better reflects readiness for law school.

Final sanity check

Before submitting, ask: is it under a page, specific and dated, neutral in tone, free of blame, clear about resolution or limits, and unlikely to create new questions? Include only enough detail to make the explanation credible; this shouldn’t read like a case file.

If the draft doesn’t add real clarity, skipping is an affirmative decision. Put that time into higher-upside pieces—your personal statement, resume, and school list strategy. Use the checklist, make the call, draft only if it reduces misinterpretation, then move on.