# Being Push: first automation scope worksheet

Prepared by Being Push as a planning template, not a report of client results.

## 1. Record the baseline

| Question | Your answer |
| --- | --- |
| Which event starts the process? | |
| How often does it run each week? | |
| Typical manual minutes per run? | |
| Errors per week, and how measured? | |
| Who owns exceptions today? | |

Estimated manual hours/week = runs/week × minutes/run ÷ 60.
Record the observation dates and sample size. Separate an estimate from a measured baseline.

## 2. Decide what can run automatically

| Step | Input/source | Rule or judgement? | Approval owner | Recovery action |
| --- | --- | --- | --- | --- |
| | | | | |

An incomplete record, ambiguous match or consequential decision must have a named review route.

## 3. Release checklist

- [ ] Test a missing input, duplicate event and unavailable API.
- [ ] Confirm the same event cannot trigger the action twice.
- [ ] Record tool permissions and data retention.
- [ ] Show the reviewer the evidence behind a recommendation.
- [ ] Assign an owner and notification for failures.
- [ ] Agree rollback and manual fallback.
- [ ] Set the observation period and review date.

## 4. Review after release

Compare handling time, exceptions and errors with the baseline using the same definition and sample method. Record a result only after observation; until then label it a success measure.