Platform

How do recurring tasks drive compliance health in Acuna GRC?

Direct answer

In Acuna GRC, recurring tasks repeat weekly, monthly, quarterly or annually, pinned to weekdays or a day of the month, and completing one creates the next occurrence, due from the completion date. Each completion records who did it and when and lets you link or create a record on the spot.

Tasks linked to controls are how the work gets done, and their completion feeds health, which rolls up through controls and measures to requirements and risks. A missed task therefore shows as a gap above it, not only in a task list. The Annual Plan shows the year's recurring tasks and scheduled controls on one 12-month grid.

Why do recurring tasks matter for compliance?

Most controls are not done once. Access reviews, backup restore tests, supplier reviews and log checks have to happen at a set frequency, and an auditor will ask to see that they did. A SOC 2 Type 2 report gives an opinion on whether controls operated effectively throughout a period, not on a single day, and ISO/IEC 27001:2022 requires the results of monitoring and measurement to be kept as evidence (clause 9.1).

A recurring task is the unit of that work: a named action, with an owner and a due date, that comes back on schedule and leaves a trace each time. If the task is tied to the control it serves, its completion is also the signal that the control is operating.

How do you set up a recurring task in Acuna GRC?

A task repeats weekly, monthly, quarterly or annually, pinned to weekdays or a day of the month. You give it an assignee, link it to the controls and requirements it serves, and it takes its place on the Tasks page in Operate.

You do not have to write every task yourself. Add from repository adopts the curated Acuna GRC task templates, filtered to the frameworks in your programme, one or many at once, and each arrives pre-linked to the requirements it fulfils. Aiko can also draft a task from a sentence that names the work, the due date and the person, as a proposal for you to confirm.

Tasks show in a sortable table or a kanban board. My Tasks shows only yours, and filters cover Overdue, Due this week, Due this month and No due date, as well as the framework. You can comment on a task and share it with a colleague.

What happens when a recurring task is completed?

Done records who did the work and when, and lets you link or create a typed, dated record on the spot. Dragging a card to Done on the board opens the panel, so the step is not skipped. See how evidence lifecycle works.

Completing the task then creates the next occurrence, due from the completion date. If a quarterly review is done two weeks late, the next one is due a quarter after that, so the interval between two checks stays what the control says it is.

The completion also feeds health. Health starts at the control, from whether it ran on time and from its tasks, and rolls up through measures to requirements, and through treatment plans to risks. See how control health works.

How does a missed task show up, and what goes wrong most often?

A missed task shows in more than one place. It is overdue on the Tasks page and in its assignee’s My Tasks, it is an unfilled occurrence on the Annual Plan, and it lowers the health of the control above it and of every measure and requirement linked to that control. A gap in the routine therefore shows as a gap in compliance, where the compliance lead will see it.

Common mistakes:

  • Tasks not linked to a control, so their completion proves nothing about any requirement.
  • Completions with no record attached.
  • Recurring work assigned to a team mailbox rather than a person or a role.
  • One task per framework for the same check, which splits the proof.
  • Frequencies copied from a template without asking whether they match the risk.

The Annual Plan shows the year’s recurring tasks and scheduled controls on one grid, with planned and completed occurrences marked. See what a compliance calendar is.

How Acuna GRC handles it

Sources

  1. ISO/IEC 27001:2022, clause 9.1
  2. AICPA & CIMA, SOC 2 (System and Organization Controls)
  3. Acuna GRC, Operate workspace

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

Frequently asked

Do recurring tasks sync with Jira or ServiceNow?

Task sync with a ticketing tool (Jira, ServiceNow, Freshservice, TOPdesk or GLPI) keeps tasks and tickets in step in both directions, but closed and recurring tasks are never sent out to the ticketing tool.

Can another system complete tasks through the API?

Yes. Where the API is enabled for your organisation, API v1 can create, update and complete tasks, under the read and write scopes given to its key.

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