Document summary
This page explains drafting, review, approval, publication, acknowledgement, and archival, and how the platform prevents unapproved publication.
Unified register
Each document has a code, version, status, scope, audience, owner, reviewer, approver, effective and review dates, and supersession link. Public text points to a specific content version, not the latest unpublished edit.
Lifecycle
States are draft, in review, changes required, approved, scheduled, effective, superseded, and archived. A document cannot become effective before required reviews and its effective date.
Review
The subject owner reviews operations, Privacy reviews data, Security reviews controls, Legal reviews obligations, and translation review checks meaning. Each reviewer approves their assigned scope and records notes.
Material change
Review determines whether a change expands purpose, reduces a right, increases retention, adds a provider, or changes an obligation. Material changes require notice and renewed acceptance where applicable.
Acknowledgement and training
A policy defines who must read or acknowledge it and by when. Page opening is not acknowledgement. The record captures user, version, time, and method and repeats for versions requiring it.
Archive and authority
Prior versions remain reviewable subject to access and retention. The public page shows a concise change log and identifies the authoritative version for translation differences without deleting prior history.
Versions
Change log
- Version 1.0.0
Published the first operational version with clear scope, responsibilities, rights, and escalation routes.