Pesticide Registry Check
Flag client addresses within 250 ft of a registered notification address

Check a client address

Type the address of a new (or existing) client. We'll geocode it, then flag any registered addresses within 250 feet.

Client address (safe)
Client address (flagged)
Registered address within 250 ft
Other registered addresses

Batch check addresses from a CSV

Upload any CSV or Excel file with a column named Address (or Job Address), plus City, State, and ZIP. Every row is geocoded and checked against the registry. Results are downloadable as CSV or Excel.

📤
Click or drop a CSV / XLSX here
Max 10,000 rows per run

Run a report on your current client list

Loading…

Notifications log

Every email and text notification you've sent through the app, for your compliance records. Download the full history anytime.

Registered addresses

The notification registry that every address is checked against.

Settings

Your company info (used in notifications)
Shown to homeowners on every notification you send. Sender Gmail address is the account the email opens from.
Backend API URL
Optional. Set to a deployed Flask backend URL to use server-side geocoding + audit logging. Leave blank for fully-client-side mode.
Geocoding service (client-side mode only)
Census is fastest for US addresses. Nominatim is a polite fallback (1 request/sec).
Flag radius
Colorado Pesticide Applicators' Act defines 250 ft. Change only if local rules differ.
ft
Registry status
Permanently bake in coordinates
After your registry is geocoded once (above), download a pre-geocoded registry.json. Replace the file at data/registry.json in your hosting and re-deploy — future visitors load instantly with no first-time wait.
About
Registry data is geocoded once on first load and cached in your browser (IndexedDB). Nothing is sent to our servers — geocoding requests go directly from your browser to the Census / OpenStreetMap APIs.