Telecom drawing stamps & permits, state by state.
“Who can stamp the telecom drawings?” is the question that stalls more ICT packages than any technical issue. This guide covers how the decision works everywhere, plus per-state notes on code adoption and licensing — reviewed and maintained by an RCDD-led design practice.
Read this first
This guide is general orientation, not legal advice. Code adoption, licensing, and what a building department accepts on a telecom package change over time and vary by jurisdiction — the authority having jurisdiction (AHJ) always has the final word. Last reviewed June 2026. Spot something out of date? Tell us — we keep this guide current from real project experience.
Three questions decide who stamps a telecom package.
State pages tell you where to look; these three questions are what the answer always comes down to.
1. What does the AHJ require?
The building department reviewing the permit decides what it accepts. Many accept an RCDD-sealed telecom package for communications scope; some want a licensed PE on anything they review. One phone call before the bid settles it.
2. What scope is on the drawings?
Pure communications scope (pathways, spaces, cabling, telecom rooms) is RCDD territory. The moment the package carries engineering scope — power design, life-safety systems, structural calculations — a licensed PE stamp enters the picture, often alongside the RCDD.
3. What does the contract say?
Owner specifications regularly require an RCDD on the design team regardless of what the AHJ would accept — federal, healthcare, and data-center specs especially. Read Division 27 before pricing the work.
State-by-state notes.
Code adoption pattern, licensing authority, and the stamp questions we hear for each state.
Need a responsible RCDD on the design?
We evaluate the ICT scope, project specification, AHJ, and required PE coordination before defining the deliverable and sign-off boundary.