Shift-, Route-, and Site-Level Dashboards

Build a simple dashboard, even in Excel, showing expected versus actual collections by market, route, parking zone, bus stand, or shift. High-frequency streams need close operational visibility because leakage is dispersed and difficult to see from headline totals alone. A dashboard helps supervisors spot which site or shift has become abnormal and direct follow-up where it matters most.

• The city has many small collection points.

• Leadership cannot tell where leakage is arising.

• Supervisors want easier comparisons across sites or shifts but currently work from raw receipts only.

No special legal reform is normally needed beyond the city’s standard authority for internal reporting.

Use consistent site codes, ensure data entry is regular, and name one officer or supervisor who owns the dashboard and the follow-up discussion around it.

• Source data are too weak or too delayed to make site-level comparisons meaningful.

Build a simple dashboard, even in Excel, showing expected versus actual collections by market, route, parking zone, bus stand, or shift. High-frequency streams need close operational visibility because leakage is dispersed and difficult to see from headline totals alone. A dashboard helps supervisors spot which site or shift has become abnormal and direct follow-up where it matters most.

• Decide the minimum dashboard fields, such as site, shift, collector, expected amount, actual amount, variance, and unusual events.

• Produce the dashboard at a rhythm managers can really use, often daily for large sites and weekly for smaller ones.

• Use the dashboard to trigger operational questions, such as why one route consistently underperforms or why one shift generates unusually many voids.

• Keep the first version simple and stable so staff actually trust and use it.

No special legal reform is normally needed beyond the city’s standard authority for internal reporting.

Use consistent site codes, ensure data entry is regular, and name one officer or supervisor who owns the dashboard and the follow-up discussion around it.

• The city has many small collection points.

• Leadership cannot tell where leakage is arising.

• Supervisors want easier comparisons across sites or shifts but currently work from raw receipts only.

• Source data are too weak or too delayed to make site-level comparisons meaningful.

• The administration cannot yet issue reliable notices, post payments accurately, or distinguish inability to pay from deliberate non-compliance.

• The largest risk is often collector leakage, not unwillingness to pay. Control, reconciliation, and complaint channels should move in parallel with any enforcement changes.

• Sanctions must be visible but proportionate, especially where daily access to a stall, bay, or route is tied closely to livelihood.