A register that tells you what's due
Every document has a number, an owner, an approver, a classification and a review frequency. The register shows what's in date, due soon and overdue, and the Dashboard says what to do next.
| Number | Title | Version | Owner | Next review | Status |
|---|---|---|---|---|---|
| PC-POL-001 | Information Security Policy | 3.0 | Priya Shah | 14/08/2027 | In date |
| PC-POL-002 | Acceptable Use Policy | 2.0 | Sam Patel | 28/10/2026 | Due soon |
| PC-POL-005 | Business Continuity Plan | 1.3 | Joe Okafor | 02/09/2026 | Overdue |
| PC-POL-007 | Access Control Policy | 2.2 | Priya Shah | 11/03/2027 | In date |
Example register, demo data
Your registers, under the same control
Asset, risk and supplier registers, the record of processing activities and the subprocessor list live here as tables, from a template or your own spreadsheet. Keep one controlled, approved version by version, or living, with dated snapshots approved for the auditor.
- Columns that check themselvesDates, choices, people from your staff list and links to your policies.
- PDFs tooUpload a signed certificate or a supplier's document and control it like the rest.
- A second pair of eyesAI review flags contradictions and gaps before approval, and drafts the summary of what changed.
| Supplier | Processes personal data | DPA | Next review |
|---|---|---|---|
| Google Workspace | Yes | PC-LEG-004 | 03/2027 |
| Stripe | Yes | PC-LEG-006 | 11/2026 |
| Linear | No | Not needed | 06/2027 |
Example register, demo data
Everything the auditor asks for, in one download
Approved versions are fixed, hashed and stored as PDFs with a document control block. Each acceptance records the version, the exact statement, the time, the IP address and the browser.
- The registerAs PDF or CSV, with review status.
- Every approved versionAs the PDF that was in force, marked "Uncontrolled when printed".
- Who accepted whatAcross everyone, or one person's full history.
- The audit logWho drafted, approved, sent and changed what, and when.
- documents/Every version, and each approved PDF as stored
- register.csvThe register with review status
- acceptances.csvEvery acceptance and its evidence
- customer-acceptances.csvSign-up acceptances from your clickwrap
- reviews.jsonEvery periodic review
- audit-log.jsonEvery change, by whom and when
- people.jsonWho was asked to accept
Proof anyone can check
Every acceptance gets a proof of record. It's digitally signed and locked against change or deletion for seven years. Anyone holding one can check it here, and the check never shows who accepted.
Checking proofs from your own code? Use the verify API.
Security reviews without the folder hunt
When a customer's security team asks for your policies, send a shared link to exactly the documents they need, current versions only, with an expiry date. They read online or download the lot.
“Our enterprise clients always want to see our policies before they sign. Now we send one link instead of hunting through folders, and security reviews that used to hold up deals go straight through.”
Start with the folder you already have.
Drop in your Word, PDF and text files, archived versions included. Approve them as version 1.0, send them to your team, and every acceptance gets a signed proof of record.
Try Business free for 30 daysBring your policies folder
Word, PDF and text files, archived versions included
- Then: Review and approve them as version 1.0
- Then: Send to your team and track acceptance
- Then: Publish your public policies on your website
- 30 days free, cancel any time
- No logins or accounts needed for your staff
- Hosted in London