Use reminder messages before and after due dates

Send short, time-bound reminders shortly before and after due dates so willing taxpayers do not slide into late payment by default. Reminder routines are cheap, visible, and often generate one of the fastest compliance gains.

• Many taxpayers mean to pay but leave it too late.

• Phone or digital contact data exist for a reasonable share of taxpayers.

• Management wants a low-cost, quick compliance lift.

• A basic list of unpaid accounts and a way to send messages or letters in batches.

• Simple, legally safe message templates with consistent wording.

• Do not over-message taxpayers if the city cannot suppress reminders once people pay.

• This is weak where contact data are too thin to make reminders meaningful.

Most compliance reforms rise or fall on consistency. Taxpayers quickly notice whether the city applies the rule across the roll or only in selected cases.

The full card would help the city plan the reminder calendar, the message tone at each stage, the stop rules once payment arrives, and the data fields needed for low-cost bulk reminders.

• Make sure bills actually reach taxpayers

• Apply late-payment penalties consistently.

A reminder system is often the cheapest and fastest way to improve compliance among taxpayers who are willing to pay but late by habit, oversight, or poor timing. It works best when it is predictable, timed around the due date, and linked to real account status so paid accounts stop receiving messages. Good reminder practice also prepares the ground for later escalation: taxpayers can see that the city gave clear, repeated notice before adding penalties or using stronger tools.

• Many taxpayers appear willing but pay late or only after repeated prompting.

• The city has usable phone numbers, email addresses, or other contact channels for a meaningful share of the roll.

• Management wants an early compliance gain that does not require heavy legal or operational change.

• Start with a small, repeatable reminder calendar rather than an elaborate communications strategy that staff cannot maintain.

• If account suppression is weak, begin with one or two reminder stages only, so the city does not send repeated messages to taxpayers who have already paid.

• Use the first round to test which channels actually reach taxpayers rather than assuming the cheapest channel will be the most effective.

• Which reminder stages matter most in your context: before the due date, just after it, or both.

• How the tone should change from friendly prompt to firmer overdue message without sounding erratic or threatening.

• Whether reminders should be uniform or adapted for different groups such as large debtors, installment-plan taxpayers, or recently corrected accounts.

First 90 days

• Choose a simple calendar, such as one message shortly before the due date and one or two shortly after it.

• Prepare short templates in plain language and make sure they match the amounts, due dates, and payment channels shown on the bill.

• Set a basic stop rule so messages cease once a payment posts or a taxpayer enters an approved payment plan.

6 to 12 months

• Run the reminder sequence for one cycle and monitor delivery, response, and complaint rates.

• Adjust timing and wording based on which messages appear to trigger payment and which only trigger confusion.

• Link the reminders to the help desk so staff can handle the predictable increase in routine questions.

12 to 24 months and beyond

• Embed the reminder calendar into routine billing operations rather than leaving it as an ad hoc communication activity.

• Refine the taxpayer segments and stop rules as the data improve, so reminders become more targeted over time.

• Use reminder results to decide which accounts need only low-cost nudges and which should move more quickly into formal overdue follow-up.

• Confirm that the city is authorised to use the chosen messaging channels for tax administration and that privacy obligations are met.

• Where bulk SMS or email is outsourced, set simple contractual rules for message security, timing, and data use.

• Ensure the reminder content does not imply enforcement steps that the city is not yet ready or authorised to apply.

• The city needs a current list of unpaid accounts and a reliable way to suppress reminders once payment arrives.

• Someone must own the calendar, message templates, and day-to-day sending process; reminder systems fail when they are nobody’s core job.

• Help-desk staff need the same scripts and dates that appear in the reminders so the taxpayer journey feels coherent.

• Poor stop rules can undermine trust quickly because taxpayers resent receiving reminders after they have already paid.

• Too many messages can feel like harassment and create political pushback; fewer, better-timed reminders are usually stronger than constant contact.

• If reminders reference the wrong amount or wrong deadline, they amplify rather than reduce confusion.

• Delivery rate of reminders by channel.

• Payment rate after each reminder stage.

• Number of complaints about repeated or inaccurate reminders.

• Share of paid accounts that still received a message because suppression failed.

• Make sure bills actually reach taxpayers.

• Apply late-payment penalties consistently.

• Show taxpayers where the money goes.

• What is the smallest reminder sequence the city can run reliably every cycle?

• Which channels have enough coverage to matter without creating major extra cost?

• How will the city stop reminders once payment posts?

• Who will review reminder performance and change the calendar if response is weak?

• B. Make payment easy and trustworthy