Policies

Policy management in Keel

Policies are the written commitments behind your controls. Keel gives you a full policy management workflow, from a first draft to an approved, versioned, framework-mapped document you can export and share.

Policies has three tabs. Register lists your policies with their status, owner and review dates. Add holds the template library, AI drafting and document import. Coverage shows which recommended policies each enabled framework still needs.

Start from the template library

Keel ships a library of 75+ framework-mapped policy templates covering the documents auditors expect: information security, access control, incident response, data retention, business continuity, and more. Pick a template, fill in its templated fields (like your legal company name), tailor the content to how you actually operate, and you have a real policy in minutes.

Draft with AI

Rather start from a description? Name a policy (for example Access Control or Incident Response) and Keel’s AI writes a clean, framework-mapped first draft right in the editor, ready for you to tailor. It’s a starting point you own and edit, never boilerplate you ship blindly. See AI tools & credits for how this is metered.

Import an existing document

Already have policies in Word or as PDFs? Import a .docx (up to 10 MB) or a PDF (up to 5 MB) and Keel turns it into an editable draft. AI cleanup is on by default and has Keel’s AI restructure it into clean Markdown, using AI credits. Untick it to import the text as is. A scanned PDF has no text layer, so import the .docx or paste the text into a new policy instead.

Check coverage against your frameworks

The Coverage tab lists the templates Keel recommends for each framework you have enabled and marks which ones are already in your library, matched by template or by title. Each missing policy has a button that creates it from its template.

Analyze policy gaps asks Keel’s AI to compare your policy set against your primary framework and list the required policies that are missing or too thin. It uses AI credits, and each analysis is saved on the tab so you can come back to it.

Versioning and revision history

Every policy keeps a revision history, so you can see how a document changed over time and who changed it. Versioning matters at audit time: it demonstrates that policies are living documents that get reviewed and updated, not written once and forgotten.

Approvals and review cadence

Route a policy through approval to record that the right owner signed off, then set a review cadence so it comes back around on schedule. A policy register tracks owners, review dates, and coverage gaps across your whole set, so you can spot a missing or overdue policy before an auditor does.

Required readers

Open a policy’s Readers tab to list the people who must read it and confirm they have. Paste emails (one per line, or Name <email>), or add every workspace member or everyone in your people directory at once.

Once the policy is approved, each reader is emailed a link that opens the policy with no Keel login. They tick a box and select Acknowledge. Keel records which version they acknowledged and when, and files the acknowledgement as evidence linked to your policy acknowledgement controls.

When you approve a new major version, every reader goes back to pending and is emailed the new version straight away. A minor version does not ask anyone to acknowledge again. Readers who are still pending get a reminder once a week while the policy stays approved, and Send links to pending sends one now. Each new email replaces the previous link, and a link expires after 60 days.

Export to PDF

When a policy is ready, export it as a branded, auditor-ready PDF straight from Keel. Share it with auditors, customers, or your team, or surface approved policies on your Trust Center.

Next steps

• AI tools & credits: drafting, import cleanup, and policy-gap analysis.
• Trust Center: publish policy names and documents to prospects.