Free workflow resource

Is your workflow ready for automation?

Start with one process your team repeats. Answer eight practical questions to see what you already know, what needs attention and what to bring to a useful first conversation.

No email required. Your answers stay on this page.

One workflow. Eight starting points.

Choose “Unsure” wherever you need input from someone else. Every gap becomes an action in your brief. This is a preparation tool; deciding whether to automate still needs evidence from the real work.

.readiness-interactive { display: none; }Use the downloadable checklist below to record your answers. Interactive next steps are available with JavaScript enabled.

Can you describe one repeatable workflow?

Name its trigger, the steps people take and what counts as finished. Map one recent case from arrival to completion. Mark every handoff and decision.

Do you know the current workload and effort?

Record how often work arrives, hands-on time, waiting time and corrections. Track representative cases. Separate time spent working from time spent waiting, and note rework.

Do you have representative inputs and expected outputs?

Include ordinary, incomplete and difficult cases you are permitted to use. Gather approved examples of inputs and checked outputs, including exceptions. Remove sensitive details where possible.

Are the rules and exceptions clear?

Identify decisions that follow fixed rules and those that require someone’s judgment. Ask an experienced operator to explain ambiguous cases. Document when the system should stop and ask for help.

Can you identify the systems and data owners?

Know where the correct records live and who can approve access or changes. List the systems involved, the source of truth for each field and the person who owns access. Verify export or integration options.

Is someone responsible for review and approval?

Name who checks outputs, approves consequential actions and handles failures. Assign a reviewer and an exception owner. Define what can proceed automatically and what needs approval.

Have you defined what a useful pilot must prove?

Set a baseline, a target and acceptable error limits for the same workflow. Choose measurable acceptance criteria with the people doing the work. Include corrections and review effort, not just speed.

Is there an owner for the system after launch?

Account for support, access, running costs, maintenance and a manual fallback. Name the operating owner and agree how issues, ongoing costs and changes will be handled after handover.

Download the blank checklist (.txt)

Continue with the work

Stay with the operating question. The technology can wait until the work is clear.

Is your workflow ready for automation?

One workflow. Eight starting points.

Can you describe one repeatable workflow?

Do you know the current workload and effort?

Do you have representative inputs and expected outputs?

Are the rules and exceptions clear?

Can you identify the systems and data owners?

Is someone responsible for review and approval?

Have you defined what a useful pilot must prove?

Is there an owner for the system after launch?

See a real RFQ workflow

Understand a systems audit

Explore AI automation

Is your workflow ready for automation?

One workflow. Eight starting points.

Can you describe one repeatable workflow?

Do you know the current workload and effort?

Do you have representative inputs and expected outputs?

Are the rules and exceptions clear?

Can you identify the systems and data owners?

Is someone responsible for review and approval?

Have you defined what a useful pilot must prove?

Is there an owner for the system after launch?

Choose the next useful path.

See a real RFQ workflow

Understand a systems audit

Explore AI automation