Controlkeep for small IT and security teams: keep controls current between audits

Small IT teams can track control owners, review cycles and expiring evidence in one register, and hand auditors a control matrix and a JSON bundle.

Use case · Updated · by the Controlkeep team

For a small IT or security team, the hard part of compliance isn't the first audit; it's the year after. Owners change, evidence goes stale, policies are revised and nobody re-collects acknowledgements. Controlkeep keeps the register current between audits, so the next one starts from a live record instead of last year's spreadsheet.

The register as a working tool

Each control has an owner, a status, a "not applicable" justification where relevant, a review cycle, mapped evidence and related policies. Use a starter framework (SOC 2-style or ISO 27001-style, written in our own words and not the official text of either standard) or your own controls. The register replaces the usual tangle of a control spreadsheet, a shared drive of evidence and an email thread of policy sign-offs.

Review cycles that come back round

Set a review cycle per control, for example every 90 days for user access, yearly for vendor reviews. A weekly email to workspace owners lists reviews that are overdue, evidence that expires within 30 days and policies due for review, and control owners get their own list. A control that hasn't been looked at shows up before an auditor finds it.

Evidence that stays fresh

  • Upload PDF, PNG, JPG, TXT, CSV, DOCX or XLSX up to 10 MB. Files are checked by content, not just extension, so renamed files are rejected.
  • Add links (a ticket, a dashboard) and written notes as evidence too.
  • Map one item to all the controls it supports, so a quarterly access review attaches once and covers several controls.
  • Set expiry dates on certificates, pen-test reports and other time-bound evidence.

Don't upload passwords, keys or personal data you don't need, and redact screenshots. The evidence help article covers the details.

Policies with versions and acknowledgements

Policies are Markdown documents with versions. Each change is a draft; an owner or admin approves it, which supersedes the previous version and asks every member to acknowledge the new one, with a reminder after 7 days. Each policy has a review frequency, and its next review date appears in the reminders when it's near.

Audit-ready exports

  • Control matrix CSV: one row per control with status, justification, owner, review dates and evidence.
  • JSON audit bundle (owners and admins): frameworks, readiness, controls, evidence metadata with SHA-256 hashes, mappings, policies with every version and acknowledgement, members and the audit log.

The hashes make it clear exactly which file was provided. Evidence file contents download individually. See audit exports.

Roles

Owners and admins approve policies, manage the team and download the audit bundle. Members own controls, upload evidence and acknowledge policies. Every important action is in the audit log, which is itself part of the export.

Plans

FreePro ($199/month excl. VAT)
Controls501,000
Evidence storage100 MB5 GB
Team members325
Included AI policy tailoring (fair use)2 a day, 10 a month10 a day

Team members include pending invitations. At a limit, the action is blocked with a message; there are no overage charges.

The limits of any register

Controlkeep records what your team says and shows. It doesn't scan your systems, enforce settings, or decide whether a control is effective. A readiness percentage is your own measure of progress, not an audit result. Pair the register with a qualified auditor's judgement.

Starting from an existing spreadsheet

Most teams already have a control list somewhere. Add a starter framework, compare it with your spreadsheet, and add your own controls for anything specific to you. Then move evidence over control by control as each one comes up for review, rather than all at once.

A quarterly routine

  1. Clear the overdue reviews.
  2. Replace evidence that expired or will expire this quarter.
  3. Re-approve any policy that changed and chase acknowledgements.
  4. Export the control matrix and compare it with last quarter's.

Try Controlkeep free

A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.