Start with the approved plans and the exact Portland permit or IVR number. If those plans require tree preservation, find inspection 507 and copy its actual result. A requested or scheduled 507 is not an approved 507. Then look for any later required tree-inspection approval and the separate permit final.
Portland’s Tree Protection and Inspection Information says required fencing and signage must be installed, inspected and approved before ground disturbance. It also says projects do not receive final approval until required tree inspections are approved. Those are different points in the record sequence.
Read the records in order
- Approved-plan applicability. Identify the page, note or condition showing that tree preservation applies to the selected permit. Do not borrow the requirement from another project at the address.
- Inspection 507 result. Find the 507 event for the same permit or IVR number. Preserve the inspection date and exact result, including a correction or reinspection if shown.
- Later required tree approval. Check the plan and inspection history for another required tree inspection or unresolved tree-protection item. A passed 507 does not fill that later gap.
- Permit final. Preserve the applicable final inspection or permit-final record separately. Match its number and scope to the same project.
This sequence prevents a common shortcut: reading an issued permit or a structural inspection as proof that the tree-preservation gate cleared. Each record answers only its own stage.
Choose the route that matches the permit type
The City’s tree-inspection page directs commercial, residential and site-development permits to inspection code 507. Its current IVR code reference also lists 507 under multiple permit families and says 507 must be approved before other inspections when tree preservation is required on the approved plans.
Do not turn that into a universal scheduling rule. Field Issuance Remodel permits route tree inspections through Urban Forestry. Zoning permits use a tree-code inspection before the separate code-compliance final, code 555. Preserve the permit type and follow the route named for it.
A tree-protection requirement can also continue after the first approval. The City says fencing remains until final inspection is approved and that changes to approved tree protection require review. Ask which record documents the stage you need instead of treating the first 507 entry as every later approval.
Retrieve the result, not just the request
The IVR reference says the system can provide inspection results and lists of scheduled inspections using the IVR or permit number. Record which function produced the information. A confirmation number or scheduled date shows that an inspection was requested; it does not supply the inspector’s result.
For each event, keep:
- The complete permit or IVR number and permit type.
- Inspection code and inspection name.
- Requested, scheduled and occurred dates when each is shown.
- Exact result and any correction or reinspection note.
- The approved-plan reference that makes the tree inspection relevant.
- The later tree approval and permit-final record, or the precise missing item.
Use the address to confirm identity, but keep the permit number as the main link. No APN input or public historical coverage period was verified for this inspection lookup.
A fictional scheduled 507 is not an approved 507
Imagine a fictional inspection history for permit PORTLAND-EXAMPLE-A. It shows 507 scheduled for April 8 and a structural inspection approved on April 12. The approved plans require tree preservation, but the history displayed in the folder contains no 507 result.
Do not convert the April 8 schedule into approval because another inspection appears later. Record 507 as scheduled and its result as missing. Ask for the 507 inspection result tied to PORTLAND-EXAMPLE-A and check for a correction or reinspection elsewhere in the same file.
Suppose the missing entry is returned and says 507 approved on April 10. Add that result without declaring the project final. Check whether the plan required a later tree inspection and then locate the separate final record. If a later tree result remains absent, preserve that gap.
The site’s final inspection status guide explains why a requested, partial or discipline-specific inspection cannot substitute for the terminal event. The Portland sequence here adds the local 507 and tree-protection gates.
Request a named missing inspection record
The City’s PPD public-records instructions document lookup by address, IVR number or permit number and a request route for existing PPD records. Use the site’s Portland permit-record guide for the broader system route, then request the exact missing inspection object.
A focused request can identify:
- The permit or IVR number, permit type and property address.
- Inspection 507 and its approximate request or inspection date.
- The exact missing result, correction, reinspection or later tree approval.
- The approved-plan page or condition already held.
- The final record being compared and the systems or sections already checked.
Ask for an existing inspection record, not a new decision about whether the project should pass. The public-record route does not establish that every tree record is online, retained for a stated period or available for release. This review did not open the request portal or submit a request.
A missing 507 result does not prove that no inspection occurred, and an approved 507 does not prove that every tree obligation or the permit final was approved. State the permit, inspection code, result, date and remaining gap without extending the conclusion to present tree condition or all work at the property.
Last checked October 6, 2026 (2026-10-06 UTC). Current official inspection guidance and codes were reviewed. No permit, IVR number, property, inspection, account, phone request or records request was entered or submitted.