Skip to content
Request a demonstration

SOP Intelligence · Enhance an existing SOP

Improve an approved SOP without losing the approved one.

Choose an existing SOP and its version. Averyniq proposes clearer wording, a missing check and a better order, shows every change beside the original, and says what the change could affect before it goes for review.

Example: Northgate Distribution (fictional) · Forklift pre-use check · version 3.0 (approved)

Simulation. Scripted example on fictional data. No file is uploaded, no model is called, and nothing here is a real customer, procedure or result.

  1. Source
  2. Analysis
  3. Draft
  4. Review
  5. Approval
  6. Published

The approved SOP and the proposal

Version 3.0 (approved) stays as approved

  1. Check the paperworkCheck the daily log is available and the truck is cleared for use.
  2. Inspect the truckWalk round the truck and check tyres, forks, mast and chains for damage and leaks.
  3. Test liftRaise and lower the forks to check smooth movement.
  4. Test the controlsTest brakes, steering and the seat belt.
  5. Report faultsReport any fault and do not use the truck until it is cleared.

What the proposal changes

  • KeptCheck the paperwork: unchanged.
  • RewordedStep 2 split into short actions in walking order.
  • AddedHorn check added, because the incident log refers to one.
  • MovedTyre and fork inspection now comes before the lift test.
  • Reworded“Do not use the truck” made explicit and tied to who clears it.

What the change could affect

AreaFindingNeeds review
TrainingOperators trained on version 3.0 would need a short briefing on the horn check and the new order.Yes: material
SafetyOne check is added; none is removed.Yes: material
ResponsibilitiesThe supervisor still clears a faulty truck; the wording now says so.No
RecordsVersion 3.0 stays on record, approved and unchanged; the new version needs its own approval.No

The SOP and the version being improved

SOP
Forklift pre-use check
Version
3.0, approved
Owner
Warehouse manager (fictional)
Request
Make it easier to follow and check for anything missing

Confirm the statement above to continue.

How it is governed

  • The approved version is never edited: a change is a new version with its own approval.
  • Material changes are routed to the reviewer with their effects listed.
  • Old versions stay in the history.

What this is for

An approved SOP gets better without anyone losing what was approved.

What this page does not do

  • This page does not read a real SOP.
  • The proposed changes were scripted for the example.
  • No change reaches workers until it is approved and published.

The other ways in