State → County → City picker

Three linked dropdowns for when the rep knows the area but not the spelling.

What it is

A cascading filter built from the same static index. Picking a state draws the state border and lists its counties; picking a county runs the county lookup and lists that county's cities; picking a city runs the city lookup. Counties that hold verified data show a '✓ data' hint.

Also called: browse permit rules · pick a county · permit filter

See it
State → County → City picker
Day rate
$500
Days figured
5
Crew size
4
Fuel & equipment
$300
Finished 2 days early — $1,800 back to the crew
The Filter row: three branded Selects (State / County / City) with a Reset link. PermitCheckPanel.tsx, stateOptions / countyOptions / cityOptions. Sample data — no customer information appears here.
How it works
  1. 1State options are derived from the counties and cities in the index
  2. 2County options filter to the chosen state and carry a '✓ data' hint when data exists
  3. 3City options filter to the chosen state and county
  4. 4Selecting a state alone draws just the state border and shows a state explainer card
  5. 5Reset clears the search, the filters, the answer, the borders and the pin
Why we built it

Free-text search fails on spelling ('St.' vs 'Saint' is handled explicitly in the boundary lookup) and on reps who know the region rather than the parcel. The state card also carries the standing truth of this domain: post-frame permits 'are issued at the county or city level — there's no single statewide permit.'

The problem
  • A misspelled place name returns nothing
  • The rep cannot see which areas are covered
Sound familiar?
What you get
Coverage is visible before you search
No dead-end search on a spelling

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →