Make the due-date register trustworthy before making messages automatic. Use this proposed sequence:
- Create a register linking customer, site, asset, service type, due date and evidence for that date.
- Separate an agreed contract visit from an invitation to buy another service.
- Confirm the correct recipient—occupier, landlord, managing agent or commercial contact.
- Put missing dates, conflicting records and disputed obligations into a manual queue.
- Choose reminder windows appropriate to the contract and scheduling process.
- Generate a task or approved message only for records passing the checks.
- Stop reminders when the visit is booked, the customer declines, the record is disputed or the relevant communication preference changes.
- Reconcile the appointment with completed work before advancing the next due date.
A proposed starting schedule could be 30 days and seven days before the recorded due date, but that is a configurable office policy—not a statement of a legal inspection interval.
Do not let an AI-generated message claim that an asset is compliant merely because a reminder was sent or a visit was booked. For domestic gas work, HSE explicitly distinguishes servicing from the contents of a gas safety check; the two should not be treated as interchangeable records. (hse.gov.uk)
Apply the service-message versus marketing distinction to renewal wording. An administrative notice and a promotional renewal campaign are not automatically the same thing. (ico.org.uk)
Stage exit: The office can trace each reminder to the correct asset, recipient and source date.
Sources cited on this page
- hse.gov.uk ↗www.hse.gov.uk
- ico.org.uk ↗ico.org.uk