Rank process improvement opportunities by impact, frequency, effort and operational risk before choosing what to automate first.
Working record
| Check | What to do | Evidence to retain |
|---|---|---|
| Process | Trace the work from its starting event to the usable output. Mark repeated entry, waiting and approvals separately. | Current process map with evidence for the slow or unreliable step. |
| Frequency | Count how often the task occurs during a defined period. Distinguish a typical workload from a peak. | The frequency record, its source and the person responsible for resolving missing evidence. |
| Impact | Describe the consequence of the risk for cost, time, users or operation. State the basis of any estimate. | The impact record, its source and the person responsible for resolving missing evidence. |
| Effort | Estimate implementation and ongoing operating work separately. State the assumptions behind the estimate. | The effort record, its source and the person responsible for resolving missing evidence. |
| Risk | Describe a specific failure, its consequence and the action that reduces it. Name the person who monitors the condition. | Risk condition, impact, mitigation and owner. |
Review the decision
Rank process improvement opportunities by impact, frequency, effort and operational risk before choosing what to automate first. Keep process, frequency, impact attached to the conclusion so the next owner can challenge the assumptions. Resolve missing evidence before treating this record as approval.
Continue the decision
How to Audit Marketing Data Before You Automate the Workflow · How to Scope a Website Project Before You Quote It.
Keep the displayed formula, input units and model scope with the result. Corrections or questions can be sent through the request section on this page.
Content updated: October 11, 2026