Backgrounds
Current architectural plans and reflected ceiling plans in DWG or RVT, with the issue date.
Approach
A disciplined, standards-driven process.
The discomfort of hiring a remote designer is the unknown of how the work gets managed. Here’s how — five phases, deliverable-by-deliverable, with the standard cited.
Discovery to closeout.
01
Discovery & Requirements
A two-call kickoff. We collect drawings, schedules, and the client's standards. We come back with a fixed proposal and a clear list of unknowns to chase.
02
Schematic / Design Development
Block diagrams, room programming, equipment counts, preliminary pathway routing. Reviewed with the project team before we lock geometry.
03
Construction Documents & BOM
Full drawing set: cover sheet, plans, risers, elevations, details, specifications. Bill of materials with manufacturer SKUs and quantities the GC can issue for bid.
04
Review / QA
Internal redline, then a separate QA pass against a BICSI/TIA checklist and the project criteria. Every finding is logged and closed before issue.
05
Construction Administration & Closeout
RFI response, submittal review, bulletin revisions, change-order technical review, live video walks with the on-site team, punch-list, and review of test results and closeout records.
Standards we design to
The reference shelf.
Packages can include a standards-traceability index that ties design decisions to the governing reference. Editions are confirmed against the publisher’s catalog and the project specification at kickoff.
BICSI TDMM (current edition)ANSI/TIA-568 seriesANSI/TIA-568.3-EANSI/TIA-569ANSI/TIA-606-DANSI/TIA-607-EANSI/TIA-758ANSI/TIA-942NEC Articles 770 / 800NFPA 72 (interfaces)NFPA 99 (healthcare)ISO/IEC 11801NESC
Tools we work in
The drafting stack.
We adapt to your team’s stack. These are the platforms we work in; tell us yours at kickoff and we’ll confirm the fit.
AutoCADRevitBluebeam RevuNavisworksBIM 360 / ACCProcoreSharePoint / TeamsVisioMicrosoft ProjectSmartsheet
What we ask for at kickoff.
Most rework starts with a missing or outdated input. These are collected and logged before design starts; anything that isn't available yet becomes a tracked open item.
Owner criteria
Technology standards, outlet and room criteria, preferred products, and labeling conventions.
Your standards
Title block, sheet numbering, layer or family standards, and specification format.
Existing conditions
Prior record drawings, photos, survey notes, or a named on-site contact for field verification.
Schedule
Milestone dates, review rounds, and the date each deliverable must be ready for your QA.
Responsibility
Who designs, reviews, signs, seals (if required), and issues each part of the package.
How a package stays controlled from first input to closeout.
Telecom packages pass through a lot of hands. These controls keep the drawings, specifications, and decisions in step, whether the work is a full design or overflow production for your team.
Source control
Backgrounds and client inputs are logged by date and version, and superseded files are retired, so the design is never drawn on stale information.
Assumptions & decisions
Open assumptions and design decisions are recorded with who made them and when, then closed before issue.
Drawing register
Each sheet and spec section carries a status and revision, so both teams see the same picture of the package.
Milestone QC
Before each issue: completeness, sheet-to-sheet consistency, drawing-to-spec agreement, and the project criteria.
Redline closure
Every review comment is answered or incorporated and tracked to closure, not lost between rounds.
Revisions & transmittals
Revision blocks and clouds identify what changed; transmittals record what was issued, to whom, and for what purpose.
See the pre-issue QA checklist for the kind of checks run before a package goes out, or how this works for A/E overflow support.
How an off-site RCDD stays embedded in your team.
The objection people don't quite say out loud, answered point-by-point.
Scheduled around your tempo
We set a coordination cadence and response windows that match your construction schedule, so remote never means out of reach.
Version-controlled files
Your approved platform -- such as SharePoint, BIM 360 / ACC, or Procore -- or an agreed project workspace. Every drawing carries a revision block and every change is logged. Controlled information is accepted only after the contract and handling requirements are confirmed.
Comms cadence
Coordination meetings, communication channels, and written response windows are matched to the schedule and defined in the proposal. You always know where the package is.
Credential sign-off
RCDD review and electronic sign-off identify the responsible ICT designer, date, and revision. This is not a state-issued PE seal; where the AHJ or contract requires one, the responsibility boundary and PE coordination are defined in the scope.
Want to walk through our SOP for your project type?
A 30-minute call. Bring the project. We'll walk you through how we'd run it.