Features
Available nowPolicy management
Govern policy intent with versioning, approval routing and scheduled review, so the published policy is the approved one.
The problem it solves
Policies drift. A draft becomes the working version, the approved copy sits in a different folder, and the review date passes unnoticed until an assessor asks when the document was last approved.
How it works
- 1
Draft and version
Every change creates a version. The history shows what changed, who changed it and when, which is the question an assessor asks first.
- 2
Route for approval
Policies move through review to an approver. Approval is recorded against the specific version, not the document in general.
- Version history retained in full
- Approval recorded per version with approver and date
- Scheduled review dates with advance notice
- 3
Link to controls
Policies connect to the controls that implement them, so a policy statement is traceable to the operational practice behind it.
Capabilities
Version control
Complete history with authorship and change dates.
Approval workflow
Review and approval recorded against the version approved.
Review scheduling
Cadence per document with notice before the date passes.
Control linkage
Policy intent traceable to implementing controls.
What you remain responsible for
- Authoring and approving policy content
- Deciding review frequency for each document
- Confirming a policy reflects how the organisation actually operates
Related capabilities
See NOVA against your own compliance obligations
Explore the governed Free access path, or walk through your framework, evidence and reporting requirements with us.
NOVA accelerates your launch preparation, but final decisions remain human.