Platform

What is a compliance calendar and why does it matter?

Direct answer

A compliance calendar is a structured view of every review, audit, assessment, renewal, and regulatory deadline a compliance program must meet. Organizations running multiple frameworks (ISO 27001, SOC 2, GDPR, NIS2) face dozens of recurring obligations per year, from quarterly internal audits to annual surveillance audits to vendor reviews.

Compliance calendar software consolidates these into one view, tracks ownership, and surfaces what's overdue. Without it, deadlines live in Outlook and on spreadsheets, making missed obligations common.

What belongs in a compliance calendar?

Everything that recurs and has an owner. A typical multi-framework calendar holds:

  • Control operation: access reviews, backup restore tests, vulnerability scans and the other checks each control runs on a set frequency.
  • Document reviews: policies and procedures due for their periodic review.
  • Risk reviews: the yearly review of each approved risk, and the follow-up of treatment plans.
  • Audits: internal audits, certification and surveillance audits, and supplier assessments.
  • Management review and the reporting that feeds it.
  • Privacy dates: processing activities due for review and processor agreements reaching their expiry.

The frameworks set the cadence for some of these. ISO/IEC 27001 requires internal audits at planned intervals (clause 9.2) and a management review at planned intervals (clause 9.3), and the documents of the ISMS have to be kept under control, including their review (clause 7.5). Other dates come from your own policies, contracts and risk decisions.

Who owns the calendar, and how do you build one?

The compliance or security lead usually owns the calendar as a whole, but each entry needs its own owner: the control owner, the document owner, the risk owner or the auditor. A calendar where every line points to the compliance team turns that team into a reminder service.

A practical way to build it:

1. Start from the requirements of each framework in scope and list what has to happen repeatedly to meet them.

2. Merge the overlaps. One quarterly access review can serve ISO 27001, NIS2 and SOC 2 at once, so it should appear once.

3. Give each entry an owner, a frequency and the record that proves it was done.

4. Add the fixed dates: audits, contract renewals, regulatory deadlines.

5. Review the calendar itself when a framework, a scope or a risk decision changes.

How does the Annual Plan work in Acuna GRC?

In Acuna GRC the calendar is built from the work itself rather than typed in separately:

  • Recurring tasks repeat weekly, monthly, quarterly or annually, pinned to weekdays or a day of the month. Completing one creates the next occurrence, due from the completion date, and records who did it with a record attached. See how recurring tasks work.
  • Controls carry their own schedule, and a due control appears in its owner’s My Actions.
  • Approving a risk or publishing a document sets a next review date one year ahead, with reminders 30 days before, 3 days before and once overdue. Confirming the review moves the date forward a year.
  • The Annual Plan lays all of this on one 12-month grid, with planned and completed occurrences marked.
  • Audits are planned in programs with a frequency and dates, and corrective actions remind their owners when due within three days or overdue.
  • Task templates from the curated Acuna GRC repository, filtered to your frameworks, arrive pre-linked to the requirements they fulfil.

Because tasks feed control health, a missed occurrence also shows as a gap on the controls, measures and requirements above it. See the Operate workspace.

What are the common mistakes?

  • One calendar per framework. The same review then appears three times with three owners, or falls between them.
  • Dates without proof. A ticked entry with no record attached will not satisfy an auditor.
  • A calendar separate from the work. Dates kept in a spreadsheet drift away from the controls and documents they refer to.
  • Fixed due dates on recurring work. If the next occurrence ignores when the last one was really done, the interval between checks quietly grows or shrinks.
  • No review of the calendar itself after a scope or framework change.

How Acuna GRC handles it

In Acuna GRC, the Annual Plan is that calendar: a 12-month grid of recurring tasks, scheduled controls and the yearly review of each approved risk and published document, with reminders 30 days and 3 days before a review and once it is overdue.

Sources

  1. ISO/IEC 27001:2022, clauses 7.5, 9.2 and 9.3

This page explains the rules in general terms and is not legal advice.

Frequently asked

Does ISO 27001 require a compliance calendar?

Not by that name. It requires internal audits and management reviews at planned intervals (clauses 9.2 and 9.3) and control of documented information (clause 7.5). A calendar is the usual way to plan and show those intervals.

How far ahead should a compliance calendar look?

A rolling twelve months covers most recurring obligations, from quarterly checks to yearly reviews and audits. Longer cycles, such as a certification cycle, are best tracked as fixed dates in the same view.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US