1
After the slow run58 minutes vs. a 45-minute target. The total is in the shift report.
Debrief runs 20 minutes. Everyone blames a different cause. Action item fixes nothing — evidence was never captured.
Changeover Analytics
You tracked the total. You don't know what drove it.
Every changeover ends with one number: total duration. Shift report, spreadsheet, whiteboard. It tells you the run was slow — not why.
The same bottleneck, three times over.
Missing task-level data hits every review, every debrief, every week you can't explain variance.
2
The comparison you can't makeTeam 1 averages 41 min, Team 2 averages 58 min on the same changeover.
Gap confirmed; location unknown. "Investigate Team 2" is the plan — no task standardised, 17-minute gap persists.
3
Week over week, nothing changesYou cut the mould swap standard from 12 minutes to 10. Performance doesn't improve.
Wrong standard or wrong compliance? Without task drift data, you optimise the wrong variable. Bottleneck moves; total stays put.
Why total duration fails as a diagnostic
Most plants capture changeover data at the wrong level. Total duration is a useful summary. It is a useless diagnostic.
Every debrief minute spent asking "does anyone know why it ran long?" is reconstructing data that should have been captured during the run.
The problem isn't effort. It's resolution.
What you have vs. what you need
You have
Total duration
You're missing
Time per task
A slow total is a symptom. The task that caused it is the diagnosis.
You have
A slow run
You're missing
Which step made it slow
You can't write a corrective action for "the run was slow".
You have
A pattern you suspect
You're missing
Data to confirm and act on it
Suspecting a bottleneck and proving it are two different plans.
When the run ends, the Gantt is ready.
Operators mark tasks complete on a tablet as they work. Every tap is a role-attributed timestamp — the run record builds itself. Nothing to fill in after.
At close, a task-level Gantt appears automatically: which step ran long, which role, idle gaps, vs. standard. Root cause without asking anyone to log anything.
Critical path visible. Which tasks drove the total — where the next SMED cycle should focus.
Idle gaps surfaced. Handoff wait time shows as hatched gaps — immediately actionable.
Role attribution clear. Bars coloured by role — Internal, External, or Post-run delay.
Line 3 · SKU-A100 → SKU-B200 *
Run completed 14:22 — Wed 26 Feb
58 min total Post-run · +13 min over target
0m10m20m30m40m50m58m
Belt clean
Internal
Temp ramp
Internal
Mould swap
External
+8 min over std
Waiting
— idle —
IDLE
Set pressure
Internal
First-piece QC
Post
▲ target 45 min
Internal External Post Idle gap Target (45 min)
* Product may differ from mockup.
Track performance across runs, teams, and lines.
Each run adds to history. Same changeover type, eight runs, two teams — improvement visible without manual aggregation.
Breakdown chart: Internal / External / Post per run. Trend line: where improvement came from — here, External dropped 42% → 26% as mould swap standard tightened and compliance improved.
Breakdown per run
Internal / External / Post split across 8 runs
target 45 min
Run 1
61 min
Run 2
58 min
Run 3
55 min
Run 4
52 min
Run 5
49 min
Run 6
46 min
Run 7
44 min
Run 8
43 min
Internal External Post Target
Total duration — 8 runs
From 61 min down to 43 min
Total duration Target (45 min) Over target Under target
The run record is the source. Stack runs and every comparison is there: team, shift, task, line, this week vs last month.
You don't build the report — you decide what to fix.
After your first run
Your next slow run will be the last one you can't explain.
Every run generates a task-level Gantt automatically. Configure once — every changeover after that produces the data for root cause and trends.
-
Timestamped sign-off
Audit-ready from run one
-
Gantt of every task
See where time was lost
-
A repeatable standard
Not tied to who showed up
7-day free trial · Self-serve · No IT project