LSAT Addendum for a Lower Score: Should You Write One?

When a Lower LSAT Score Warrants an Addendum—and When It Doesn’t

A lower later LSAT score does not automatically call for an addendum. Admissions already sees your full testing history through LSAC. The addendum is not a disclosure document. It is an interpretation tool: a brief, factual note that helps a reader understand one score more accurately when context actually changes the picture.

The useful model is a short memo, not a defense speech. It explains what happened, how that circumstance affected that specific test administration, and why the lower result should not be treated as the best measure of your likely performance. In a process that often relies on holistic review—schools read the file as a whole, not as one number in isolation—that kind of clarification can help.

What an addendum is not matters just as much. It is not a second personal statement. It is not the place to vent about the test, challenge LSAC rules, blame a school, or ask for sympathy or extra consideration. Once the tone turns defensive, emotional, or argumentative, the document usually stops helping.

The committee’s practical question is straightforward: was this lower score a one-off disruption, or is it more likely your usual level? Submit an addendum only if it materially improves that judgment. If you have no new, decision-relevant context to offer, silence is often stronger than a long explanation. Optional does not mean everyone should write one. It means write one only when it makes your score history easier to read. Short and useful beats heartfelt every time.

Most LSAT Swings Are Normal; Patterns Matter More

Not every LSAT change carries signal. Admissions readers generally understand that modest score movement can fall within ordinary test-to-test variation, not reflect a meaningful shift in underlying ability. The practical question is not whether any drop is inherently bad. It is whether the pattern leaves a reviewer with an unclear or unhelpful impression.

That is where score bands matter. Put simply, a score band is the range around a reported score that accounts for normal variation from one sitting to the next. It is a reminder that a small swing is not automatic evidence that something changed in a lasting way. An addendum earns its place only when it helps a reader distinguish a likely blip from a result that appears to signal something more.

There is no single admissions formula, either. Some offices may care more about the highest LSAT. Others may pay closer attention to the sequence of scores as part of a whole-file review, reading the application together rather than score by score. The safer assumption is that a person, not a spreadsheet, is asking a simple question: what story do these numbers tell?

That makes pattern and fit the real tests. A one-off dip surrounded by stronger performances usually reads differently from a steady downward line across multiple administrations. Reviewers also look for consistency across the file: do the scores broadly fit the writing, academic record, and rest of the application? If yes, silence is often fine. If the drop creates genuine ambiguity, a brief addendum can clarify the point without overexplaining.

Lower LSAT Score? Use This Three-Part Addendum Test

Write an LSAT addendum only if it changes how a reviewer reads the score. If you can point to a specific, time-bound disruption that plausibly drove the lower result, it can help. If you cannot, skip it. In many files, silence is the better choice than an explanation that is vague, generic, or obviously just an attempt to soften a disappointing score line.

Run a simple three-part test. An addendum usually earns its place only when the drop is noticeable enough to invite questions, the cause is concrete and dated, and the context actually improves the interpretation of that sitting. A brief illness during test week, a family emergency, a proctoring or technical problem, or a problem affecting an approved accommodation can qualify because each gives the reader a clearer account of what happened.

Leave it out when the explanation is broad, vague, or self-defeating. General stress, ordinary test-day nerves, “I underperformed,” or “I did not prepare enough” rarely help. Unless there was an unusual, time-bound reason you can state neutrally and briefly, those explanations add words without adding judgment. Worse, they can make the lower score more prominent and signal weak decision-making.

Retakes change the calculus. If a later score improved, keep the addendum short: identify the disruption and note that the later result is the better indicator. If the later score did not improve, be much more careful. At that point, an addendum should appear only if the disruption is genuinely specific and credible; otherwise it risks sounding like excuse-making rather than useful context.

Explain the Score With a Tight Cause-and-Impact Chain

A strong LSAT addendum does one job: help the reader interpret the score. It is not a hardship narrative. The admissions question is narrower—was there a discrete disruption, what concrete testing consequence did it create on that test day, and is there a reason this result should not be treated as your usual level?

Organize the explanation around three points: the event, the test-day effect, and the resolution. Keep the chain tight. “A difficult month affected performance” is too diffuse to carry much weight. “A medication change caused severe insomnia for two nights before the exam, which affected focus and pacing; the issue was then resolved with a physician” is stronger because it links a specific disruption to timed performance.

Credibility comes from observable details, not dramatic language. Dates matter. So does the exam format, if relevant. A reschedule attempt, a medical visit, or an approved accommodation can also anchor the account. Broad blame usually weakens the case. Do not fault a proctor, test center, or institution unless you can describe a specific interruption clearly. And unless a school asks for them, you usually do not need to attach records.

Then stop. Include only the facts needed to explain the score. Lengthy mental-health histories, diagnoses, or graphic medical detail usually add heat without adding clarity. A useful test is blunt: does each sentence help explain this score, on this day?

