Policy management
Policies written, approved and kept current
Clients and insurers ask to see your policies. This module gives you ready-made ones, a clear approval trail and a record that your team has read them.
Fix what matters first
Policies are the part everyone puts off.
Starting from a blank page
Writing a password policy or an acceptable use policy from scratch is slow, and most owners are not sure what it should say.
Nobody has read them
A policy that is filed and never read does not change what people do, and you cannot show that anyone has seen it.
They go out of date
Policies written once and never reviewed stop matching how the business works.
What changes
From a blank page to signed-off policies.
First
You start from ready-made policy templates linked to the security measures they support, and edit them to fit your business.
Then
Policies are approved and sent to staff, and you can see who has acknowledged each one.
Ongoing
Review dates are tracked and reminders go out, so policies stay current.
How it works
How it works.
Start from a templateThe structure and the links to security measures are already done.How this works underneath
Templates cover areas such as acceptable use, passwords, data handling, incident response, AI use, suppliers and business continuity. Each is linked to the SMB1001 it supports.Approve and send to staffA clear sign-off, with who approved what and when.How this works underneath
Policies move through draft, review and approval. Approved policies can be sent to staff for acknowledgement, which is recorded per person with a date. Every change is versioned.Keep them currentReviews are scheduled, and the record feeds your proof pack.How this works underneath
Review dates and reminders are tracked. The policy, its version history and the staff acknowledgements are kept as and appear in your proof pack.
A small example
What this can look like.
- Situation
- A client's security questionnaire asks for a password policy. The firm does not have one.
- What changes
- The owner starts from the template, adjusts it, and approves it.
- What happens next
- It is sent to all staff. Thirty-six acknowledge in the first week and the rest are reminded.
- What is kept
- The policy, its version and each acknowledgement are kept as evidence.
This is an invented example to show how the module works. The names and figures are not a real customer's.
What is in it
What is in policy management.
Policy library
Every policy in one place, version controlled and linked to the security measures it supports.
Templates
Ready-made policies aligned to SMB1001 that you edit to fit your business.
Staff acknowledgement
Send a policy to your team and track who has read it, with dates.
Version history
See who changed a policy, what changed and when.
Review reminders
Review dates tracked so policies do not go stale.
Proof pack integration
Policies, history and acknowledgements flow into your proof pack.
Questions
Common questions.
No. You can upload your own policies, or start from a template and edit it.
Each policy can be sent for acknowledgement, and the platform records who acknowledged it and when.
Yes. Policies edited outside the platform can be uploaded as a new version, keeping the history of who did what and when.
Related
Works with.
Get your policies sorted.
The free readiness assessment shows you where you stand and what to fix first. If we are not the right fit, we will tell you that too.