Skip to content
Work Instruction App Work Instruction App

Deviations and checks during the work

Last updated:

In short

In the Work Instruction App you build the checks into the work instruction itself: a number step gets a minimum and maximum, a barcode step an expected value, and in a choice step you tick which answers count as a deviation. A wrong number or barcode stops the operator until it is corrected. Every saved run is then judged against its version, and a run with a deviation is labelled and easy to find.

A value outside the tolerance that is only noticed at the end of the week is a missed chance to act. Put the limits in the instruction, and the deviation shows up while the operator is still at the machine.

What it looks like in the app

Details of a completed forklift check with the Deviations section on top: a damaged fork and a tyre pressure below the minimum, the steps marked in red
Deviations at the top of the run, with links to the marked steps.
Run mode of a forklift check: a tyre pressure of 11.5 bar is marked because the allowed range is 8 to 10

Minimum and maximum for measured values

Give a number step an optional minimum and maximum in the editor. When the operator enters a value outside that range, the step is marked and Next and Finish only work once the value is corrected. Put the corrective action on the same page, so the operator knows what to do before entering the new value.

An expected barcode

A barcode step can expect one value, for example the article code of the right material or the code of the right tool. A different scanned or typed code is marked and blocks Next and Finish, so the wrong part is noticed before it is used.

Not OK, a low rating or a count outside the norm

Not every check is a number. An OK / Not OK step answered Not OK is a deviation and can require a remark or a photo before the operator goes on. In a Checklist every point answered Not OK is its own deviation, named after the point. A Rating below its minimum and a Counter outside its norm are recorded as well, without stopping the operator. Add a Follow-up task that only shows after a Not OK, and the repair is assigned to a colleague in the same run.

Editor with a choice step selected: under Deviating answers the option No is ticked

Answers that count as a deviation

In radio buttons, a selection list, checkboxes or a switch you tick in the editor which options count as a deviation, for example No at Guard in place. The operator can still choose that answer, because it may be the truth, but the run is marked. Combine it with a step that only appears when that answer is chosen, such as a repair or a report of the defect.

Editor with the page Repair, shown only when the answer to Forks and chains undamaged is No

Pages that only appear when needed

A page can be set to Only show when an answer to a choice step on an earlier page equals a chosen option, for example a repair page only when the check is answered with No. Hidden pages are skipped by Next and Previous, do not count in the progress, and a required step on a skipped page does not block Finish. In the run details a skipped page is shown as skipped.

Runs overview filtered on runs with deviations, with a Deviation label per work instruction

Find every run with a deviation

The server judges every saved run against the version it was carried out with: a number outside its minimum or maximum, a barcode that is not the expected value, a deviating option that was chosen, a Not OK answer, a rating below its minimum or a count outside its norm.

  • A label on the run in the runs overview, and the filter With deviations to show only those runs
  • A Deviations section at the top of the run details, with each deviating answer and a link to its step
  • The deviations on the print page of the run and in the export to Excel or CSV

Patterns in the dashboard

With an Analyze subscription the dashboard shows deviations per week, the steps that deviate most often and a list of all deviations with links to the runs. A step that keeps deviating usually points to a cause in the process or in the instruction itself. See reports for everything the dashboard shows.

Frequently asked questions about deviations

No, deliberately not. Deviations are visible in the runs overview (label and filter), at the top of the run details, on the print page and in the dashboard. When a run must be checked before it counts, switch on Approval required: the Manage users then get an e-mail for every completed run, see approval and review.

Not with a number outside the minimum and maximum or a barcode that differs from the expected value: Next and Finish only work once it is corrected. An answer marked as a deviation in a choice step can be chosen; the run is then marked, and a page with Only show when can ask for the follow-up.

Against the version the run was carried out with. When you change a limit in a new version, it applies to the runs of that new version.

Yes. Switch on Required in the step properties: the operator cannot go on until the step is filled in. Together with a minimum and maximum, a measured value is then both present and within range.

Setting up the checks is part of creating work instructions, which needs Manage. Every operator with Execute works with them. The run details with the Deviations section and the dashboard need Analyze. See pricing.

Try the Work Instruction App for free

Create your first digital work instruction in minutes. 30-day free trial, no credit card required.

Start your free 30-day trial

No credit card · Cancel any time · Live in 5 minutes

Start your free 30-day trial · no credit card