A procedure is only controlled if everyone can tell which version is in force and prove what it said on any given day. Swat iQua Suite separates approval from going effective and freezes the effective version as a controlled-copy PDF, so the document an operator printed last year is exactly the document an inspector sees today.
Why approval and go-live are separate
In practice an SOP is often approved days or weeks before it takes effect, to give time for training and roll-out. Swat iQua Suite reflects that: the approved SOP stays “awaiting go-live” until someone makes it effective. Only then is the controlled copy saved and training based on the new version can begin.
Controlled copies
- The controlled-copy PDF is generated once, at make-effective, and saved — it cannot be altered.
- Reprints come from that saved file and are never regenerated from live data.
- Before approval, a watermarked preview is available for review.
- The rich-text body is sanitised again when the PDF is rendered.
Revising an SOP
Editing an effective SOP reopens the review and approval workflow. The version number moves up when the revision is approved, and every change, with its reason, is recorded in the audit trail.
From SOP to training
An effective SOP prompts the creation of a training in Training Management, and a training can only be created from an approved, effective SOP version. On the shop floor, batch steps, dispensing and packaging check that the operator is trained on the linked SOPs before work can start. See how documents and training work together on the document and training management page.