What 'RCDD-certified design' actually commits the designer to
Clients ask for it. Few teams agree on what it means. A plain-language explainer for contractors and design firms.
The conversation usually starts the same way. A specification asks for “RCDD-stamped drawings” and the team scrambles to figure out what that actually requires. The question gets passed from the prime to the integrator to the cabling subcontractor, and somewhere along the way the answer gets fuzzy. It is worth slowing down and saying clearly what the credential does and does not do.
What the credential actually does
The RCDD is a credentialed sign-off — not a state-issued professional engineering license. It commits the stamping party, by reputation and by BICSI standing, to having designed, reviewed, or supervised the design of the work shown on the drawing. It does not confer the authority to stamp electrical-engineering or structural drawings.
Documentation practices for ICT design follow the BICSI TDMM and TIA-606. Treat the responsible-party block, revision history, and electronic-seal handling as part of the deliverable, not an afterthought.
In practice, a few things follow when a reviewer sees an RCDD seal on a deliverable. The package is read against the BICSI and TIA reference set rather than reinvented from first principles. Coordination with electrical and structural is presumed to have been considered. And the responsible party carries a continuing-education obligation that is checkable.
What it does not do
It does not substitute for a PE where the authority having jurisdiction asks for one. It does not absolve the general contractor of construction-administration responsibility. And it does not preempt the project-specific specification when the spec is tighter than the standard.
Three things to confirm before you commit to RCDD-stamped on a bid
- Confirm the AHJ accepts an electronic seal — the local building department is the final word.
- Decide whether the stamping party is on your team or the integrator's, and get it in writing in the teaming agreement.
- Make sure both the design package and the as-built package carry the seal, with revision history intact.
None of this is exotic. But it gets fumbled often enough that it is worth settling early. Get the credentialed designer on the team at the start, name the responsible party, and the “who stamps this” question stops being a source of schedule risk.
Principal of ICT Design Partners, a focused, remote-first ICT design, QA, and white-label practice for contractors and design firms.
About the firm