# Being Push: smallest complete software release

An original planning worksheet from Being Push. It does not claim measured customer outcomes.

| Decision | Record before estimation |
| --- | --- |
| Business change | One task that should become faster, safer or easier |
| Primary user | The person performing that task each day |
| Complete journey | Start event → actions → saved output → confirmation |
| Source of truth | Which system owns each record and editable field |
| Permissions | Who may view, change, approve and export |
| Exclusions | Features deliberately left for a later release |
| Acceptance | Observable checks with a named reviewer |

## Acceptance checklist

- [ ] A new user can complete the main task without developer intervention.
- [ ] Invalid inputs produce a helpful message and preserve entered data.
- [ ] Duplicate requests cannot create duplicate transactions.
- [ ] Unauthorised users cannot read or change protected records.
- [ ] Keyboard and narrow-screen workflows remain usable.
- [ ] An interrupted task has a recovery route.
- [ ] Data export and restore have been demonstrated.
- [ ] The client has access, run instructions and a support owner.

## Build-or-buy decision log

List the closest existing product, its missing requirement, the recurring cost of working around that gap, and the ongoing maintenance cost of a custom build. State assumptions and the next fact needed before choosing.