Docs/Records, Defects, and Renewals

Renewal Lifecycle and Reminders

The renewal lifecycle keeps compliance current with automatic next-due dates and escalating reminder emails.

For: Owners and office teams3 min read3 sections

Renewal timeline

Walk the reminder tiers that keep compliance current without anyone remembering.

60 days beforeFirst reminder to the landlord or letting agent; plenty of time to book.
30 days beforeSecond reminder; the property appears on the due-soon tile.
7 days beforeUrgent reminder; schedule the check now to avoid lapsing.
OverdueEscalated reminder; the property moves to the overdue tile until a new record is generated.

Renewal Functions

  • Generating a CP12 best-effort books next year’s check, on the same engineer, so the cycle continues.
  • Compliance status rolls up as Valid, Due soon, Overdue or Action required, and shows Unknown until a first record exists.
  • Due-soon and overdue worklist tiles surface on the dashboard.
  • A daily job sends escalating reminders as the due date approaches and passes.

Reminder Tiers

Two thresholds are at work here, and they are deliberately different. Email reminders begin at 60 days, but the dashboard “Due soon” tile only starts at 30 days, so a property can receive a 60-day reminder email while it still reads Valid on the dashboard (a satisfactory, in-date record). This is by design: the emails give landlords early notice, while the tile reflects nearer-term operational urgency. The two line up again from 30 days onward.

  • Email reminders escalate at 60, 30, and 7 days before due, then again once overdue, sent once per tier so a tier never repeats.
  • The dashboard “Due soon” tile (and the due-soon compliance status) appears at 30 days, not 60, so between 60 and 30 days a property may be emailed yet still show Valid.
  • The landlord or letting agent is emailed; a property with no client uses the occupier’s email instead. There is no push notification, though the office bell gets an alert when a property turns Due soon or Overdue.
  • Renewal reminders are on by default (the switch is under Settings, then Notifications) so compliance does not depend on memory. A new CP12 resets the sent tiers, and a renewal.due webhook fires when a property turns Due soon or Overdue.
  • Tenant delivery of the record happens within the statutory 28-day window via a secure link.

Troubleshooting

  • Reminder not sent: confirm reminders are enabled and the recipient contact details are present.
  • Emailed but still shows Valid: expected between 60 and 30 days. The first emails precede the dashboard “Due soon” tile, which starts at 30 days.
  • Next check not created: only a CP12 books it, and it is skipped when the property already has an open check; schedule manually if it did not run.
  • Property shows overdue unexpectedly: confirm the last record date and the renewal window.

Make Compliance Self-Chasing

The renewal lifecycle exists so compliance does not depend on someone remembering. Generating a CP12 schedules the next check, status rolls up to the dashboard, and reminders escalate automatically.

  • Confirm renewal reminders are enabled and recipients are correct before relying on them.
  • Use the due-soon and overdue tiles as the daily worklist for protecting compliance.
  • Deliver records to tenants within the statutory 28-day window.
  • Treat action-required outcomes as remedial work to plan, not just a status to display.

Was this page useful?

Previous

Defects: At Risk, Immediately Dangerous, and NCS

Next

Records Delivery