Change Request Log
How can change request log support strategic choice or positioning?
Public preview
What this template contains.
Purpose. Use this log as the programme's authoritative index of change requests from submission through decision, implementation and closure. Application. Component changes should enter the programme log when they affect shared benefits, strategy, resources, dependencies or controlled programme content. A request remains open until it is rejected, withdrawn or fully implemented and verified. 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 log as the programme's authoritative index of change requests from submission through decision, implementation and closure.
Application
Component changes should enter the programme log when they affect shared benefits, strategy, resources, dependencies or controlled programme content. A request remains open until it is rejected, withdrawn or fully implemented and verified.
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.
Request
Change identification number, PWBS number, Change description, Requested by
Analysis
Priority/severity, Change impact, Cost, Level of effort
Decision and closure
Proposed resolution, Decision, Decision maker and actual resolution, Decision date
Protected resources
Included resource formats.
Related models