# Automation Readiness Checklist

Automate with Khushbu · Version 1.0 · Example learning material

Check the rules, data, access and exceptions before you build anything.

## Rules

- [ ] The decision rules are written down, not just "known" by one person
- [ ] Fixed rules are separated from steps that need human judgment
- [ ] You can state what a correct run looks like, start to finish

## Data

- [ ] The input arrives in a predictable place and format
- [ ] Required fields are defined, and missing fields have a path
- [ ] Duplicate input is detected or prevented
- [ ] Sensitive data is identified and access to it is limited

## Access

- [ ] Approved accounts and roles exist for every system touched
- [ ] Credentials live in a secret store, not inside the workflow
- [ ] The automation uses the least access it needs to do the job
- [ ] A named person owns the credentials and can rotate them

## Exceptions

- [ ] There is a path when data is missing, invalid or duplicated
- [ ] Failures are visible and routed to a named owner
- [ ] A manual fallback exists if the automation is paused
- [ ] Retry and escalation behaviour is defined

## Human checkpoints

- [ ] Approval points are explicit before any consequential action
- [ ] External messages or payments need a human where it matters
- [ ] The team knows how to pause, resume and check the workflow

## Worked example / note

Fictional check: An approval workflow may create a record automatically, but must not send an external email until a named approver confirms. A missing approver routes the item to a review queue instead of guessing.

## Usage

Adapt for personal or internal team use. Examples are fictional and are not verified client or learner results. This checklist is not a security certification, a compliance audit or a guaranteed outcome.