Take the tour
A 60-second walkthrough of PolicyDesk
You are the Compliance Officer at Arbor Health, a 1,200-employee SOC 2 Type II shop. Legal just rewrote the data-retention policy — the retention window changed from 30 to 90 days. That is a substantive change. Walk through how PolicyDesk drafts, reviews, publishes, re-attests, and produces audit evidence.
Click any step to start the tour from there. A green banner stays at the top of every page so you always know what to look at and how to advance.
- 1Viewing asPolicy author·/policies
Author drafts the updated policy. AI generates the plain-language summary and flags the retention-window edit as substantive. Author confirms.
- 2Viewing asReviewer·/reviews
Reviewer queue: data-retention policy routes through SME, legal, and security in sequence (restricted category). Each reviewer signs off or requests changes.
- 3Viewing asExecutive approver·/reviews
Once all required reviewers approve, the policy lands in the executive queue. Executive signs off; publication unlocks.
- 4Viewing asHR / People Ops·/admin/audiences
HR confirms the audience rule for this policy: all US-based employees plus contractors with data access. 847 employees fall in scope.
- 5Viewing asEmployee·/attestations
Employee inbox: the updated policy appears as a new attestation task. Because the change was substantive, prior attestations to v1 were superseded — re-attestation is required.
- 6Viewing asCompliance officer·/
Compliance dashboard: coverage moves toward 100% in real time. Overdue attestations surface by team. Expiry calendar updates with the new annual review date.
- 7Viewing asAuditor·/audit
Auditor read-only view: every state change above — drafts, reviews, exec approval, publication, audience evaluation, attestations, supersession — is in the audit trail. Exportable as an evidence packet.
What you will learn
You just saw a substantive policy update move from author draft (AI summary + change-impact) → category-gated reviewer chain (SME → legal → security) → executive approval → audience-rule evaluation → re-attestation across 847 employees → audit-evidence packet. Every prior attestation was preserved as superseded, every reviewer decision was timestamped, and the auditor can hand-walk the entire history with one export.
Tip: every state change in this app emits an audit event — open /audit to see the trail.