Distinguishing sent reminders from verified responses

Tag the outbound reminder

When a reminder email or message is sent, add a system‑generated tag "Reminder sent" with the timestamp and channel (email, SMS, printed note). Do not change the credential’s status — it stays "Current", "Expiring soon", or "Expired" as before.

Capture the verified response

When the employee or trainer replies with a concrete action — attached renewal certificate, confirmed course date, or written statement that renewal is in progress — add a second tag "Response verified" with the date, responder name, and a one‑sentence summary. Attach the reply or the new certificate.

Worked example — OSHA 10 renewal

Before: Lena Fischer – OSHA 10 – Expires in 51 days – Status: Current Day 1 (60‑day offset): Reminder sent via email. Tag added: "Reminder sent 2026-03-14 email". Day 10: Lena replies with a screenshot of her enrollment confirmation for a 2026-04-20 class. Tag added: "Response verified 2026-03-24 Lena – enrolled 2026-04-20". Attachment: lena_osha_enroll.png. After: The record shows both tags. A filter for "Reminder sent" AND NOT "Response verified" now excludes Lena, so she does not receive the 30‑day notice.

Exception — automated acknowledgment only

If the only reply is an auto‑reply or a generic "Got it" without evidence of renewal action, do not add "Response verified". Keep the credential in the pending‑response view until a substantive update arrives.

Result: The dashboard cleanly separates credentials that have only been nudged from those with confirmed progress, preventing duplicate reminders and giving supervisors a true picture of renewal momentum.

Related: Cert Expiry Tracker features.