Issue Log
Track problems that are real but not yet formal incidents or projects.
Purpose
This operating record makes issue log visible as repeated work rather than occasional memory. It should identify owner, cadence, evidence, and unresolved findings.
Operating record
| Cadence | Set a normal review interval and event-driven trigger. |
|---|---|
| Owner | Identify the role accountable for keeping issue log current. |
| Source data | List the systems, logs, reports, tickets, or records used during review. |
| Findings | Record exceptions, decisions, blockers, risk changes, and follow-up actions. |
| Evidence | Keep the smallest durable proof that the review occurred and produced a result. |
When to use
- When the work repeats often enough that memory is no longer reliable.
- When more than one person may request, perform, review, or inherit the work.
- When risk, approval, evidence, or handoff needs to be visible later.
Common failure modes
- Ownership is implied rather than named.
- Inputs are accepted before they are complete.
- The output is not easy to verify later.
Review guidance
Review this page after a material incident, after a role or system change, and on a normal cadence appropriate to its risk. During review, check whether the owner is still correct, whether inputs are still complete, whether the output is still useful, and whether related pages need updates.