The three objections to remote ICT design, answered

Stamping, coordination, and site presence. Where the objections are real and where they are inherited from an older workflow.

Remote-first ICT design draws the same three objections almost every time: who stamps it, how does coordination work, and what about site presence. Two of the three are answerable with process. The third is a real constraint worth naming honestly.

Objection one: stamping

A credentialed sign-off does not require the designer to be in the building. The RCDD seal commits the responsible party to the design shown, applied against the BICSI and TIA reference set. What matters is a clear responsible-party block, revision history, and an AHJ that accepts an electronic seal — none of which depend on physical proximity.

Objection two: coordination

Coordination with electrical, structural, and architectural disciplines is a documentation and cadence problem, not a presence problem. A shared model, a regular coordination call, and disciplined RFI handling close the loop. In many cases a remote designer with a structured cadence coordinates more reliably than an on-site one working from memory.

Objection three: site presence

This one is real, and the honest answer is a division of labor, not a plane ticket. Routine observation belongs to the team already on the site — the general contractor or a local representative working a written checklist. For the moments that genuinely benefit from the designer’s eyes — a pre-rough-in walk, a punch list, a tricky pathway condition — we run a scheduled live video walk with the on-site team, captured against the drawing set, so what was seen and what was decided is on the record. A remote practice names those touchpoints up front instead of treating presence as the default.