Examples of deviations

What counts as a deviation depends on the business's requirements and procedures. These constructed examples show different kinds of situations that may need follow-up:

  • HSE: a walkway is blocked by materials, contrary to the site's procedures.
  • Quality: a delivered item has a different specification from what was agreed.
  • Procedure: a planned inspection has not been carried out or documented.
  • Environment: waste sorting does not follow the business's waste procedure.

Deviations, near misses and suggestions for improvement

A near miss is an event that could have caused harm. It can be reported and followed up in the deviation process when your procedures allow for it. Nobody needs to have been hurt for a situation to be worth looking into.

A suggestion for improvement can be about a better way of working without any requirement being breached. Use your own categories, and let your procedures explain how employees should report.

What should a deviation report contain?

A good report gives the person following up a concrete starting point. Describe what you observed before trying to explain the cause.

  • What happened or was observed?
  • Where and when did it happen?
  • Which requirement or procedure does it deviate from, if known?
  • What immediate action has been taken according to internal procedures?
  • Are there relevant photos or other documentation?

The report needs an owner

Follow-up should establish severity, ownership and the next step. Later, the team can investigate the cause, carry out actions and assess the result before the case is closed.

SmartDeviation lets employees report with photos in the mobile app and take the case further on the web. You can also use the incident report form as a starting point for deciding which information you need.