CraftAClause is built with — and for — small business operators. Browse the ideas below, vote for the ones you need, or add your own. We read every single one.
PDF export works well for handing a finished policy to an auditor, but plenty of teams need to drop the document into their own letterhead or a customer's required format. A .docx export alongside the existing PDF would cover that. Vote if this would help you.
Once a policy is published, most of us need proof that staff actually read it — a link you send to the team, a record of who acknowledged which version and when, and a nudge for the people who haven't. This pairs naturally with the version history that already exists: an acknowledgement should be tied to the exact version someone read.
From the team: On our roadmap. Acknowledgements will be tied to the exact policy version someone read.
Review reminders currently arrive by email. For teams that live in Slack or Teams, a reminder in the channel where work actually happens is much harder to ignore. A simple incoming-webhook integration per workspace would cover the basics: review due, review overdue, policy published.
From the team: Planned — likely starting with simple incoming webhooks before a full app integration.
When a security questionnaire or audit asks "which policy covers control X", the mapping today lives in someone's head or a spreadsheet. It would save real time if each policy could be tagged against the SOC 2 trust criteria / ISO 27001 Annex A controls it addresses, with a coverage view showing which controls have no policy yet.
From the team: Planned. We want the mapping to be reviewable, not auto-claimed — an auditor should be able to trust it.
Magic links work, but teams already living in Google Workspace or Microsoft 365 expect to click "Sign in with Google" and be done. Larger customers will eventually ask for SAML and SCIM provisioning too. Vote if password-less email links are a blocker for rolling this out to your team.
Most businesses aren't starting from zero — the policies exist already, scattered across .docx files and Google Docs. Importing pasted text works today, but a direct file upload that preserves headings and numbering would make moving an existing policy set in much less tedious.