Start with the permit number and the record era. Pima County’s current permit-status guide defines Approved, Issued and Final as different stages and warns that permits before 2013 may use other statuses. Preserve older wording instead of translating it automatically.
Read the three current labels as separate events
| Displayed label | What the County says it records | What to look for next |
|---|---|---|
| Approved | Staff approved an application that meets County ordinances and codes. | Find the later issue record. |
| Issued | Fees paid; permit issued for construction. | Keep its date and inspect the later events. |
| Final | All inspections passed and permit requirements were completed. | Match the result to the same permit. |
Treat each row as its own dated event. One row cannot substitute for another, and an entry on one permit cannot close a separate trade permit, prove occupancy approval, or describe current building condition.
The statuses that come before Approved
Approved, Issued and Final are the end of the line. The same County page lists five earlier review statuses, and a permit stuck in one of them tells you the project never reached construction approval:
- ADM REV (Administrative Review): the County is checking that all required documents were submitted.
- DEFICNT (Deficient): the applicant was told to submit missing documents.
- SUB REV (Substantive Review): the County is checking the plans against its ordinances and codes for that permit type.
- PLANRFAI: the substantive review found errors or omissions and the plans went back for corrections or more information.
- DENIED: the plans reached the maximum number of re-reviews under the County’s SOP 220.0 and weren’t approvable. The applicant would need a new application with new fees, so look for a second permit number for the same project.
An old permit that still shows PLANRFAI or DEFICNT never reached approval on that record; it doesn’t show that work was authorized. If the building exists anyway, that gap is the question to take to the County.
Use the permit number to anchor the record era
The County’s status guide explains the year code with its own example: P14CP0001 was the first “CP” permit issued in 2014. Read a number in three parts: the year (14), the permit type letters (CP) and the sequence (0001). Record the full number, displayed wording, date and source system before comparing an older file with a newer one.
Build a compact reconciliation card:
- Identity: permit number, address or parcel used to confirm the record, and issuing jurisdiction.
- Era: year code and the system or file where the label appears.
- Event: exact wording, displayed date and any linked inspection or document number.
- Gap: the later event or underlying file that has not been found.
This card prevents a modern definition from silently replacing older wording. It also shows whether two screens concern the same permit or merely the same site.
Diagnose a fictional old-and-new mismatch
Imagine a fictional folder in which P12CP-OLD carries Approved and P24CP-NEW carries Issued. A separate inspection entry refers only to the newer number. None of these invented records can be merged just because they share an address.
First, keep each number and entry on its own line. Next, attach the inspection only to the number it names. Then list the missing bridge: perhaps a later document for the older file, an inspection result for the newer one, or the record that explains the legacy wording. The gap is a named record question, not a reason to upgrade either file.
If a later file arrives, compare its permit number, date and issuing office with the card. Keep a mismatched response as a separate clue. Ask which document connects the two identifiers rather than assuming the newer file completes the older permit history.
If the response contains an inspection sheet instead of the requested decision, compare its title, number, date and source with the gap row. Keep an unrelated response separately. Record whether the target was not located, was inaccessible, or was simply not part of the response; those outcomes require different follow-up questions. Do not rename the supplied file to make it fit the timeline.
Request the missing file instead of guessing
Pima County’s building-records page sends Development Services requests through Permit Gateway and requires an account. It says to verify jurisdiction and submit one address per request. For an applicable Certificate of Occupancy request, include the permit activity or suite number.
Name the object you need: an underlying permit, inspection result, occupancy document or explanation for a specified number. Include the displayed wording and approximate date as locating context. This route is for an identified missing file; it does not promise that every historical document remains available or that staff will map old terms to new ones.
For the broader address, jurisdiction and archive sequence, use the Pima County permit-search guide. If the missing piece is an approved plan set rather than a status, the Pima project drawings guide explains why a document search can miss it. To evaluate an inspection outcome after locating the right permit, use the final-inspection status guide.
A portal entry alone does not prove that all work at the site was permitted, that every related file reached its last stage, or that occupancy approval was issued.
Pima County permit-status guide checked October 20, 2026.