Draft, review, approve and release your SOPs. Every step is a signature that records its meaning, every stored file is checked against its SHA-256 when it is read, and the people who must read a new version are assigned it the moment it takes effect.
Draft, in review, approved, effective. The author cannot approve or release their own revision. Releasing a new revision supersedes the previous one in the same step, and any copy that is not the effective version is marked as uncontrolled.
When a revision takes effect, everyone in its training departments is assigned that version, and open assignments on the old one are closed. Each person signs “read and understood” against the effective file, and the training matrix shows who is trained on what.
Every regulated change writes its audit entry in the same database transaction, or not at all. The database rejects changes and deletions of audit entries for every account. Filter the trail, read what changed from before to after, and export it as a numbered PDF.
Veritas controls documents and the training that follows them. Change control, deviations and CAPA, and single sign-on are on the roadmap; until then, keep your current tools for them. Validation stays your responsibility, for your intended use and procedures.
Write to the product team for a walkthrough. Bring one of your SOPs and see it go from draft to trained.