Field notes
When zone coverage looks fine but request density says otherwise
Many on-demand operators feel covered when a map shows at least one provider inside each zone. Service request density by hour often disagrees. A zone can look staffed at 10 a.m. and still miss the 5–7 p.m. band when most booking requests arrive.
Density is simply requests per hour inside a zone, optionally weighted by average job length. Overlay that with available provider-hours in the same window. Where density rises and available hours stay flat, acceptance may still look healthy while assignment lag grows—customers wait after the “accepted” confirmation.
In Malaysian cities, school-run corridors and evening residential pockets often diverge from commercial lunch peaks. Treating the city as one average flattens those differences. When we map zones for clients, we ask for district or postcode labels that match how they already schedule people, not an abstract grid invented for the report.
If your zone labels are inconsistent, fix that before commissioning a full Pattern Review. Otherwise the map will reflect filing habits more than real demand.