Understand staged compliance notifications
Interpret advance, due and overdue notice stages without sending duplicate messages.
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 active notification chain for the record.
- Check the previous stage and send timestamp.
- Verify the record remains active and the expiry date has not changed.
- Check whether a renewal submission already exists.
- Allow the next supported stage to run only when its conditions are still true.
Fields, rules and limits
- The scheduled notification service evaluates 90-, 60-, 30-, 14- and 7-day notices and the expired stage. It keeps delivery state per recipient and prevents duplicate stage/recipient sends. Changed dates and renewal state can affect what is due.
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.