Workflow Bottleneck Diagnostic Tool

Find where a sequential workflow spends the most time waiting. Enter stage timings from the same sample to compare delay candidates and decide what to investigate first.

Use the workflow diagnostic Read the companion guide

A ranked delay table, waiting share and next investigation.

Enter your own evidence, or try the clearly labeled fictional example. Generate a report, print it or save an editable copy to reopen later.

Inputs stay in page memory and are not submitted to Regal Nexus Group. Work is not saved automatically. Save an editable copy before leaving and store downloaded business information deliberately.

Prepared by the Regal Nexus Group editorial team. Version 1.0 · 21 October 2026.

Find the delay worth investigating

Compare stage timings and backlog to create an evidence-led investigation brief. Use one sequential workflow and the same sample for every stage.

You will create: A ranked delay table, waiting share and next investigation. Read the companion guide.

Define the review

Workflow name

For example, customer onboarding.

Responsible owner

Required.

Review period

For example, the previous four weeks.

Cases completed in this period

Use the same period for all observations.

Sample and measurement method

Record sample size, timestamps used and any missing evidence.

Workflow stages

Use at least two sequential stages. Do not add parallel or overlapping times.

Stage 1

Stage name

Required.

Mean active work per case (hours)

Convert minutes to hours: minutes ÷ 60.

Mean waiting time per case (hours)

Exclude active work and overlapping waits.

Cases waiting now

A snapshot count, measured consistently.

Evidence / suspected cause

Separate what you observed from what you suspect.

Stage 2

Stage name

Required.

Mean active work per case (hours)

Convert minutes to hours: minutes ÷ 60.

Mean waiting time per case (hours)

Exclude active work and overlapping waits.

Cases waiting now

A snapshot count, measured consistently.

Evidence / suspected cause

Separate what you observed from what you suspect.

How this tool works

Use one workflow with a clear start and end. Record active and waiting hours from the same representative cases.
The tool adds sequential active and waiting time, calculates the waiting share and sorts stages by mean waiting time. Backlog is recorded separately.
A long wait is an investigation candidate. Confirm capacity, dependencies and root causes before calling it a proven throughput constraint.

A worked example

In the fictional example, contract approval waits 18 hours per case. The full sequential cycle is 25.25 hours, so the next step is to investigate approval timing and capacity.

Questions before you use it

Does the longest wait prove the bottleneck?

No. Waiting can arise from batching, missing inputs or dependencies. Establish what limits end-to-end throughput before choosing a fix.

Can I use parallel workflow branches?

Do not add overlapping branch timings as if they were sequential. Review one sequential path at a time and record the measurement boundary.

Download the companion checklist (PDF) · Read the full guide

Discuss this workflow delay

Bring your diagnostic brief to a free 30-minute assessment. Discuss where work waits, which evidence is missing and whether an operational diagnostic would help.

Discuss this workflow delay

Your inputs and report are not sent automatically when you open the booking page.

Explore our services · How we work