How Confluence tasks work, and why recurring tasks need a pattern
Before you design Confluence recurring tasks, it helps to be clear about what a single task does. In Confluence Cloud a task (also called an action item) is a checkbox line on a page. You add one by typing /action in the editor, then:
- Assign it with a mention. Type
@and a name inside the task. The assignee gets a notification in Confluence, and an email too if they are subscribed to email notifications. - Give it a date. Add a date to the task line. Once that date passes and the task is still open, it turns red on the page.
- Find it again. Tasks assigned to a person appear in their own Tasks list in Confluence, where they can also tick them off.
- Report on many at once. The task report macro lists tasks from chosen spaces or pages, filtered by label, assignee, creator, creation date and status (complete or incomplete).
That is a solid toolkit for one-off work. The catch is in the word "one-off". A task belongs to one page, it is ticked once, and then it is done. There is no "repeat every month" setting on the task line. If you run a monthly check, next month's task has to come from somewhere: a person, a template, a rule. That "somewhere" is the pattern this article is about.
Patterns to schedule repeating work in Confluence
Most teams combine a few of these.
A template plus a page per period
Write the checklist once as a page template: the steps, a task line for each step, headings for what to record, and a place for attachments. Each period, someone creates a new page from the template under a parent page for that activity. Space templates are created by space admins, so agree on the content before you ask for one.
A naming convention
Give every period's page a predictable title, such as Firewall review 2026-Q4 or Scan review 2026-10. Year first sorts cleanly, makes search results obvious and makes a missing month easy to spot in the page tree.
A schedule page
One page lists every recurring item in a table: what it is, how often it runs, who owns it, who covers for them, the next due date and a link to the latest period's page. This is the page people check when they wonder "what is due this month?", and the page you update when someone changes roles.
An owner per item
Every recurring item needs one named owner, not a team. Teams don't create pages; people do. Add a backup for holidays and leavers.
Calendar reminders
A reminder a few days before each period starts ("create the October scan review page") is what keeps the pattern alive. Team calendars in Confluence, which can send email reminders by event type, come with Premium and Enterprise plans. On other plans, a repeating event in your normal work calendar does the same job.
Confluence automation
Confluence automation has a scheduled trigger and an action that publishes a new page in a chosen space, under a chosen parent, optionally from a template. Put a date in the title so each run gets a unique name. That turns "someone remembers to create the page" into a rule. How many rule runs you get each month depends on your plan, so check your usage allowance before you build many of these.
Jira recurring work items, if you use Jira
If your team already lives in Jira, Jira Cloud can set a work item to recur: open it, choose Set to recur from the automation menu or the due date field, and pick a schedule, optionally based on whether the last copy was completed. Each copy carries over the fields but not attachments or links, and the runs count toward your automation usage. It is a good fit for the reminder and the to-do; keep the record of what was checked on a Confluence page and link the two.
| Pattern | What it solves | What it doesn't |
|---|---|---|
| Template + page per period | Consistent content every time | Someone still has to create the page |
| Naming convention | Gaps are visible in the page tree | Nobody is told about the gap |
| Schedule page | One view of owners and due dates | It goes stale unless someone maintains it |
| Calendar reminder | A nudge before each period | Tied to one person's calendar |
| Confluence automation | Pages created on time | No view of what is late or skipped |
| Jira recurring work item | A fresh to-do each period | The evidence lives elsewhere |
A worked example: a monthly recurring checklist in Confluence
Say you review vulnerability scan results every month. The monthly scan review guide covers what the review itself involves; here is how to set up the recurring checklist by hand.
- Create a parent page called
Vulnerability scan reviews. It holds the procedure and one child page per month. - Create the template. Ask a space admin for a template with: the month, the scan date, a task line for each step (export results, triage critical and high findings, open tickets, confirm last month's fixes), a heading for decisions and a heading for attachments.
- Agree on the title format:
Scan review YYYY-MM. - Add the item to your schedule page with its owner, backup and "due on the last day of the month".
- Add a label such as
scan-reviewto each month's page, and put a task report on the parent page filtered by that label and by incomplete tasks, so open steps from every month show in one place. - Set the reminder. A repeating calendar event on the 20th of each month for the owner, or an automation rule that publishes the new month's page from the template.
- Each month, the owner creates (or opens) the page, assigns the tasks to themselves, attaches the export, ticks the tasks and writes a one-line conclusion.
Run like this, the page tree becomes your evidence: one dated page per month, each showing who did the work and what they found.
What tends to break in a hand-built recurring checklist
The setup above works well for a few months. These are the failures that show up later, usually when someone asks to see a full year.
- Nobody creates next month's page. The reminder lands during a holiday, a release or a busy week, and the month is quietly missing. The naming convention shows the gap, but only to someone who looks.
- The owner leaves. Their calendar reminder leaves with them, open tasks stay assigned to them, and the schedule page still names them. Nothing tells anyone that the item has no owner.
- Skipped periods leave no record. Sometimes a period genuinely doesn't apply: the system was out of scope, or the quarter's review was merged into another. If nobody writes that down at the time, a skip and a miss look identical a year later.
- Overdue is invisible. A red task on one page is easy to miss. There is no single place that says "three checks are late across the space" unless someone builds and maintains it.
- A ticked box isn't sign-off. Ticking tasks shows the owner thinks they are done. If someone else is supposed to review the result, that review needs its own record, and the page can still change after it.
Tip: if you skip a period, still create its page and write why it was skipped, who decided and when. An explained gap is evidence; an unexplained one is a question.
For compliance work these failures matter more than usual, because an auditor typically samples periods across the year and asks for proof of each. The SOC 2 compliance calendar lists the recurring controls a typical program runs and how often.
Recurring compliance activities with Compliance in a Box
Compliance in a Box is a Confluence Cloud app that runs a SOC 2 program in one dedicated Confluence space. Its recurring activities are built for exactly the controls described above: a ready-made set of 15, such as the monthly vulnerability scan review, the quarterly user access review and the annual penetration test. The recurring activities chapter of the user guide has the details.
A schedule per activity
Each activity runs Monthly, Quarterly, Semi-annual or Annual, with periods aligned to your fiscal year and each due on its last day. A Compliance Admin can change it with Edit schedule, which previews the next periods before saving. Every change is kept as a new schedule version in the audit log. See how schedules work.
A dated evidence page before each period
Ahead of each due date (14 days by default, adjustable from 0 to 90), the app creates the period's evidence page under the activity page, titled with the activity and the period. It starts with the due date, a checklist of what to provide and a heading for each item. Only the activity owner and Compliance Admins can edit it, and when the owner changes, those edit rights move to the new owner.
An owner and approvers
The owner fills in the page and selects Submit for approval. The submission is tied to that exact page version, and the period is approved once every approver has approved it. Editing the page before approval cancels the submission, so the approval always matches what the approvers saw.
Reminders as Confluence tasks
Reminders are ordinary Confluence tasks, assigned to the person on their own private Compliance tasks page in the compliance space, so Confluence itself notifies them. Owners are reminded when the period's evidence page opens, 3 days before the due date, and then once a week after it if the period is overdue. Approvers are reminded about submissions waiting for them. See how reminders work.
Overdue in plain sight
A period that isn't approved or skipped by its due date becomes Overdue. The Activities tab counts every overdue period per activity, the Dashboard shows overdue items across the program, and each owner sees their unfinished periods in My Tasks. If an owner's account is deactivated, the Dashboard lists what they held so an admin can reassign it.
Skips with a reason
When a period legitimately doesn't need doing, a Compliance Admin selects Skip and fills in Why is it skipped?. The period is closed, never counts as overdue, and the reason and who skipped it are kept for the auditor. See skip a period.
For how activities fit with policies and acknowledgements in the same space, see running a SOC 2 program in Confluence.
FAQ
Can a Confluence task repeat on its own?
A task belongs to one page and is completed once. To repeat the work, create a new page (and with it new tasks) each period, by hand from a template or with an automation rule that publishes the page on a schedule.
How do people get notified about Confluence tasks?
When you assign a task by mentioning someone, they get a Confluence notification, plus an email if they are subscribed. Overdue tasks turn red on the page. If you want people chased before or after a due date, plan that yourself with a calendar reminder or an automation rule.
Should recurring checklists live in Confluence or Jira?
Either can hold the to-do. Confluence is usually the better home for the record, because one page holds the checklist, the findings and the attachments. Many teams use a Jira recurring work item as the reminder and link it to the Confluence page.
How do I show that a recurring check ran every period?
Keep one dated page per period with who did the work, when, what they found and any attachments, plus a written reason for every skipped period. Your auditor decides which periods to sample, so every period should be complete.