Finally, check the rest of the application for consistency. If the addendum says a major disruption affected functioning in June, the résumé, essays, and activity descriptions should not quietly imply the opposite.

Write the LSAT Addendum Like a Brief: Format, Tone, Template

If an addendum is warranted, treat it as a brief, not a personal essay. One tight, neutral, memo-like paragraph—usually three to six sentences—is enough. State the affected test date, identify the disruption, explain its impact on that sitting, and note what changed afterward. If you have stronger evidence of ability, mention it briefly rather than arguing for a different result.

Admissions readers usually skim addenda for decision-relevant facts. Format matters. Use active voice, concrete nouns, and few adjectives. Keep the tone professional, factual, and forward-looking. Name one disruption, not every stressor around the exam. Give enough context to make the issue understandable, then stop. Skip the full prep timeline, the emotional arc, and any attempt to persuade a school to discount the score.

Template

On [test date], [specific disruption] affected the administration of the LSAT. As a result, [brief impact on performance]. [What changed afterward or how the issue was addressed]. [Optional: a later score or other evidence] better reflects current ability.

Illustrative example

On the April 2024 LSAT, a prolonged technical interruption broke concentration early in the exam. That disruption affected pacing for the remainder of the test. The issue was reported through the testing platform, and later testing conditions were stable. The June 2024 score is the better indicator of current performance.

Before you submit, run four checks: the tone is factual rather than aggrieved; the length stays tight; every detail matches the rest of the application; and any mention of reporting the issue or seeking accommodations is limited to one clause. If documentation exists, a brief note that it is available is enough. Attach materials only if a school asks.

Common Disruptions: What to Include, What to Avoid

Scenario-based addenda work best when they isolate one discrete disruption, explain how it affected that test sitting, and, where relevant, note any formal steps you took without turning the document into a complaint. The goal is straightforward: show that this administration was atypical and that the score should be read in that context.

Illness or injury. Name the issue plainly, then connect it to test-day functioning: timing, concentration, or stamina. If true, note recovery or explain why the circumstance was limited to that sitting.

Family emergency or other acute disruption. Keep the timeline tight. One or two sentences is usually enough to establish that the day was unusual without drifting into personal narrative.

Logistics or technical problems. Specificity matters more than outrage. A useful description identifies a late start after repeated disconnections and multiple proctor interruptions; saying only that “the proctor was bad” does not. If you reported the issue, opened a case, or sought a retake, say so briefly and neutrally.

Accommodations. Use the same approach. If an approved accommodation was unavailable, changed, or disrupted, describe the operational impact and, if true, note that a later administration reflected the intended conditions.

When you mention a complaint or retake request, report the fact; do not argue the merits. Avoid broad accusations, details you could not support if questioned, or statements that create a new concern, such as suggesting an ongoing unmanaged condition or persistent instability without any sign of resolution. In this setting, a supported, restrained explanation helps; a vague or combative one usually hurts.

LSAT Score-Drop Addenda: Avoid the Common Misfires, Then Run a Final Check

Your LSAT score-drop addendum has one job: clarify a real, time-bound disruption. Keep it brief, factual, consistent with the rest of the file, and free of blame. If it cannot meet that bar, skipping it is usually the stronger move. Admissions committees read many applications without addenda; extra explanation helps only when it reduces ambiguity.

Where Addenda Fail

Start with usefulness. The weakest versions dwell on anxiety, frustration, or disappointment but give the reader nothing concrete to assess. An addendum should tell the reader what happened, when it happened, and why that context matters.

Then comes tone. A paragraph that complains about LSAC, a proctor, or testing conditions rarely helps, even when the frustration is real. Defensive writing creates more concern than clarity. The same restraint applies to private medical or personal detail: include it only when it is needed to make the timing and impact understandable.

Finally, protect your credibility. If the test date, work demands, caregiving duties, or other facts do not align with the rest of the application, the addendum does damage. And if the real issue reflects a broader academic pattern, that usually belongs in a different explanation, not an LSAT-specific one.

The Final Go/No-Go Screen

Leaving the section blank is not automatically suspicious; many files are reviewed without optional explanations. Before submitting, ask:

• Is an LSAT addendum optional at this school?
• Can this stay under one paragraph?
• Does it name the test date and a specific, time-bound disruption?
• Does it describe the impact concretely and show that the issue has passed or been addressed?
• Is the tone neutral, and is every fact consistent with the rest of the file?

If every answer is yes, submit it. If not, let the rest of the application speak.

Two hypothetical files reach the same reader on the same afternoon. One includes a full paragraph about stress, unfair proctoring, and how disappointing the lower score felt, but never pins the issue to a date or explains why the dip should be read as an exception. The other stays to a single paragraph, names the test date, ties the decline to a specific work crunch that has since passed, states the impact plainly, and matches the timeline elsewhere in the application. The first adds noise. The second adds usable context. That is the standard: if the paragraph adds clear, consistent context in a neutral tone, submit it; otherwise, let the rest of the application speak.