Design criteria and responsibility map
Owner requirements, project specifications, applicable standards, system boundaries, design assumptions, field-verification responsibility, and the interfaces another discipline must carry.
Coordinated plans, risers, telecom rooms, rack elevations, schedules, specifications, and QA for new construction, retrofit, and tenant improvement work. Delivered remotely with field inputs and responsibility boundaries defined before drafting starts.
The deliverables are selected to match the project phase and contract. Each item below can be included, excluded, or assigned to another party in the responsibility matrix.
Owner requirements, project specifications, applicable standards, system boundaries, design assumptions, field-verification responsibility, and the interfaces another discipline must carry.
Telecommunications outlets, device locations, cable-tray and conduit routes, sleeves, zone pathways, service entrances, and keyed notes coordinated against the current architectural background.
Copper and fiber topology, media and strand or pair counts, termination points, pathway relationships, entrance facilities, and the connection between ER, MDF, IDF, and TR spaces.
Room layouts, rack and cabinet placement, wall fields, ladder rack, cable management, service clearances, grounding and bonding, power coordination, and equipment elevations.
Cable and equipment schedules, labeling rules, installation details, test criteria, closeout requirements, Division 27 specifications where scoped, and a bill of materials when the project needs one.
A documented pre-issue QA pass, coordinated revisions, defined deliverable formats, and RCDD review or sign-off only within the responsibility written into the proposal.
Structured cabling touches nearly every building discipline. The design package should show each interface clearly enough for its responsible party to act.
The result is not a promise that every concealed condition is known. It is a controlled record of what was coordinated, what was field-verified, what remains open, and who owns the next decision.
The workflow starts with current architectural backgrounds, owner standards, existing-condition records, room data, equipment assumptions, and a named field-verification plan.
Milestones and review windows scale with the project, but the sequence stays stable enough for the whole team to know what is current.
Review the RFP, owner standard, Division 27 requirements, project location, available backgrounds, schedule, and the exact RCDD role.
Resolve system boundaries, field inputs, pathway and space assumptions, media strategy, labeling, testing, and coordination ownership before production expands.
Produce coordinated plans, risers, room layouts, elevations, schedules, and details against controlled backgrounds and named review milestones.
Run the RCDD QA pass, close comments, record assumptions and open items, and issue the agreed native files and PDFs at a controlled revision.
When included, answer RFIs, review submittals, assess changes, and check closeout records against the issued design intent.
Design references are selected for the actual building, system, owner standard, adopted code, and project specification—not copied from a generic notes sheet.
RCDD review covers the agreed ICT design responsibility. It does not replace a licensed PE, architect, code official, or the contractor's obligation to verify field conditions and install the work correctly.
Need the room layer in more detail? Review MDF, IDF, ER, and TR telecom room design. When the assignment includes contract specifications, see the dedicated Division 27 telecommunications design and coordination service.
Need the broader credential and engagement picture? See how to hire an RCDD consultant.
Send the project location, phase, available backgrounds, drawing count, schedule, and any Division 27 or RCDD requirement. You'll get a direct fit assessment and a clear next step.