Template
Separate severity from priority
Describe the damage before deciding the queue.
Before you use it
- Use when
- Bugs or incidents compete for limited remediation capacity.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
A template to use
Observed impact / severity: ___. Who or what is affected: ___. Workaround: ___. Exposure/frequency: ___. Deadline, dependency or business reason affecting priority: ___. Current priority and owner: ___.
Why it matters
Severity describes the observed impact of a defect. Priority records how urgently the organisation plans to address it, considering exposure, workarounds, dependencies and deadlines. Keeping them separate makes the scheduling decision visible without changing the impact record to justify it. Use the organisation’s definitions for each label.
An example
An export fails for a small group with a workaround. A contractual deadline can raise its priority without changing the observed failure.
Check your result
Does the record explain both the impact and the reason for its place in the queue?
Keep this limit in mind
- Priority can change with releases, regulation, customer exposure or available workaround; severity should not be rewritten merely to win scheduling. Follow the formal escalation policy for safety, security or regulatory incidents; this template does not set their urgency.
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Connected ideas
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaWrite a bug report someone can use
Evidence and sources (1)
This triage template records observed impact separately from the organisation’s scheduling priority.
Editorial design and source provenance only. No causal benefit, percentage improvement or validated intervention is claimed. Access: selected_source_sections; 2026-10-11. Registered first-party project text; template provenance, not an efficacy study.
Separate severity from priority — Brali source record · Selected template fields
All sources (1)
Edition and review
Version 0.1.0 · Published
Agent review: Agent editorial and scoped evidence review · 2026-10-11