Issue Log Template & Example
A handbook-style issue log template & example with field guidance, workflow, review checks and source-derived example evidence.
What this artefact controls
Issue Log Template & Example should be treated as a decision instrument, not as paperwork completed for its own sake. Its practical value comes from making the underlying decision, evidence, ownership and review cycle visible. In this handbook, the supplied source structure is retained as the factual basis while the surrounding guidance explains how to complete, review and maintain it in day-to-day project delivery.
The source set repeatedly links project documents to broader control relationships: scope creates the work to be scheduled and costed; resources execute that work; stakeholders influence acceptance and change; risk captures uncertainty; quality establishes evidence of conformance; and performance information explains whether the project is still moving toward its intended outcome. Issue Log Template & Example belongs in that integrated system. It should therefore use identifiers and terminology consistent with adjacent project records so that a reviewer can trace a decision across documents without relying on memory.
Before filling any field, write one sentence describing the decision or control action the completed artefact must support. Then identify the accountable owner, contributors, reviewers, approval authority and next review trigger. This prevents a common failure in project documentation: every box is filled, but nobody can explain what decision the document enables or who must act when conditions change.
How the information fits together
This visual is an HTML/CSS interpretation for the KEVOS article reader. It conveys the decision structure without embedding the supplied source artwork as a screenshot.
Complete the template with traceable information
The following field map is extracted from the supplied blank or completed source document where text was available. Wording has been normalised for web readability, but the source structure remains the basis. Where a field is not applicable, record why rather than silently leaving a potentially important control blank.
| Source field / section | What to record | Review test |
|---|---|---|
| ISSUE LOG | Record the minimum evidence needed for issue log to support the provide a navigable reference model that helps practitioners connect concepts, processes, domains, outputs and delivery approaches without turning guidance into a rigid recipe. | The entry is specific, traceable and reviewable. |
| ID | Assign a unique, stable identifier that can be referenced from reports, changes, risks, requirements or evidence. | The entry is specific, traceable and reviewable. |
| Type | Record the minimum evidence needed for type to support the provide a navigable reference model that helps practitioners connect concepts, processes, domains, outputs and delivery approaches without turning guidance into a rigid recipe. | The entry is specific, traceable and reviewable. |
| Description | Write an observable, specific statement that a reviewer outside the drafting team can understand without verbal explanation. | The entry is specific, traceable and reviewable. |
| Pri. | Record the minimum evidence needed for pri. to support the provide a navigable reference model that helps practitioners connect concepts, processes, domains, outputs and delivery approaches without turning guidance into a rigid recipe. | The entry is specific, traceable and reviewable. |
| Impact on Objectives | Write an observable, specific statement that a reviewer outside the drafting team can understand without verbal explanation. | Scale and calculation method are defined. |
| Owner | Name one role or person who has the authority and practical responsibility to drive the item to its next state. | A named owner can act without ambiguity. |
| Status | Use a small defined status set and apply it consistently; status should reflect current reality, not desired progress. | Status matches evidence and next action. |
| Res. Date | Use an unambiguous date and make clear whether it is the preparation, approval, review or event date. | Date meaning and calendar are unambiguous. |
| Resolution | Record the minimum evidence needed for resolution to support the provide a navigable reference model that helps practitioners connect concepts, processes, domains, outputs and delivery approaches without turning guidance into a rigid recipe. | The entry is specific, traceable and reviewable. |
| Comments | Record the minimum evidence needed for comments to support the provide a navigable reference model that helps practitioners connect concepts, processes, domains, outputs and delivery approaches without turning guidance into a rigid recipe. | The entry is specific, traceable and reviewable. |
Blank web-ready structure
This compact version is designed for copying into a project working note or for translating into your organisation’s controlled form. It is not a claim that these are the only fields required by every organisation, contract or jurisdiction.
What the uploaded example demonstrates
The source set uses a recurring worked project — Mary’s Consulting and its new company website — to show how project artefacts connect. The examples are useful because the same scope, team, costs, risks, stakeholders and milestones recur across multiple forms, allowing the reader to see how one project decision propagates through the documentation system. Any numerical value below is a source example or a calculation explicitly identified as such; it should not be treated as a universal project standard.
- Status legend: Open (just logged) · In Progress (actively being worked) · Resolved (closed with fix) · Escalated (raised to sponsor / external party for resolution)
- Mary's Consulting – New Company Website Sep 14,
- I-001 Resource Bill (UX) had unexpected High Schedule (1-week slip Andrew (PM) Resolved Aug 17, Bill returned with overlapping work Cross-training added to
- medical leave Aug 10–14. risk) 2026 re-prioritized; no net schedule slip. Backup action items.
- I-002 Technical Approved CMS provider's Mediu Cost (+$1,000) Bob (Dev) Resolved Aug 22, Negotiated 5-seat legacy pricing for first Year-2 cost flagged for
- I-003 Stakeholder Marketing Lead requested Low Stakeholder engagement Bill (UX) Resolved Aug 5, 2026 Bill added Marketing Lead to weekly Improved alignment
- I-004 Scope Sales Lead asked whether the Low Scope (small) Andrew (PM) Resolved Aug 28, Added to Phase 2 backlog, not in scope for Documented in
- I-005 Quality Initial accessibility lint detected High Quality (WCAG Bill (UX) Resolved Sep 4, 2026 Bill updated brand colors; sponsor Linter now in CI to
Step-by-step workflow
For controlled project records, the final step is not “save the file”. The final step is to make the current approved state discoverable, communicate the decision to affected people and define the next review trigger. That trigger may be a phase gate, threshold breach, approved change, new stakeholder, supplier event, forecast movement, risk trigger or a scheduled review date.
Review checklist before approval or use
- The reference distinguishes historical process models from current principles and domains.
- Illustrative process maps are not described as mandatory sequencing.
- Edition and source context are explicit.
- Links between governance, scope, schedule, finance, stakeholders, resources and risk are visible.
- The page helps users find the right template or decision artefact.
- Current PMI facts are separated from the supplied training material.
Run the review from the perspective of a competent person who did not attend the drafting meeting. If they cannot reconstruct the basis, current state and required next action from the record and its cited evidence, the artefact is not yet controlled enough for a material decision.
Common mistakes and recovery actions
Memorising a chart without understanding the decision it supports.
Recovery: return to the approved objective or baseline, identify the missing evidence or decision owner, and record the corrective action before proceeding.
Treating one delivery approach as universally correct.
Recovery: return to the approved objective or baseline, identify the missing evidence or decision owner, and record the corrective action before proceeding.
Combining editions without stating the differences.
Recovery: return to the approved objective or baseline, identify the missing evidence or decision owner, and record the corrective action before proceeding.
Using an exam-preparation heuristic as a contractual requirement.
Recovery: return to the approved objective or baseline, identify the missing evidence or decision owner, and record the corrective action before proceeding.
Confusing process names with organisational job titles.
Recovery: return to the approved objective or baseline, identify the missing evidence or decision owner, and record the corrective action before proceeding.
Keep the document alive after first approval
A project artefact is only useful while its status is known. Give it a unique identifier, version, owner, approval state and effective date. Define what types of change require reapproval and what updates can be made administratively. Retain superseded versions when the record is needed to explain a historical decision, claim, audit, acceptance or lesson.
Use the document in reviews by focusing on exceptions and decisions rather than reading every field aloud. Ask what has changed since the last review, what assumption has been invalidated, what threshold has been crossed, which decision is now due and which action remains without an owner. This converts the artefact from static documentation into a control mechanism.
At hand-off, confirm that downstream users can interpret the identifiers, units, assumptions and status values without relying on the original author. For project close-out, make sure unresolved items have an operational owner and a clear retention location. A closed project should not leave behind orphaned risks, undocumented support obligations, unverified benefits or ambiguous acceptance evidence.
Source basis and limitations
This page is an original KEVOS handbook synthesis grounded in the uploaded source files. It intentionally paraphrases and restructures the material for practical application rather than reproducing the source documents as images. Where the source contains an illustrative project value, that value remains an example. Where a required blank source was absent, the limitation is stated explicitly rather than silently inventing a missing form.
- PMBOK+8+Plans+and+Documents/Manage Project Execution/Issue_Log_BLANK.pdf
- PMBOK+8+Plans+and+Documents/Manage Project Execution/Issue_Log_FILLED.pdf
Current authoritative context used for the reference pages: Project Management Institute, PMBOK® Guide — Eighth Edition and the 2026 PMP Examination Content Outline. The article package does not reproduce substantial PMI publication text.