Automation Readiness Checklist

Is the process documented anywhere — even roughly?

Doesn't need to be perfect. A notes doc or a voice memo counts.

Does the process happen the same way every time?

Automation needs consistency. If it depends on who's doing it, document the right way first.

Is there a clear start and end point?

We need to know what triggers the process and what 'done' looks like.

Are there known exceptions, and do you know how to handle them?

Edge cases don't have to be automated — but they have to be acknowledged.

Is the relevant data in a system (not just in someone's head or on paper)?

If the information isn't digital, we need a capture step before automation.

Is the data consistent? Same format, same field, every time?

Inconsistent data (mixed date formats, phone numbers with/without dashes) breaks automations.

Do you know where the data lives — and who has access?

We need to be able to read and write to the right place.

Does someone own the outcome of this process?

If no one is accountable, automation may improve the speed of a problem nobody's fixing.

Does your team know the process is being automated?

Surprise automations cause confusion. Loop in the people affected before we build.

Is there someone internal who can flag when something goes wrong?

Automation needs a human backstop. Define who gets the alert when it breaks.

Are the tools involved accessible via API or integration?

Some software is locked down. We'll check this — just flag anything unusual.

Are login credentials available for the relevant accounts?

We'll need admin-level access to connect systems.

Is there a test environment, or can we test safely in production?

We always prefer to test before going live. Know which option applies.