Last updated: 2026-04-25
Expiry alerts
Anchorlet sends a daily email when any compliance record in your workspace is exactly 60, 30, or 7 days from expiring. The email summarises which property + type + expiry date for each item that hit one of those thresholds today.
How it works
A daily cron runs at 8am UTC (around 09:00 Dublin in summer, 08:00 in winter). For each workspace:
- Anchorlet runs three queries — records expiring in exactly 60, 30, and 7 days.
- If any of those buckets have items AND the workspace owner has compliance alerts enabled, an email is sent.
- A row is logged so duplicate cron firings don't double-send.
You'll get one email per day at most — not three separate emails for the three thresholds.
Why "exactly" 60 / 30 / 7
The thresholds are step-functions, not ranges. A cert that expires in 31 days won't trigger a 30-day alert today; it'll trigger one tomorrow. This is deliberate — it means each cert generates at most three alerts (one each at 60, 30, 7 days) over its lifecycle, not 60+ daily reminders. If you miss the 30-day alert, you'll still get the 7-day one.
Turning it off
Settings → Preferences → Compliance expiry email alerts → toggle off.
It defaults to on for all users. Toggling off only affects your account — other workspace members keep getting alerts on their own preference.
What the email looks like
- Brand-A logo at the top.
- Three sections (only the buckets with items appear): Expiring in 7 days (red), Expiring in 30 days (orange), Expiring in 60 days (amber).
- Each section is a small table: property, cert type, expiry date.
- "Open compliance dashboard →" button at the bottom.
- "Manage email preferences" link in the footer.
Subject line
Anchorlet: 3 compliance items need attention this week — the count includes everything across all three buckets.
What the email doesn't do
- It doesn't try to renew the cert for you. You still need to book the assessor / electrician / engineer.
- It doesn't remind you about LPT (Local Property Tax) — that's a separate feature on the property compliance tab with its own alert schedule.
- It doesn't surface the legacy
ber_certsorrtb_registrationsrows from the older per-type tables. If a record was added via the legacy UI, migrate it to the new compliance tab to get covered.