Approval reminders should notify staff about work that is still pending and avoid repeating the same message after retries. Bind each reminder to a defined occurrence and check current decision state before sending.
Reminders are separate business effects
A reminder is an external notification about a pending approval, not a new approval request. Its identity should distinguish the proposal and reminder occurrence while preserving one logical send across retries.
For a proposed scheduler, define reminder times, recipient scope, channel, maximum count, and expiry behaviour. Store occurrence state durably. A restarted scheduler should discover whether a reminder was already submitted rather than regenerate it from scratch.
Do not assume a failed notification response means nothing was delivered. The sending provider may have accepted the message before the response was lost. Use its supported duplicate protection or reconciliation and document any remaining limit.
Test a fictional approval completed near reminder time
A manager approves a request at 10:00 while the scheduled reminder worker wakes. The worker must check the current decision and avoid sending a message that still asks for approval if the request is already resolved under the defined timing policy.
Now simulate a notification timeout after provider acceptance. The retry should preserve the reminder identity. Creating a new identity on each execution defeats the duplicate guard.
| Reminder fixture | Required behaviour |
|---|---|
| Request still pending | Eligible scheduled reminder |
| Approved before send checkpoint | Suppress stale reminder |
| Request expired | No continuing reminder series |
| Same scheduler occurrence repeated | One logical notification |
| Recipient loses approval role | Apply current routing and permission policy |
Inspect the actual message sink and approval state. A scheduler ledger with one row is not enough if two external messages were accepted before that row was updated.
Avoid notification fatigue
Choose cadence from the work’s urgency and staff coverage. Escalation should move responsibility through the approved process rather than repeatedly broadcasting the same vague request. Include a clear action link and safe proposal context.
More frequent reminders may reduce waiting but increase interruptions and stale messages. Measure time to decision, reminder usefulness, and unresolved age. A high message count is not evidence that the approval process works.
This reminder design is proposed. The voice integration case study describes related workflow experience. Pair it with safe approval expiry and duplicate email prevention.
Approval reminder FAQ
Should a retry create another reminder occurrence?
No. Retry the same logical occurrence under its documented sending policy.
Can reminders continue after approval?
Not as requests for the resolved decision. Check current state and define any separate completion notification explicitly.
What should happen when nobody responds?
Follow the approved escalation or expiry policy rather than extending reminders indefinitely.