Where Pane's data comes from.
Official city and county records, organized by address, with the source attached. Here's what's in them, how often they update and where Pane has coverage.
Sources
Pane collects code enforcement records directly from the cities and counties that publish them, and resident complaints (311 requests) where the city publishes those too.
Pane keeps the city's own dates and statuses. Where a city doesn't publish something, Pane says so. It doesn't estimate or fill the gap.
What each record includes
| Field | Notes |
|---|---|
| Address | Matched to the property you sent |
| Record type | Violation or complaint |
| Filed date | The city's own date |
| Status | The city's own status: open, in progress or closed |
| Category and description | As the city records them |
| Recommended action | Pane's plain-language next step, where available |
| Fines and amount paid | Where the city publishes them |
| City record link | Where available |
See the fields in context in the sample report.
How often it updates
Pane checks for new records as often as each city publishes them. Cities publish on their own schedules, so this varies by market. Each city's coverage page shows the date of its latest record, and a city that stops publishing is marked as paused.
Coverage
The coverage page lists the states, cities and counties open to address search, with each one's current status.
For a portfolio, send your list and Pane tells you which addresses it covers before you commit to anything. Ask about markets that aren't listed.
How you get it
Send addresses by spreadsheet, CSV or API. Results come back in the Pane app, with a PDF for each report. Monitored properties stay in the app, and Pane tells you when a city files something new.
Your data
Pane reports on properties, not people. Our Privacy Policy explains how we handle the addresses and information you send.