PLAINREADS — ISSUE LOG
Source: https://plainreads.com/blog/issue-log-template

REUSABLE ISSUE RECORD
ID and date reported:
Observed problem and affected context:
Impact on current commitment or user task:
Priority and reason:
Resolution coordinator:
Next action and action owner:
Due or review point:
Status:
Workaround:
Permanent resolution:
Closure check and verifier:
Decision/escalation needed:
Resolution evidence and closure date:

FICTIONAL EXAMPLE — I-07
Problem: Welcome-message expense link points to old document location.
New starter sees access error; existing operations user can open it.
Impact: New starter cannot find approved instructions; publication incomplete.
Priority: Resolve before next welcome message.
Coordinator: Morgan.
Next action: Lee confirms approved location and intended audience access.
Workaround: Morgan supplies approved instructions via authorized channel.
Permanent fix: Update welcome link once location/access is confirmed.
Review: Before next welcome message; Casey decides hold or approved alternative
if access is still unresolved.
Closure: New-starter-equivalent account opens replacement link and locates
submission instructions. Morgan records result; Casey confirms acceptance.

REVIEW
- What changed?
- What is blocked, by whom or what?
- What is the next observable action?
- When is a new decision required?
- Who can make that decision?

CLOSURE
- Verify under the conditions in which the failure occurred.
- Distinguish workaround, permanent fix, and accepted limitation.
- Record action, evidence, acceptance, and date.
- Preserve history and follow applicable retention rules.
- Feed recurring causes into a lessons-learned review.