DailyWF / Workflows
Change Request Review
Review a proposed change before it affects production work.
How to use this workflow
Change Request Review is useful when repeated work needs a visible path from request to completion. Keep it compact: the value is in clarifying ownership, next action, and evidence, not in creating a large approval artifact.
- Describe the change, affected systems or people, reason, and expected benefit.
- Check risk, rollback, communication, timing, and dependencies before approval.
- Assign a single execution owner and a separate reviewer when risk justifies it.
- Execute during the agreed window and record actual results.
- Close only after validation, communication, and follow-up items are complete.
Expected output
A completed change request review record with trigger, owner, decision, next action, and evidence.
Common failure mode
Approving work without rollback, validation, or communication expectations.
Use notes
| Best trigger | Use when the work repeats, affects others, creates risk, or needs a defensible handoff. |
|---|---|
| Evidence | Keep the shortest record that proves the decision, action, owner, and result. |
| Review point | Review after incidents, repeated confusion, tool changes, ownership changes, or missed expectations. |
Related pages
- Access ReviewDefine how access is reviewed, changed, approved, and removed.
- Change ManagementDefine when changes require review, approval, notice, or rollback planning.
- Change Review ChecklistReview planned changes before execution.
- Change vs IncidentDistinguish planned change from unplanned service disruption.
- Incident NotificationDefine who must be notified when incidents affect service, data, obligations, or reputation.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.