Torque spec is 45 Nm. Operator got 47 on the third attempt. Task shows completed.
Borderline result is invisible. No flag, no note. If the tool is drifting, there's no record of when it started.
Operator comments & deviations
The task shows completed. The deviation doesn't.
Operators add a plain-text comment on any task before complete — same screen, about ten seconds. Timestamped on the run record. Timing data shows what ran long. Only the operator can tell you why.
What disappears when there's nowhere to write it down
Deviations that get handled — then vanish from the run record.
Something went wrong on Task 4. The engineer asks what happened.
Operator is already on the next job. Best anyone offers is a shrug. Next run starts from the same blank slate.
CI suspects the seal swap keeps causing rework.
No step-level observations to confirm it. The improvement case has no evidence. The standard stays unchanged.
Operator leaves a note. Engineer reads it in the run record.
One field on the task screen, before mark complete. No separate deviation log. Operator writes what they saw — including measured values — and moves on.
After the run, flagged tasks sit in the post-run record with the exact note. Review starts with observations, not "does anyone remember what happened on the third step?"
Task in progress
Torque clamp bolts to spec
Operator
Comment — value & observation
optional47 Nm— required three passes before torque settled. Check wrench calibration.
Timestamped · attached to this task · saved with run record
Measured value goes in the comment with the observation.
From a single observation to a confirmed pattern.
One comment is context. The same note on 6 of 8 runs is evidence — a case for replacing the wrench or tightening the spec.
Without capture, SMED cycles start with interviews: who was available, what they remembered. With task-level comments, open run history, filter the task, read what operators wrote.
Operators were already noticing it. Now you have a record.
Torque clamp bolts to spec
Last 8 runs · Line 3
"47 Nm — required three passes before torque settled. Check wrench calibration."
Same wrench issue flagged across 6 runs. Action: schedule calibration or replacement.
Related
Live operator visibility during changeover
Every step, role, and delay as it happens.
Post-run analytics & changeover performance
Run record — including comments — feeds task-level Gantt and multi-run trends.
How to track changeover performance with a Gantt timeline
What a changeover Gantt shows and what to act on.
After your first run
Your next improvement case starts with evidence, not a hunch.
One changeover, one run. Operator observations timestamped and attached to the task — answers ready when review starts.
-
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