How to Write Strong Evaluation Justifications
Write short rationales that connect the criterion, the evidence and the consequence without repeating the whole response.
You'll learn
- Name the criterion and the specific behavior that meets or violates it.
- Explain why the difference affects task success.
- Match the strength of your claim to the evidence you inspected.
- A reviewer should be able to reconstruct your decision from your rationale.
In this guide
A justification is an audit trail for a decision. “A is clearer and more accurate” sounds like a judgment but leaves another reviewer unable to check it. Name what A preserves, what B changes and why that difference controls the score.
Build a rationale around the deciding evidence
Four moves
State the judgment
Use the task’s label or preference. Do not bury it beneath a summary of both answers.
Name the criterion
Specify correctness, source fidelity, completeness or the relevant rubric dimension.
Point to the evidence
Quote a short phrase or identify the precise claim, omission or action.
Explain the consequence
Say how the difference changes the answer’s usefulness, validity or compliance with the prompt.
Evaluate the explanation itself
Evaluation example
- X is better because it is more informative and professional.
- X is preferred for source fidelity. It preserves the beginner audience and advance-registration requirement. Y contradicts the registration rule and broadens the audience, which could lead readers to arrive without a valid booking.
Write enough to make the decision checkable
If one error decides the result, explain that error first. Add secondary differences only when they affect the preference, severity or a required dimension. A task that asks for separate correctness and style explanations needs both; a short overall rationale does not need a catalogue of every wording change.
| Weak wording | More useful wording |
|---|---|
| It hallucinates. | It says the trial measured accuracy, but the supplied methods list only completion time. |
| It ignores the prompt. | The prompt requests two items; the response supplies five. |
| It is more detailed. | It includes the required eligibility condition that the other answer omits. |
| I verified the answer. | I checked the stated deadline against the supplied notice; the remaining claims were outside this review. |
Be precise about uncertainty
If the evidence is insufficient, state what is missing and use the project’s rule for that case. “The source does not give a sample size” is stronger than “the sample size seems suspicious.” If you cannot run code, describe a static reasoning finding rather than claiming that a test failed.
When appealing a review, use the same structure. Identify the disputed criterion, the source passage and why the current label conflicts with them. A calm, reproducible explanation gives the reviewer something to resolve. Arguing that you usually perform well does not establish that this submission is correct.
Common mistake
Writing the rationale after forgetting the evidence
Keep permitted notes while reviewing, especially for long traces or documents. Reconstructing from memory encourages invented quotations, missing conditions and explanations that do not match the selected label.
Read it once as the next reviewer
- Can someone find the exact defect from my explanation?
- Does the consequence follow from the defect?
- Does the rationale support the label and severity I selected?
- Have I distinguished observation from inference?
- Have I removed generic praise and claims of checks I did not do?
Key takeaway
Short is useful when the evidence survives the edit. Brevity alone is not a quality measure.