Risk & Change
Issue Tracking
MyPMP
QMS Template
| Ref | Issue | Priority | Owner | Status |
|---|---|---|---|---|
βοΈ
Free to try β your work auto-saves in this browser.
Saving to the cloud (sync across devices) is a paid feature. Unlock Issue Tracking for $1/mo, or get everything with membership ($9/mo or $99/yr).
β οΈ Risk & Change
Auto-saved in your browser Β· β members can white-label & sync across devices
About the Issue Tracking template
An Issue Tracking log is a live register of problems, blockers, and unresolved questions that are already affecting a project, capturing each issue from the moment it's raised through to resolution. Unlike a risk register, which deals with potential future events, an issue log records events that have happened and need active management. Keeping it current gives the project manager a single source of truth for what's slowing delivery and who owns the fix.
It's part of My QMS, MyPMP's Quality Management System: fill it in online, personalize it with your name and logo, then export a clean, branded PDF. Your work auto-saves in your browser.
When to use a Issue Tracking
- βΈA risk has materialised and now needs corrective action rather than monitoring
- βΈA team member or stakeholder flags a defect, dependency slip, or resource conflict
- βΈDuring status meetings to review open items, ageing, and overdue actions
- βΈWhen a decision or clarification is blocking a task and needs escalation
What a good Issue Tracking includes
- βUnique issue ID and short descriptive title
- βDate raised, raised by, and category (technical, resource, scope, dependency)
- βPriority or severity rating and current status (open, in progress, resolved, closed)
- βAssigned owner and target resolution date
- βDescription, impact on schedule/cost/quality, and agreed action or workaround
- βResolution notes and date closed for audit trail
What's inside this template
The interactive form above gives you:
A table of Ref, Issue, Priority, Owner, StatusNotes
Tips & common mistakes
- π‘Assign a single named owner to every issue; shared ownership means no ownership
- π‘Set and review a target date, and track ageing so stale issues get escalated rather than forgotten
- π‘Distinguish issues from risks and actions so the log stays focused and doesn't become a catch-all task list
How it works
- 1. Fill it in β type directly into the fields, tables and sections above.
- 2. Brand it β add your organization name and logo with the Branding button.
- 3. Export β print to PDF, or become a member to white-label and sync across devices.
FAQ
What's the difference between an issue log and a risk register?οΌ
A risk register tracks uncertain events that might happen in the future, while an issue log records problems that have already occurred and need resolution now. A risk becomes an issue once it materialises.
Who is responsible for maintaining the issue log?οΌ
The project manager owns the log overall, but each individual issue should be assigned to a named owner accountable for driving it to resolution.
How should issues be prioritised?οΌ
Rate each issue by severity and impact on schedule, cost, or quality, then combine that with urgency to decide order of attention; high-impact, time-sensitive issues warrant escalation.
Make it yours β $9/mo or $99/yr
Membership unlocks white-label export (remove the MyPMP footer), cloud sync across devices, plus all apps & ScheduleX.
See membership