A permit record establishes what an issuing jurisdiction filed for a defined permit type and status. It does not establish that every improvement occurred, that work is complete, or that the retained history is exhaustive.
Read the permit as a jurisdictional filing
| Field | Value / state | Reading |
|---|---|---|
| Issuing jurisdiction | City, county or authority | The system that owns the record |
| Permit type | Building · electrical · site · other | Scope is defined by the filing |
| Filing date | Date submitted or issued | Do not substitute observation date |
| Status | Applied · issued · finaled · expired | Status vocabulary varies |
| Retained history | The window the system exposes | Older activity may not be visible |
| Filed | Permit type | Status | Issuing jurisdiction |
|---|---|---|---|
| 2019-04-11 | Building — shell | Finaled | City of Dallas |
| 2021-09-02 | Tenant improvement | Finaled | City of Dallas |
| 2023-06-27 | Electrical | Issued | City of Dallas |
| 2025-02-14 | Roof replacement | Applied | City of Dallas |
Nothing filed before the retained window is visible here. Absence in this table is not evidence that no work occurred.
Synthetic product demonstration. It shows a research pattern, not a live record or completeness claim.
Limitations that change the next question
- A permit feed can be partial or limited to one issuing jurisdiction.
- A finaled permit does not replace an inspection of the official record.
- No permit observed is not proof that no work occurred.
- Permit data does not provide tenant, lease, rent or operating information.
Use activity without overstating it
Tie each activity observation to its property key, permit type, filing date and status. If the source only exposes an official link, keep the link state instead of manufacturing a normalized event.
For diligence, compare permit history with parcel configuration, assessment changes and recorded instruments. A mismatch is a research question, not an automatic conclusion.