In this resource
§1 Purpose and Principles
An issue log transitions a project from reactive scrambling to proactive resolution.
While a risk register captures potential future events, an issue log acts as the central repository for problems that are occurring right now. It ensures that every obstacle—whether it's a technical constraint, a resource shortfall, or a stakeholder misalignment—is formally captured, assigned an owner, and tracked through to resolution.
KEVOS® Principle: Never leave a project meeting with an "understood" problem. If it threatens scope, schedule, cost, or quality, it must be assigned an ID and formally entered into the log. Unlogged issues are unmanaged issues.
§2 The Template Data Structure
A highly effective issue log requires exactly ten distinct data fields. Omitting any of these breaks the chain of accountability.
| Field Name | Description and Usage |
|---|---|
| ID | A unique identifier (e.g., 1-001) used for traceability in status reports and change requests. |
| Type | Categorisation of the issue (e.g., Resource, Technical, Stakeholder, Scope, Quality, Process, External). |
| Description | A clear, objective statement of what is occurring. |
| Priority | High, Medium, or Low urgency based on the proximity of the impact. |
| Impact on Objectives | Specific detailing of how the issue affects Schedule, Cost, Scope, or Quality. |
| Owner | The single individual accountable for driving the resolution (not necessarily the person fixing it). |
| Status | Current state of the issue (Open, In Progress, Resolved, Escalated). |
| Res. Date | The actual date the issue was fully closed or resolved. |
| Resolution | The concrete action taken to close the issue. |
| Comments | Contextual notes, secondary impacts, or lessons flagged for the project retrospect. |
§3 Worked Example (Mary's Consulting)
Reviewing how a live project organises its active and resolved challenges.
The following example is synthesised from a real-world web delivery project. Notice how the descriptions are objective, impacts are tied directly to project baselines, and ownership is restricted to a single name per issue.
| ID | Type | Description | Pri. | Impact | Owner | Status | Res. Date | Resolution / Action |
|---|---|---|---|---|---|---|---|---|
| 1-001 | Resource | Bill (UX) had unexpected medical leave Aug 10-14. Brand-design work delayed. | High | Schedule (1-week slip risk) | Andrew | Resolved | Aug 17, 2026 | Bill returned with overlapping work re-prioritised; no net schedule slip. Backup designer briefed. |
| 1-002 | Technical | Approved CMS provider's enterprise tier no longer offers 5-seat licensing, only 10-seat. | Medium | Cost (+$1,000) | Bob | Resolved | Aug 22, 2026 | Negotiated 5-seat legacy pricing for first year; 10-seat from year 2. Flagged for budgeting. |
| 1-003 | Stakeholder | Marketing Lead requested earlier visibility into design mockups. | Low | Engagement | Bill | Resolved | Aug 5, 2026 | Bill added Marketing Lead to weekly design review meetings. |
| 1-005 | Quality | Initial accessibility lint detected colour-contrast issues on 3 components. | High | Quality (WCAG) | Bill | Resolved | Sep 4, 2026 | Bill updated brand colours; sponsor re-approved. Linter added to CI pipeline. |
| 1-006 | Technical | CRM API does not expose 'industry vertical' field needed for lead routing. | High | Schedule; Quality | Bob | In Progress | — | Working with vendor. Fallback: collect vertical via form, store in CRM 'notes' at launch. |
| 1-007 | Resource | Consultant bio submission rate at 38% vs. 60% target by Sep 12. | Medium | Scope (smaller directory) | Christine | In Progress | — | Mary issued firm-wide reminder; tiered launch plan in place (top 50 at launch). |
| 1-008 | External | Hosting vendor reported planned maintenance window Nov 22 (2 days pre Go-Live). | High | Schedule (Go-Live risk) | Bob | Escalated | — | Escalated to vendor account team requesting deferral or guaranteed exit criteria. |
| 1-010 | Scope | Sponsor requesting new Press / Media section for launch. | High | Scope, Cost, Schedule | Andrew | Open | — | Change request CR-007 drafted; impact analysis complete; awaiting CCB disposition. |
§4 Status Definitions
To prevent confusion across project teams, apply these strict definitions to the "Status" column.
Open
The issue has just been logged. The owner has been assigned but active work to resolve the impediment has not yet begun, or a strategy is still being formed.
In Progress
The owner is actively executing the resolution strategy. The team is aware of the workaround or the steps being taken to mitigate the impact.
Escalated
The project team cannot resolve the issue with current resources or authority. It has been raised to the sponsor, steering committee, or an external party.
Resolved
The fix has been implemented, validated, and the impact neutralized. The issue is closed and logged for retrospective review.