Skip to content

Is this workflow ready for automation?

A working brief for an operations lead, technical owner and decision-maker to complete together. Use it to surface the evidence needed for the next step.

Start the brief
Readiness brief
Download the working brief

Describe a specific workflow and expose its unanswered questions. This is a planning aid, not a certification, audit or automatic readiness score.

A brief for the next decision

The work

Scope and accountable owner

The starting point

Baseline, method and known gaps

The information

Sources, permission and access owner

The dependencies

Connections and responsible teams

The review

Decision point, exceptions and test cases

The investment decision

A first stage and evidence to continue

Keep the status explicit

Known and evidenced

Needs investigation

Owner to confirm

Six areas to establish together. This is a planning canvas, not a score, certification or automated assessment.

Define the work

A one-sentence scope and a named owner.

Name the trigger, the result and the person accountable. Keep the scope narrow enough that the beginning and end are recognisable.

  • What starts the workflow?
  • What does a complete result contain?
  • Who owns the outcome?

Establish the starting point

A baseline with its measurement method and known gaps.

Observe a representative sample. Separate active work, waiting and correction. Record the period and how the observations were gathered.

  • How often does the task occur?
  • Where is time spent?
  • What does an exception look like?

Understand the information

A source list, access owner and unresolved information questions.

Identify the source records, permission to use them, their quality and any restrictions on the tools that may process them. Resolve access questions with the organisation's responsible owner.

  • Which information is necessary?
  • Is it complete and available in a usable form?
  • Who can approve its use and access?

Map the dependencies

A dependency map with an owner for each connection.

List the systems, teams and suppliers the workflow depends on. Include the connection you would need and who can confirm that it is available.

  • Which systems need to exchange information?
  • Who controls each integration?
  • What happens if a dependency is unavailable?

Design the review

A review point, an exception route and representative test examples.

Decide what the software can prepare or execute and which actions require a person to decide. Give exceptions an owner and define the context they need.

  • Where is judgement required?
  • Who can amend, reject or approve the output?
  • How will mistakes and exceptions be found?

Decide what would justify investment

A proposed first stage and an explicit decision point.

Set an observable success measure and the costs to investigate. Include operating effort and review time. Agree the evidence needed before moving beyond a first stage.

  • What improvement matters to the organisation?
  • What will implementation and continued operation require?
  • What result would cause you to expand, change or stop?

Your starting point

What do you already know?

Use this list to collect the decisions you can support with evidence. It provides a discussion agenda, rather than a readiness score.

Select the areas you have already worked through.