A closer look at deadline reminders in Read & Confirm for Confluence — including the Reset workflow

[#1]

Hi everyone,

Two weeks ago we shipped configurable deadline reminders for Read & Confirm for Confluence. Now that the feature has been in use for a bit, I wanted to walk through how the pieces fit together — especially the Reset operation, which addresses a workflow most policy owners run into eventually.

The basics

Each confirmation request has two reminder slots, defaulting to 7 days and 1 day before the deadline. From the request detail page, the creator can:

• Edit the timing (any integer from 1 to 365 days before the deadline)
• Disable either slot independently
• Reset an already-sent reminder so it can fire again

Reminders go out as a single footer comment per request that @mentions every user still pending — so a 30-person review doesn't flood the comment thread with 30 separate notifications.

The Reset workflow — why it exists

Here's the scenario it solves:

Your security team publishes an updated VPN policy. You create a confirmation request with a 30-day deadline. The 7-day reminder fires on schedule. Halfway through, legal asks for a clause change. You update the page — but the people who haven't confirmed yet won't get a fresh nudge, because their reminder is already "sent."

That's where Reset comes in. Open the Reminders dialog, click Reset on the slot that already fired, and it becomes eligible again. The next time daysUntil === daysBefore, it goes out as a new footer comment to everyone still pending.

In short:

• Normal cycle: each slot fires at most once → no accidental double-sending
• Manual intervention: creator explicitly resets → reminder re-arms

Other use cases for Reset

• Deadline was extended and you want a fresh round of reminders
• The original reminder hit a quiet day (e.g., a public holiday) and didn't get the attention it deserved
• A page has been republished after major revisions, and you want acknowledgments aligned to the new version

Why footer comments + mention

We deliberately built reminders on top of Confluence's existing mention infrastructure rather than creating a separate notification channel:

• Users already trust mention — mute, follow, and email rules all work as-is
• Notifications stay attached to the document
• Data never leaves your Atlassian environment (Forge-native, no external storage)

If you've started using the feature, I'd love to hear:

• Are two reminder slots enough for your workflows?
• Has Reset come up in practice? In what scenarios?

Marketplace listing: https://marketplace.atlassian.com/apps/1138072457/read-confirm-for-confluence