Make sure bills actually reach taxpayers

Use a practical mix of digital delivery and hand delivery so that taxpayers actually receive their bills. A city cannot credibly enforce or penalise non-payment if large numbers of taxpayers never got a notice in the first place.

• The city hears frequent claims that bills never arrived.

• Digital access is mixed, so one channel alone is not enough.

• The administration wants a fairer basis for reminders and enforcement.

• Recognition of the chosen notice channels and a simple dispatch plan.

• A way to log undelivered notices and feed corrections back into the register.

• Do not rely only on digital delivery where phone or email data are weak.

• This will not solve deeper data problems if names and addresses are consistently wrong.

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 right delivery mix, the route or dispatch logic, proof-of-delivery rules, and the follow-up process for undelivered bills.

• Use reminder messages before and after due dates

• Fix basic record errors quickly

• Use a clear overdue notice ladder.

Fair collection starts with credible notice. If a large share of taxpayers never receives a bill, late-payment penalties and stronger enforcement will look arbitrary, even when the city is legally in the right. A practical delivery system therefore matters almost as much as the bill itself. In many cities the best answer is not one channel but a mix: digital delivery where contacts are strong, plus physical delivery or local collection points where they are not.

• The city hears frequent claims that bills never arrived or arrived too late to act on.

• Digital access is uneven, so a purely electronic approach would leave important groups out.

• Management wants a cleaner and fairer basis for reminders, penalties, and enforcement.

• Begin by identifying the strongest available delivery channels for each part of the city rather than assuming one channel can serve everyone.

• If addresses and contact details are weak, combine delivery reform with a simple process for capturing corrections during the cycle.

• Create one dispatch log from the start so the city can see what was sent, what bounced, and what still requires follow-up.

• How much of the roll should receive digital notices, and when a paper or hand-delivered notice remains necessary.

• What counts as acceptable proof of delivery for different channels, especially before stronger enforcement steps.

• Whether ward staff, contracted couriers, postal services, or revenue officers should handle physical delivery in different areas.

First 90 days

• Map the current delivery routes and identify where bills fail most often: wrong contacts, late printing, weak dispatch, or weak proof of delivery.

• Clean the easiest contact fields first, especially phone numbers and the addresses of high-value accounts.

• Draft a simple hybrid delivery plan that states which channel will be used for which taxpayer groups and how exceptions will be logged.

6 to 12 months

• Pilot the delivery mix in a limited geography and track what share of notices arrive successfully through each channel.

• Train delivery staff or local counter staff on what information to capture when a notice is undeliverable or a taxpayer offers corrected details.

• Create a standing loop for undelivered notices so corrections feed back into the register instead of remaining in field notebooks.

12 to 24 months and beyond

• Move the hybrid process into routine operations and budget for repeat delivery rather than treating it as a one-off campaign.

• Use delivery data to refine the citywide mix, for example by increasing digital dispatch where contacts prove reliable and reducing wasted paper runs where they do not.

• Link proof of delivery and undelivered cases directly to the overdue notice ladder so escalation is based on real information.

• Confirm which delivery channels are legally recognised today and whether digital notices need an explicit local rule or administrative instruction.

• If delivery is contracted out or delegated to ward teams, set clear responsibility for data protection, proof of delivery, and handling of returned notices.

• Where security or access is sensitive, agree in advance how field teams will identify themselves and how residents can verify legitimacy.

• A practical dispatch owner is essential; delivery usually fails when printing, dispatch, and follow-up sit in separate teams with no single manager.

• The city needs a simple way to merge contact corrections from delivery back into the operational register.

• If physical delivery is used, local route knowledge matters as much as formal maps, especially in settlements with weak addressing.

• Over-reliance on one channel can exclude major taxpayer groups; the first design should be deliberately hybrid where access is mixed.

• If proof-of-delivery rules are vague, the city may think it has given notice when it has not, weakening later enforcement.

• If undelivered cases are logged but never corrected, the city will repeat the same failure every billing cycle.

• Share of bills successfully delivered by each channel.

• Number and share of undelivered notices that are corrected and resent.

• Time from bill generation to completed dispatch.

• Share of enforcement-stage accounts with usable proof that notice was sent.

• Send bills people can understand.

• Use reminder messages before and after due dates.

• Use a clear overdue notice ladder.

• Which parts of the city need a physical channel even if digital delivery expands?

• What proof of delivery will the city rely on before escalating to penalties or stronger action?

• Who will own the undelivered log and make sure corrections are actually used?

• How will the city explain legitimate delivery channels so taxpayers can distinguish them from informal collectors?