Click New Policy. Write it in the built-in editor (headings, lists, tables) or upload an existing document.
Follow one policy from draft to proof.
Write it, describe it, send it for approval, publish it, keep every version, improve it with suggestions, and prove people read it. Scroll and watch the policy on the left change.
Set category, owner, review date, relevant frameworks and your own reference ID (for example POL-HR-004).
Send it through the approval workflow, where chosen approvers accept or reject.
Move it through the lifecycle: Draft → Under Review → Approved → Published → Archived.
Every content change is saved as a version. Click a version to read exactly what the policy said on that date and who saved it, or restore an older one.
Optional AI analysis reviews the policy and suggests improvements.
The employee opens it in a reader. A timer ensures they spend a minimum amount of time reading before the Acknowledge button works. This prevents instant click-throughs.
Acknowledgement that stands up in an audit
Proof that employees have read and agreed to policies.
"We published the policy" is not enough; auditors want proof each person saw it.
How it works- Assign a policy to employees. It appears in each person's My Learning.
- The employee opens it in a reader. A timer ensures they spend a minimum amount of time reading before the Acknowledge button works. This prevents instant click-throughs.
- The acknowledgement is recorded with a timestamp.
- The Policies page shows the percentage who have acknowledged each policy.
Who uses itEmployees acknowledge; managers monitor.
Try it: the button waits for 20 seconds of reading.
Four numbers on the Policies page
Four KPI tiles show policies needing approval, ready to publish, renewing soon, and renewal past due.
Needs approval
Waiting on an approver.
Ready to publish
Approved, not yet live.
Renews soon
Review due within 30 days.
Renewal past due
Review date has passed.