28 January 2026 · 5 min read
Reviewer fatigue shows up in exception notes first
Before a backlog becomes a missed deadline, it becomes soft language. “Further information required.” “Awaiting clarity.” “Does not appear sufficient.” Those phrases postpone judgement while keeping the ticket green.
Count soft closes
Pick a fortnight of exceptions and mark which ones name a missing artefact versus which ones express unease. A rising soft-close rate usually means the queue is too wide for the hours available — not that reviewers forgot how to write.
Shrink the front door
Fatigue fixes rarely start with writing workshops. They start with intake: fewer duplicate requests, clearer ownership, and sampling that does not pretend every control needs the same depth. Module 2 of our workshop spends more time on status language than on prose style for this reason.
Protect a challenge hour
Some UK teams schedule a short daily window where reviewers only write challenge questions — no new intake, no pack export. It sounds artificial. It also stops challenge work from being squeezed into the last twenty minutes of a shift.
If notes stay vague after you shrink the queue, then invest in narrative practice. Until then, treat soft closes as a capacity signal.