TEAM WORKFLOW AUDIT · TEAMS OF EIGHT OR MORE

See the whole route of one workflow before automating any of it.

$1,500 USD. Twelve months of up to five inboxes, the map, credited if we build.

Paid upfront · Credited if we build

One person sees a task. The team reveals the workflow.

Personal AI use helps with a task. It cannot show where work starts, who touches it, what waits, or what counts as done.

FIVE QUESTIONS NOBODY CAN ANSWER YET

RequestWhere does it start, and how many arrive in a week?OwnerWho picks it up, and who assumed someone else had?HandoffHow long does it sit between two desks?DecisionWho is allowed to decide, and what happens when they are out?CompletionWhat counts as done, and who agrees it is?

Answer all five for one workflow and the automation decision makes itself. Guess, and you automate the wrong step. The coral-marked step stays with a person either way.Haven’t audited one inbox yet? Start there, free — it comes first.

WHAT GETS MEASURED

Measure the work before changing it.

Both numbers are agreed in writing on day one, and reused afterwards.

Capacity

How much work the team got through in a set stretch of time, say 40 renewals a week. Work handled in a stated period

Turnaround

How long one piece of work takes from the moment it lands to the moment it is done, waiting included.

Elapsed time from an agreed start to an agreed end

Depending on the agreed workflow, we examine

Volume in a stated periodWorking time and waiting timeStart, completion, and turnaroundTouches and handoffsOwners and approvalsBacklog, where it can be defined

Not every measure exists for every workflow. Setup says which evidence is usable.

WHAT GETS MAPPED

Make the full route visible.

Fourteen fields, in order. Missing or disputed answers stay marked: no path finished from assumption. One agreed operating route, written down end to end

One agreed operating route, written down end to end

Trigger

What starts it, and who sets it off.02

Inputs

Documents, data, and messages it needs.03

Systems

Where the work is actually done.04

People and owners

Named, not job-titled.05

Handoffs

Every point where it changes hands.06

Decisions

What has to be judged, and by whom.07

Approvals

Who is authorised to say yes.08

Rules

Written, assumed, or in one head.09

Exceptions

Cases that break the route.10

Waiting time

Time the work sat still.11

Working time

Time someone was on it.12

Completion

What everyone agrees is done.13

Volume

How often, over the agreed period.14

Turnaround

Agreed start to agreed end.

Unknown owner, disputed rule, evidence we could not see: marked, never smoothed over.

HOW OPPORTUNITIES ARE RANKED

Rank the work, not the tools.

No single score decides. Three questions sort it: pass one, fail two, it waits.

QUESTION ONE

Does it matter?

Frequency, team time, delay, capacity, turnaround. Twice a quarter can wait.

QUESTION TWO

Is the workflow understood?

Boundaries, owners, inputs, rules, and a completion everyone recognises.

QUESTION THREE

Can it be bounded?

Stable rules, usable inputs, known exceptions, defined review.

Use the simplest appropriate level. Higher autonomy is not inherently better.Tool choice comes last.

What you receive

A measured view of one workflow.

Six documents. Outputs of the audit, not proof of later improvement.

Current-state workflow map

The agreed route: owners, systems, decisions, approvals, exceptions, completion. Gaps marked.

Supported baseline

Capacity, turnaround, working and waiting time, only where evidence supports a definition.

Three ranked improvements

Ordered by evidence and operating fit. Unknowns left visible.

Human-review boundaries

Judgment, approvals, exceptions, escalation, stop conditions.

Recommended first implementation

The simplest bounded next build, if one is warranted.

Fixed-price implementation brief

Scope and acceptance tests. “Build nothing yet” is a valid finding.

Measurement and mapping only. Implementation, dashboards, and reporting are separate.

HUMAN REVIEW AND CONTROLS

Keep people where judgment matters.

The map marks every decision, approval, exception, and owner before automation is chosen. Tax, accounting, and advice judgment stay with your people.

A person approving work before it continues

APPROVAL

EXCEPTION

The four DAWN levels →

Fixed rules, predictable inputs

May suit deterministic automation. No model needed.

AI prepares or recommends, a person reviews

The draft is machine work. The send is yours.

Bounded multistep work needs checkpoints

Named exception paths and a place to stop.

Some workflows can be designed around AI

Only with clear ownership and controls. The audit switches nothing on.

HOW IT RUNS

Measure. Map. Decide what comes next.

Scope the audit

Business unit, candidate workflows, usable evidence.

Measure and map

Routes, handoffs, delays, volume, turnaround, as far as evidence supports.

Review the opportunities

45 minutes: what to pursue, what stays uncertain, where people stay.

Choose the next step

Scope a build, gather more evidence, or stop. Stopping is a real answer.

Five business days after access and evidence are validated. Anything beyond one workflow, one unit, five inboxes, or twelve months gets a separate scope.Start my Team Workflow Audit

FIT

Built for work that crosses a team.

Trust is earned one workflow at a time.

A good fit looks like

A team of eight or moreRepeated work that crosses people or systemsLeadership able to sponsor access and decisionsA preference for measuring before implementing

Accounting and tax firms

EXAMPLES, NOT CLIENT RESULTS

Client onboardingDocument collectionStatus updatesAssignmentsReviewsDeadlinesSeasonal capacity

Where audits get pointed. Examples, not client results.

Straight answers

Scope, price, what we need from you, and what happens when the answer is “don’t build it.” Work passing between team members with an owner at each step

No. The free audit inspects one inbox. This one measures and maps a workflow across a team: different scope, different price.

A request routed through automation with a person reviewing it before completion

See the whole workflow before choosing what to automate.

Twelve months of up to five inboxes, $1,500 USD upfront. Anything outside that gets its own scope.

Start my Team Workflow Audit Start with one free inbox audit

TEAM WORKFLOW AUDIT · $1,500 USDSee the whole route of one workflow before automating any of it.Twelve months of up to five inboxes, the map, credited if we build.Start my Team Workflow AuditPaid upfront · Credited if we build

One person sees a task. The team reveals the workflow.

Personal AI use helps with a task. It cannot show where work starts, who touches it, what waits, or what counts as done.

RequestWhere does it start, and how many arrive in a week?OwnerWho picks it up, and who assumed someone else had?HandoffHow long does it sit between two desks?Decision, stays with a personWho is allowed to decide, and what happens when they are out?CompletionWhat counts as done, and who agrees it is?

Answer all five for one workflow and the automation decision makes itself.Not looked at one inbox yet? Start with the free inbox audit.