keymodels
Program Issues Register
When and how should program issues register be applied?
Public preview
What this template contains.
Purpose. Use this register for conditions that already exist and require resolution at programme level. Application. Issues may originate within the programme, be escalated by components or arise externally. Unlike a risk, which concerns an uncertain future event or condition, an issue is current; both records may be linked when an anticipated risk occurs or an issue creates new uncertainty. Completion discipline. Create entries at the level defined by the template, use a stable identifier where one is available, l
Use context
Purpose, application, discipline.
Purpose
Use this register for conditions that already exist and require resolution at programme level.
Application
Issues may originate within the programme, be escalated by components or arise externally. Unlike a risk, which concerns an uncertain future event or condition, an issue is current; both records may be linked when an anticipated risk occurs or an issue creates new uncertainty.
Completion discipline
Create entries at the level defined by the template, use a stable identifier where one is available, link the supporting record and assign an owner, status and review point. Update entries without erasing decision history, and apply the access and retention rules appropriate to the information.
Field summary
Structured sections without protected files.
Issue
Issue identification number, PWBS number, Issue description, Identified by
Analysis and resolution
Root cause, Issue impact, Issue owner, Proposed resolution
Closure
Subsequent impacts, Date closed, Notes
Protected resources
Included resource formats.
Related models
