How to write an issue-spotter answer that collects points

The person grading your exam is working from a rubric. Not a general impression, a list: issues that should have been raised, and for each one, whether you applied the rule to the facts. They are reading fast, with a stack to get through, looking for the items on that list.

Almost everything that makes an issue-spotter answer score well follows from that one fact, and almost every way students lose points is a way of writing for a different reader than the one they have.

Coverage beats depth, up to a point

A competent treatment of six issues will usually outscore a beautiful treatment of two, because the four you never reached are worth zero no matter how good the two were.

This runs against every instinct trained by undergraduate essay writing, where depth and elegance were the point. Here the rubric has line items, and an elegant paragraph earns the same credit as a plain one that reaches the same conclusion. Spend the saved time on the issue you have not written yet.

The limit is real, though: naming an issue without applying it to the facts collects very little. Points live in the application. What you are aiming for is many issues, each genuinely applied, not a list of issue names.

Signal the issue so it registers

Your grader is scanning. Make each issue easy to find: name it, state the rule in a sentence, apply it to the specific facts in the prompt, conclude. Then start a new paragraph for the next one.

A new paragraph per issue is worth more than it sounds. An answer that treats four issues inside one dense block invites the grader to miss two of them, and a point they did not see is a point you did not get. This is not about presentation for its own sake. It is that a scanning reader with a checklist finds what is structurally obvious and misses what is buried.

Use the facts, because they are all there for a reason

Every fact in the prompt was put there by someone. Most of them trigger something. When a fact seems oddly specific, the delivery arrived on a Sunday, the buyer was seventeen, the letter was never sent, that specificity is the professor pointing at a doctrine.

A useful pass before you write: go through the prompt and mark every fact that seems chosen rather than incidental. Your issue list is mostly already there. Facts you never mention in your answer are usually issues you never spotted.

When you spot something you cannot resolve

Name it, argue both sides in two sentences, and move on.

Do not skip it. An issue raised and left genuinely uncertain collects most of what is available for it, because the rubric is asking whether you saw it and engaged with it. And do not stall on it either. The most expensive mistake on a timed exam is spending eleven minutes resolving something unresolvable while three untouched issues sit at the bottom of the page.

Real ambiguity is often deliberate. A question where the answer is clean tests less than one where it depends.

Practising against a real answer key

The hard part of practising issue spotters alone is that you cannot grade your own coverage. You already know which issues you saw, and the ones you missed are invisible to you by definition, which is exactly the information you need.

Gavel generates essay exams from your own notes, with the interrogatories weighted the way an exam weights them, and grades your answer against the answer key for that specific question rather than a general impression. What comes back is per-question: what the key expected, what you covered, and what you did not reach.

You can run it on the material you are actually being examined on.