Put routine coverage audits on the calendar

Schedule small, regular checks—such as hotspot audits, permit-to-roll checks, and imagery reviews—so that coverage does not decay after a one-off campaign. This protects earlier gains and is usually cheaper than repeatedly rebuilding the roll from scratch.

• The city has already improved the roll and now needs to keep it current.

• Growth is steady enough that the register drifts if nothing is checked routinely.

• Management can commit to a recurring calendar and small annual budget.

• A simple audit plan, ownership of follow-up actions, and a place to record corrections.

• At least one source of update evidence, such as field checks, permits, or imagery.

• This is not the first move if the underlying register is still badly incomplete.

• Routine audits add little value if there is no process to absorb and act on findings.

The political risk is usually low to moderate, but the city still needs to show that new records will be handled fairly and that residents are not being drawn into a process they do not understand.

The full card would help the city plan a repeatable audit rhythm, the hotspots to review, the minimum evidence to collect, and the staffing and budget needed to keep coverage from slipping.

• Use imagery to spot new buildings and extensions

• Give each property one ID in one register

• Link the roll to permits, sales, and new service connections.

Coverage declines quietly when the city treats maintenance as something that will happen informally. Routine audits give the administration a calendar, a budget logic, and a leadership checkpoint. They also make it easier to protect the gains from more intensive discovery work without having to repeat a major survey every few years.

Create a repeating audit rhythm so the city periodically checks whether the register is drifting out of date and corrects it before losses become large again.

A city that has already made some improvement in coverage and now needs a practical maintenance cycle that leadership can budget for and supervise.

A first scheduled audit cycle in priority areas, with a concrete list of additions and corrections rather than a vague commitment to keep the roll current.

Adopt an affordable audit rhythm and assign a small team to own it, rather than leaving maintenance to good intentions.

Revenue administration with mapping, field, and possibly partner-data support.

• The city has already widened the register but has no predictable method for keeping it current.

• Growth or densification is continuing, even if not everywhere.

• Leadership prefers a manageable recurring task over occasional large clean-up drives.

• Choose a realistic cycle and scope, such as annual hotspot checks or a two- to three-year rotation.

• Decide how the audit will combine desk review, imagery, partner data, and field follow-up.

• Create a clear workflow from audit finding to register correction.

• Set the unit of review: hotspot, ward, growth corridor, or rotating citywide sample.

• Decide which audit methods are most cost-effective for the city’s context.

• Choose how results will be reported to management so the cycle remains visible and funded.

First 90 days

• Approve the first audit calendar and define the team responsible.

• Select the first geography or risk areas and assemble the relevant existing data.

• Document the update and reporting process so the audit produces action rather than only findings.

6 to 12 months

• Run the first audit cycle and process the additions and corrections it reveals.

• Compare the audit yield across different methods or geographies.

• Use the first results to refine the next cycle and to justify budget provision.

12 to 24 months and beyond

• Embed the audit routine in the normal budget and annual workplan.

• Link the audit cycle to imagery review, trigger data, or field checks where useful.

• Use repeat cycles to spot where the city still needs deeper reforms rather than only maintenance.

• Most cities can start this administratively, though partner-data access or field-verification authority may need clarifying.

• The main legal need is often not a new law but clear internal authorisation and documented procedures.

• A small cross-functional team is usually more effective than a large one with weak ownership.

• The city needs simple reporting discipline so audit findings do not disappear into routine workload.

• Maintenance is easier when the register already has stable IDs and usable location references.

• Audit cycles that are too ambitious quickly collapse into missed deadlines and declining credibility.

• Findings can accumulate without action if update capacity is weak.

• If management never reviews the results, the audit becomes a ritual rather than a maintenance tool.

• Whether the audit cycle was completed on schedule.

• Number of additions and corrections identified and processed.

• Lag between identification of an issue and update of the register.

• Change in coverage quality in the audited areas over successive cycles.

• This card reinforces PT-COV-04 on imagery, PT-COV-08 on event triggers, and PT-COV-10 on citizen-reported changes. Together these cards create a maintenance system rather than a one-off clean-up.

• What audit cycle can the city actually sustain every year or every two to three years?

• Which areas should be checked first and why?

• Who will follow through on audit findings once they are identified?

• How will leadership know whether the cycle is working?