A batched server pass that finds pipeline cards with an address but no recorded lookup, resolves their city/state/county against the jurisdictions table (no geocoding), records a frozen snapshot for each, and returns only what it newly wrote so the board can paint the new badges.
Also called: permit check runs itself · automatic jurisdiction lookup · permit check on board load
- 1The board collects the visible sales card ids and calls action:'latest' in one request
- 2Cards with no lookup are passed to action:'auto' (capped at 200 ids)
- 3Existing lookups are excluded first so a frozen snapshot is never replaced
- 4One jurisdictions read per state involved, then matched in memory — a query per card would be 200 round trips for one board
- 5City name is matched first (city rules govern inside city limits), then county
- 6Cards outside coverage are skipped silently rather than answered wrongly
Quoted in the route: 'if there's an address under the contact, the permit check should be automatic — it should say whether it's the county or the city specifically, on the opportunity card outside the modal.' The route adds why it is free: '🔑 NO GEOCODING… Resolving against that table is exact, free, and works when a maps key doesn't — running a paid geocode per card on every board render would be indefensible.' And the reason it exists at all: 'A permit answer nobody asked for is the most valuable kind: the surprise permit bill turns up AFTER the quote went out.'
- A check that requires someone to remember it does not happen
- Per-card geocoding would make an automatic check too expensive to run
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 →