PermitLens
Search. Prove. Follow up.
Scope pilot
Coverage

Show what was checked before the team trusts the result.

Source coverage belongs in plain view. People need to know what returned rows, what came back empty, and what is not covered yet.

01

Track county feeds and municipal adapter status

02

Expose coverage freshness directly in the UI

03

Make rollout gaps visible instead of tribal knowledge

Prove Source Coverage screen from the PermitLens application.
What this surface needs to answer

Was this source checked, and can the team trust the result?

When this page works, the team knows what data can be trusted before the follow-up moves forward.

read only
Miami-Dade County permits

Primary source for permit number, address, type, owner or contractor details, issue date, and last inspection fields.

read only
Miami-Dade County inspections

Feeds the inspections screen with permit number, inspector, request date, sequence, and disposition.

reference
Municipality reference

Useful for jurisdiction labels and code mapping, but not a live municipal permit feed.

Coverage

Prove Source Coverage

Permit teams do not just need a result. They need proof that the right records were checked before the next handoff.

PermitLens coverage model

  • County feeds where public records are available
  • Municipal adapters where a city source needs separate coverage
  • Empty, failed, missing, and not-applicable source states shown honestly

The product requirement

Teams should see source coverage and freshness directly in the app.

If there is ambiguity about what was checked, the workflow turns back into a screenshot and a guess.

Keep going

Source coverage should map to the pilot's real risk.

Use the demo to see the product shape. Reach out when you want to talk through which South Florida sources and public-record layers matter first.

Open demo Scope pilot