VanillaPM
Sign in Get started free Dashboard
Free template

Issue log template

A free issue log template in Excel and CSV — issue, type, priority, owner, due date, status, an automatic overdue flag and days open, what it blocks, actions, escalation and resolution.

Download Excel (.xlsx) Download CSV Free · no sign-up · opens in Word, Excel, Google Docs/Sheets and LibreOffice

What's inside

ColumnWhat goes in it
IDISS-001, ISS-002 …
IssueWhat is happening now, and its effect
Typedrop-down Technical, Resource, Supplier, Stakeholder, Quality, Schedule, Cost
Prioritydrop-down Critical, High, Medium, Low
Raised by
Date raised
OwnerOne person who will resolve it
Due date
Statusdrop-down Open, In progress, Escalated, Resolved, Closed
Overdue?Past the due date and not resolved · calculated
Days opencalculated
Blocks (task or deliverable)
Actions taken
Escalated to
ResolutionWhat fixed it; fill in before closing

The Excel file has three sheets: the blank register, a filled example from the Coral Ridge Resort sample project, and how to use each column. The CSV is the blank header row only.

What an issue log is

An issue is a problem that is happening now; a risk is one that might. The issue log lists the current problems, who owns each one, when it must be fixed, and what has been done about it, so nothing is left waiting for someone else.

When to use it

Every day of delivery. Review open issues at each team meeting and escalate the ones that are past their due date or beyond the team's authority.

How to fill it in

  1. Describe the issue and its effect in one sentence.
  2. Set the priority and give it one owner with a due date.
  3. Record what it blocks: the task or deliverable that can't move until it is fixed.
  4. Log the actions as they happen. The Overdue? and Days open columns update themselves.
  5. Escalate when it is beyond the owner's authority, and record who to.
  6. Write the resolution before closing: what fixed it. That is where lessons come from.

Common mistakes

  • Risks and issues in the same list. Keep threats that might happen in the risk register.
  • Issues owned by "the team", so nobody owns them.
  • Closed with no resolution recorded.

See it used on a real project: B4 · Remove impediments and manage issues