Use a clear overdue notice ladder

Adopt a staged overdue process—reminder, formal demand, final notice—so that taxpayers get clear warnings and the administration builds a defensible path to stronger action. This is one of the simplest ways to make enforcement feel fair and consistent.

• Arrears follow-up is ad hoc or too informal.

• The city wants stronger enforcement without jumping straight to harsh measures.

• There is a need to document due process before penalties or legal action.

• Clear templates, timelines, and rules on when an account moves to the next stage.

• A way to record that each notice was sent or delivered.

• Do not rely on notice escalation if bills themselves are not reaching taxpayers.

• This adds little if staff ignore the timetable and do not follow through.

The city normally gets the best results when it can show that ordinary taxpayers had a fair chance to pay before penalties or stronger action began. Consistency matters more than drama.

The full card would help the city plan the notice templates, timing, delivery proof, escalation rules, and the hand-off from soft reminders to formal enforcement.

• Make sure bills actually reach taxpayers

• Apply late-payment penalties consistently.

A good overdue process gives taxpayers several clear chances to respond and gives the administration a defensible route from soft follow-up to stronger action. That matters both operationally and politically. When notices escalate in a predictable order, the city can show that it acted fairly and consistently before adding charges or using heavier enforcement tools. The key is not the number of letters; it is the discipline of moving accounts through the same sequence every cycle.

• Arrears follow-up is ad hoc, inconsistent, or too informal.

• The city wants to strengthen compliance without jumping straight to highly coercive measures.

• There is a need to document due process before penalties, field visits, liens, or court-linked action.

• Make the first ladder short and realistic; a sequence that staff can complete is stronger than a long one they cannot sustain.

• If proof of delivery is weak, build that into the notice design and record-keeping from the beginning.

• Link the ladder to actual account status so paid accounts stop moving forward automatically.

• How many stages the ladder should contain and what each stage is meant to achieve.

• Which channels will be used at each stage, and when stronger proof of delivery becomes necessary.

• When an account should move out of the notice ladder and into penalties, field follow-up, or stronger enforcement.

First 90 days

• Draft the reminder, formal demand, and final notice templates in plain language and make the consequences of inaction clear.

• Set the timetable for each stage and align it with billing dates, reminder messages, and penalty triggers.

• Create a simple log so the city can see which accounts are at which stage and what proof exists.

6 to 12 months

• Pilot the ladder on a manageable set of overdue accounts and check whether the timing and wording produce responses.

• Refine the hand-off points between each stage so staff are not improvising on difficult cases.

• Train frontline staff and managers on what each notice means and what action should follow.

12 to 24 months and beyond

• Embed the ladder into routine arrears management and stop relying on ad hoc personal judgment for common cases.

• Use the weekly arrears report to see where accounts are getting stuck and whether notice stages need adjustment.

• Periodically review whether the ladder is still proportionate once other tools such as payment plans or clearances mature.

• Confirm that notice periods, content requirements, and methods of service align with local law or regulations.

• Clarify whether each stage is an administrative notice only or whether some steps carry specific legal effect for later enforcement.

• Where third parties deliver final notices, define proof and custody responsibilities clearly.

• The city needs reliable account status, current contact data, and a way to stop escalation after payment or correction.

• Notice templates, logs, and proof of delivery should be standardised across offices.

• Managers must monitor whether cases are actually moving through the ladder and not stalling after the first notice.

• If the city sends warnings but fails to follow through, compliance can worsen because taxpayers learn the ladder is not serious.

• If the wording is overly threatening too early, the city may generate political resistance without gaining extra payment.

• If notices reference the wrong amount or wrong channel, they can strengthen taxpayer resistance rather than compliance.

• Number and share of overdue accounts at each notice stage.

• Payment or contact rate after each stage.

• Share of final notices with usable proof of delivery.

• Average time accounts spend in the ladder before resolution or escalation.

• Make sure bills actually reach taxpayers.

• Apply late-payment penalties consistently.

• Visit major defaulters in person.

• What are the minimum stages the city can apply consistently every cycle?

• At which point does the city need stronger proof of delivery?

• Who decides when an account moves from notices into stronger action?

• What will the city do if large numbers of accounts stall at one stage?