PE Stamp and License Verification in Oregon

These links are provided as starting points to the official state sources. A board's current instructions and online record control; confirm the page, status, discipline, and authorization directly before a project submission.

• Oregon engineering licensing board
• Official license verification or lookup
• Project code and AHJ requirements for Oregon
• Responsible engineer and scope confirmation

The Oregon board resource does not approve a design or transfer responsibility to a contractor, owner, or another engineer. The responsible professional reviews the project inputs, code basis, calculations, drawings, and existing conditions, then determines which documents can be signed or sealed. Oregon enforces a mandatory statewide code through the Building Codes Division (BCD); local jurisdictions cannot amend it, giving Oregon one of the most uniform code environments in the country. The OSSC is updated on the state's own cycle from the IBC base. Oregon licenses PEs by comity for qualified out-of-state applicants and accepts electronic seals; the state applies specific rules on seal and signature requirements for digital submittals.

A Oregon PE may need the project address, current architectural backgrounds, discipline scope, adopted code information, site and existing-condition evidence, equipment data, calculations, AHJ checklist, and any correction notice. Oregon's uniform statewide code makes plan review consistent across jurisdictions, though metro Portland and Washington County (Hillsboro's Silicon Forest) run high-volume review. Stormwater is a defining permitting issue — Portland's on-site infiltration and green-infrastructure requirements are among the strictest in the country — and Cascadia seismic detailing is expected on essential facilities. Mild, wet marine climate west of the Cascades with modest cooling loads; Heavy rainfall driving stormwater and moisture/envelope detailing; Cold, dry high-desert climate east of the Cascades; Growing summer peak-cooling needs and wildfire-smoke filtration are examples of why project inputs must be confirmed rather than assumed.