# Repetitive task inventory

Use this worksheet for five working days. Record the work as it happens instead of reconstructing the week from memory. Do not include secrets, personal data, customer confidential data, or regulated information.

## Task log

| Date | Task or queue | Trigger | Person or role | Active minutes | Waiting created | Correction or repeat? | Systems touched | Outcome |
| --- | --- | --- | --- | ---: | --- | --- | --- | --- |
|  |  |  |  |  |  |  |  |  |

## Candidate summary

Complete one summary for each repeated task.

- Task name:
- Accountable owner:
- What creates one item?
- What observable result finishes it?
- Runs per week:
- Total active minutes per run across all people:
- Typical elapsed time:
- Who waits while it is open?
- What drives future volume?
- Share of cases following the normal path:
- Three common exceptions and their current owners:
- Source of truth for required inputs:
- How quickly can a correct result be verified?
- What external action occurs?
- What is the impact, detectability, scope, and reversibility of a wrong action?
- Is there a usable manual fallback?
- Who would own monitoring, failed runs, changes, and retirement?

## Candidate score

Score each item from 0 to 2. A score is a discussion aid, not an approval to automate.

| Factor | 0 | 1 | 2 | Score |
| --- | --- | --- | --- | ---: |
| Frequency | Monthly or rarer | Weekly | Daily or scales with volume |  |
| Stability | Sequence changes each run | Normal path repeats | Normal path and main exceptions repeat |  |
| Inputs | Hunted from memory | Some named sources | Required sources and owners are clear |  |
| Checkability | Subjective or delayed | Human can review | Outcome and effects can be verified |  |
| Coordination | One person, no wait | One handoff | Several people or systems wait |  |
| Containment | Immediate hard-to-reverse harm | Gate can contain effect | Draft, internal, or reversible effect |  |
| Ownership | No owner | Process owner only | Service and decision owners named |  |

## Decision

- Keep manual and document:
- Simplify or batch first:
- Assist with preparation or drafting:
- Automate a bounded path:
- Evidence needed before deciding:
- Review date:

Measure real clean completion, corrections, exceptions, harmful effects, detection, recovery, and owner effort after any pilot. Do not report projected hours as realized savings.
