How to choose the first workflow to automate

Why the first choice matters

One owned workflow establishes a reusable pattern: a named owner, clear permissions, test cases and honest measurement. Your team can review a concrete output and improve the handoffs before connecting more of the business. Document inputs, decisions and handoffs before building, including the parts that currently depend on someone’s memory.

Six criteria for a strong first workflow

Compare candidate tasks against these criteria. Choose the task with a clear operating pattern and a way to judge whether the change helps.

1. It repeats often. Daily or weekly work supplies enough ordinary cases to test and measure.
2. It follows a predictable pattern. Identify the usual inputs, steps and output, plus the exceptions that need review.
3. It has a source of truth. Define the inbox, document, form or system of record the workflow uses.
4. It has a clear owner. Name the person who knows what correct looks like, reviews exceptions and accepts the launch.
5. It has a measurable baseline. Record volume, time per item and correction rates before the build.
6. It has clear approval points. Agree the permissions for routine steps and the named people responsible for consequential decisions.

Routine steps and consequential decisions

Routine work runs within agreed permissions; named checkpoints cover consequential decisions. Extraction, routing, drafting and preapproved, bounded routine messages can run automatically within those limits. Money movement, legal commitments, irreversible actions or activity outside the agreed limits require the appropriate approval. Uncertainty and defined exceptions go to the responsible person for review.

A measurement checklist to run before and after

Capture a baseline, then measure the same workflow and a comparable volume after a defined trial period. Include the review and exception work that remains.

• Volume: how many items arrive each week.
• Time per item: from receipt to a review-ready result.
• Correction rate: how often a person needs to fix the output.
• End-to-end time: from first input through the required approval.
• Exception rate: how often the workflow needs human review.
• Team confidence: whether the owner can explain the workflow and handle an uncertain result.

Worked example: supplier-invoice intake and purchase-order matching

A services business receives supplier invoices by email and re-keys the same figures into its accounting system. In this worked example, the inputs are the supplier email, attached invoice, related purchase order and agreed accounting fields.

The agent extracts the supplier, line items, quantities and prices, checks them against the purchase order, and prepares a draft accounting entry or review-ready record. It flags missing details, mismatches and uncertain readings for the named person.

The routine intake, extraction and matching run within agreed permissions. The responsible person reviews the draft at the posting checkpoint; matching alone does not authorize posting or payment. This removes repeated copying while retaining the required judgement and approval.

Frequently asked questions