Business Listing Through Data-Sharing and Street Verification

Build or refresh the business list by combining what the municipality already knows with what partner agencies, utilities, market managers, or local associations know, then verify quickly in the street. In many cities this is more accurate and cheaper than starting a citywide sweep from zero. It is especially useful where businesses already appear in fragmented lists but not in the licensing register.

• Other offices or partners already hold partial business information, such as permit lists, market registers, utility records, or inspection records.

• Business activity is concentrated enough that short verification visits are practical.

• Staff can manage basic matching in Excel or another simple system.

The city should be able to receive and use non-sensitive data for local revenue administration. If needed, this is often handled through simple data-sharing agreements or MoUs.

Assign a liaison in each relevant office, define a short matching rule, and keep a log of every new business added, corrected, or rejected after verification.

• Partner data are too weak to be useful.

• Politics or institutional conflict make data-sharing unrealistic in the short term.

Where possible, show partner agencies that cleaner local business data also helps their own operational work.

Build or refresh the business list by combining what the municipality already knows with what partner agencies, utilities, market managers, or local associations know, then verify quickly in the street. In many cities this is more accurate and cheaper than starting a citywide sweep from zero. It is especially useful where businesses already appear in fragmented lists but not in the licensing register.

• Map the best existing data sources, such as permit files, market lists, utility records, inspector notebooks, and association lists, and agree a basic data-sharing cycle.

• Run simple matching to identify likely missing businesses, duplicates, and obvious address or activity errors before field visits begin.

• Send small verification teams to confirm only the uncertain cases so that staff effort is focused where the data are weakest.

• Add, correct, or close accounts immediately after verification and keep a source log so the process can be repeated every quarter or every half year.

The city should be able to receive and use non-sensitive data for local revenue administration. If needed, this is often handled through simple data-sharing agreements or MoUs.

Assign a liaison in each relevant office, define a short matching rule, and keep a log of every new business added, corrected, or rejected after verification.

• Other offices or partners already hold partial business information, such as permit lists, market registers, utility records, or inspection records.

• Business activity is concentrated enough that short verification visits are practical.

• Staff can manage basic matching in Excel or another simple system.

• Partner data are too weak to be useful.

• Politics or institutional conflict make data-sharing unrealistic in the short term.

• Keep the first contact proportionate. A coverage reform should widen the licensing base, not feel like a surprise enforcement raid on small operators.

• Log the date and source of each new or corrected account so the city can challenge duplicates, disputes, and informal side deals later.

• Where possible, show partner agencies that cleaner local business data also helps their own operational work.