For platform admins

Platform admins maintain the master SOP library that organisations adopt. You write the canonical procedures; clinics take them and run.

Publishing a version

In Master library, open an SOP (or create one) and use the editor. Each publish creates a new immutable version with a changelog, so history is preserved and every change is diffable. Clinics tracking the SOP pick it up automatically.

Significance & re-certification

When you publish, choose a significance:

• Minor — typo or formatting. Does not force staff to re-train.
• Moderate / Major — a material change. Staff who were trained on an earlier version become due to re-certify.

This means you can fix a comma without making hundreds of people re-take a knowledge check, while genuine policy changes still propagate properly.

Knowledge checks

Edit each SOP’s knowledge check in the same screen as its content, so the two never drift apart. Questions, options, the correct answer, an explanation and the pass mark are all editable; options are shuffled automatically.

Review cycle & the digest

Each SOP has a review interval and a next-review-due date. The Contributions & reviewsdashboard shows who has been editing, how significant their changes were, and which SOPs are overdue or due soon for review. A weekly email digest can flag what’s due.

The cascade

Your master set flows down to each organisation and clinic. Organisations can hold their own master and deploy it to their sites; sites can track or customise. Everyone can diff their copy against the source above them, and adopt updates when they choose.