Defining Project Scope & Estimating

Identifying the Scope of Work

Every RCDD engagement begins with a single question: what, exactly, is the designer being asked to design? The Define Scope of Project domain sits first in the blueprint's four job-task domains and represents 10% of the RCDD exam, but its influence extends across the entire project — a poorly defined scope produces cost overruns, missed requirements, and change orders long after the design is complete.

Scope of work begins with the owner's or architect's project requirements: building type and occupancy, the systems to be designed (structured cabling, backbone, telecommunications spaces, pathways, and any specialty systems such as audiovisual, wireless, or electronic safety and security), and the boundaries of the RCDD's responsibility versus other disciplines (electrical, mechanical, general contractor). The RCDD must also identify applicable codes and standards and the governing authority having jurisdiction (AHJ), because code and standard requirements — and the order of precedence when sources conflict — shape what "complete" scope looks like. A scope statement that omits a required system, an interface with another trade, or a code obligation is an incomplete scope, regardless of how detailed the drawings eventually become.

Site Survey and Assessment of Current Conditions

For renovation, retrofit, and addition projects — the majority of real-world ICT work — the RCDD cannot design from record drawings alone. Existing drawings are frequently outdated, incomplete, or simply wrong after years of unrecorded field changes. A site survey (sometimes called a site assessment or walk-through) is the RCDD's direct, physical verification of current conditions before design begins.

A thorough site survey typically documents:

• Existing pathway condition and available capacity — conduit, cable tray, and raceway fill, and whether existing pathways can be reused or must be replaced/supplemented.
• Existing telecommunications spaces — location, size, power, HVAC, and whether current spaces meet the sizing and environmental requirements for the new design.
• Existing cable plant — media type, category/grade, age, and whether it can be reused, needs augmentation, or must be fully replaced.
• Building structure and obstructions — ceiling heights, structural members, fire-rated assemblies, and other trades' existing infrastructure that will affect new pathway routing.
• Environmental hazards — asbestos, confined spaces, or other conditions that affect access and safety planning.

Findings from the site survey are reconciled against record documents, and discrepancies are documented — because the survey, not the record drawing, becomes the basis of design when the two disagree. This assessment directly supports later phases: an inaccurate site survey produces inaccurate cost estimates, inaccurate pathway designs, and unanticipated field conditions during installation.

Estimating Project Cost

Once scope and existing conditions are understood, the RCDD contributes to (or produces) a project cost estimate. ICT cost estimating combines several components:

Estimates are built from quantities derived from the design (or, at early stages, from historical unit costs per outlet, per square foot, or per drop) and refined as the design matures from conceptual to construction documents. An RCDD's estimate must be defensible — traceable back to specific quantities and unit prices — because it becomes the baseline against which bids and change orders are later measured.

Estimating Schedule and Timeline

ICT installation does not happen in isolation; it is one sequence within the overall construction schedule. The RCDD's timeline estimate must account for:

1. Design duration — time to produce, review, and finalize design documents through each submission phase.
2. Procurement lead time — ordering and delivery of cable, hardware, and specialty equipment, which can be the schedule's longest pole for long-lead items.
3. Rough-in sequencing — ICT rough-in (pathway and backbone placement) typically follows structural and electrical rough-in and must be coordinated before walls and ceilings close.
4. Trim-out and termination — outlet and equipment termination, generally following finishes.
5. Testing, commissioning, and closeout — field testing, punch-list resolution, and documentation delivery, which must be scheduled before occupancy.

A realistic schedule protects the owner from a design that cannot physically be installed in the available construction window, and protects the designer from being blamed for delays caused by unrealistic compression elsewhere in the schedule.

Capturing Design Intent

The final piece of scope definition is design intent — a written and graphic record of what the design is meant to accomplish and why, independent of the specific products eventually installed. Design intent captures the owner's operational requirements (expected user density, growth projections, redundancy expectations, performance targets) and translates them into a basis of design that guides every subsequent decision: media selection, pathway sizing, space allocation, and testing criteria.

Design intent matters because construction documents alone rarely explain why a decision was made. When field conditions force a change, or when a contractor proposes a substitution during bid or installation, the design intent document is what lets the RCDD (or a successor) evaluate whether the proposed change still satisfies the owner's actual requirements — not just the letter of the drawings. Capturing design intent early, and keeping it available throughout the project, is what allows scope, cost, and schedule decisions to remain traceable back to the owner's original business need.