Issue Log Template
A structured framework to capture, track, and resolve project issues before they derail your objectives.
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.
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Issue Log Template & Example. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use Issue Log Template & Example as a decision instrument rather than an administrative form. The subject terms—issue, example, template, tracking, worked—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Name the decision. Write the decision, approval, handover or control activity the completed template must support.
- Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
- Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
- Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
- Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Filling every box even when a field is not applicable instead of recording why.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Writing vague statements without an owner, measure, date or evidence source.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Copying a previous project without revalidating assumptions and stakeholders.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Using the document as a private worksheet when it is meant to support a shared decision.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Creating an approved baseline but failing to define who maintains it and when.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Is the purpose and intended decision clear to a reader outside the team?
- Are owners, dates, measures and sources complete and internally consistent?
- Which fields are assumptions and how will they be validated?
- What event, threshold or review date causes this document to change?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying Issue Log Template & Example?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about issue would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- Risk Management in Portfolios, Programs, and Projects: A Practice Guide — Project Management Institute. Used for risk practices across portfolios, programs and projects. Accessed 2026-08-13.
- ISO 31000 family — Risk management — International Organization for Standardization. Used for principles and guidance for enterprise risk management. Accessed 2026-08-13.