DailyWF / Reference
Change vs Incident
Distinguish planned change from unplanned service disruption.
Plain-language explanation
Change vs Incident is a practical concept page. Use it to align language before writing a workflow, policy, or review record.
How to apply it
- Keep definitions operational rather than academic.
- Tie the term to decisions people actually make.
- Use examples and counterexamples when confusion is likely.
Expected output
A plain-language reference note that helps users choose the right workflow, policy, or template.
Common failure mode
Approving work without rollback, validation, or communication expectations.
Use notes
| Use with | Link this note from workflows and policies where the term affects decisions. |
|---|---|
| Avoid | Do not turn definitions into rules unless a policy page owns the requirement. |
| Review point | Revise when repeated questions show the explanation is still ambiguous. |
Related pages
- Incident NotificationDefine who must be notified when incidents affect service, data, obligations, or reputation.
- Access ReviewDefine how access is reviewed, changed, approved, and removed.
- Change ManagementDefine when changes require review, approval, notice, or rollback planning.
- Change Request ReviewReview a proposed change before it affects production work.
- Change Review ChecklistReview planned changes before execution.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.