Resend a compliance notification email
Resend an existing notification using its retained log and linked record context.
Before you start
Compliance View opens the workspace; Create is used for new intake, Edit for review/approval and Delete for deletion. Each action also validates its record.
Follow these steps
- Go to the notification log and review the original recipients and subject.
- Verify the record is still current for the same stage.
- Use Resend Email only when a resend is operationally justified.
- Check the updated send status and timestamp.
- Avoid repeated resends when delivery failure requires an address correction instead.
Fields, rules and limits
- Review the recipient delivery ledger before repeating a run. A record or PDF may already exist even when one recipient failed. Retry the failed delivery rather than creating a duplicate compliance record.
Check it worked
The linked entity, saved state, dates and evidence match the intended task.
If something does not look right
If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.
Questions and answers
Does a parsed document count as approved?
No. Parsing supplies suggested values. A reviewer must verify the linked entity, evidence and required fields, then use the separate approval action.
Is the generated PDF the original certificate?
No. The system PDF reflects the saved compliance record or notification. Open the original source evidence separately when checking the document supplied.