PE Stamp and License Verification in California

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.

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

The California 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. California enforces a statewide code through Title 24, published by the Building Standards Commission on a three-year cycle. The 2025 edition took effect statewide January 1, 2026, with local jurisdictions permitted to adopt more stringent amendments based on local conditions. California requires additional state-specific exams in seismic principles and engineering surveying for civil PE licensure, and issues separate structural engineer (SE) authority for certain buildings. Electronic seals are accepted; comity is available but not automatic.

A California 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. California permitting is layered: local building departments enforce Title 24, while CEQA environmental review and coastal, fire, and air-district agencies can add parallel tracks. Plan review timelines vary widely — large coastal cities can run long, while inland jurisdictions and third-party plan-check services move faster. Extreme climate diversity — coastal marine to high desert to alpine; Cooling-dominated Central Valley with 100°F+ summers; Strict all-electric and demand-response utility pressures; Wildfire smoke intrusion driving filtration in the WUI are examples of why project inputs must be confirmed rather than assumed.