The SOP lifecycle
SOPs in Swat iQua Suite move from draft to review, approval and a separate make-effective step. Approval does not put an SOP into use on its own: an approved SOP waits “awaiting go-live” until someone deliberately makes it effective, so the date it takes effect is a recorded decision. Editing an effective SOP reopens the workflow, and each approval moves the version on.
Segregation of duties is enforced by the server — the reviewer cannot be the author, and the approver cannot be the author or the reviewer — with no administrator bypass. The signature block shows each signer’s designation at the time they acted, not their current job title.
Controlled copies that cannot drift
When an SOP is made effective, a controlled-copy PDF is saved and can never be changed. Reprints use that saved copy rather than regenerating it, so the document an inspector sees is the document that was approved. A watermarked preview is available before approval, and reference numbers follow your departments.
Global SOPs across sites
Group-wide procedures can be shared across sites as global SOPs, with their trainings copied to each site, while site-specific SOPs stay local.
Swat iQua Suite controls SOPs and the training that follows them. It is not a general learning management system — every training starts from an effective SOP version.
