PE Stamp and License Verification in Tennessee

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.

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

The Tennessee 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. Tennessee's State Fire Marshal's Office adopts a statewide commercial building code — currently based on the 2018 IBC — that applies where local governments have not adopted their own. Larger cities like Nashville, Memphis, and Knoxville administer local building departments and may enforce their own adopted editions and amendments. Tennessee grants licensure by comity for qualified out-of-state PEs and requires a Certificate of Authorization for firms. Electronic seals are accepted per board rules.

A Tennessee 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. Tennessee's statewide code baseline provides predictability, but Nashville, Memphis, and Knoxville run active local building departments with their own review timelines and amendments. Nashville's sustained growth has stretched review capacity, while Memphis-area projects add New Madrid seismic scrutiny and Mississippi-corridor floodplain requirements. Genuine four-season climate with both cooling and heating loads; Humid summers requiring latent-load management; New Madrid seismic influence in West Tennessee; Heavy rainfall and river-corridor flood exposure are examples of why project inputs must be confirmed rather than assumed.