A lead_permit_lookups row per lookup, holding the input address, geocoded point, matched county and place FIPS, whether the point was inside city limits, the matched jurisdiction id, the full JSON snapshot of the answer, and who ran it. Re-opening the card replays that snapshot exactly rather than recomputing it.
Also called: permit audit trail · what did we check · permit lookup history · who checked the permit
- 1resolve() calls api.recordLookup after the answer renders
- 2org_id and looked_up_by are stamped SERVER-SIDE; any client-supplied org_id is ignored
- 3On mount, latestForOpportunities returns the newest row and restoreLookup redraws the pin and borders from it
- 4Nothing is written back during a restore — 'A recorded lookup is the answer a quote was based on, so it is REPLAYED, never recomputed'
- 5The auto-check pass never re-answers a card that already has a recorded lookup
The panel comment: 'It is the answer a quote was based on and must not drift.' The API comment adds the reason a re-run is refused: 'Never redo one that exists — a recorded lookup is a FROZEN snapshot and silently replacing it would lose the answer the quote was based on.' And on attribution, when nobody ran it: 'Recording a user here would be a lie about who checked, and "who checked" is the point of the audit trail.'
- A rule that changes later makes an old quote look negligent
- Nobody can say whether the permit was checked at all
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 →