Telecom Installation Make-Ready Checklist
A pre-mobilization gate for approved drawings, rooms, pathways, materials, access, testing, and closeout before cable crews arrive.
A telecom installation is not make-ready because the start date is on the schedule. It is make-ready when the field team can identify the current work, reach every work area, receive approved material, use coordinated pathways and spaces, perform the required tests, and turn the result over without inventing missing decisions. The gate belongs before labor and deliveries mobilize, while a missing answer is still a coordination item instead of downtime.
Telecom make-ready is an evidence check, not a meeting. The release package should show the approved scope and drawings, accessible work areas, usable pathways and spaces, approved materials, named coordination owners, test requirements, and closeout format. If a required condition has no evidence or owner, it is open.
Keep make-ready separate from design review
Design review asks whether the proposed ICT system is coordinated and fit for purpose. Make-ready asks whether the approved work can start in the actual building on the planned date. Both matter, but combining them hides risk. A make-ready walk should not redesign rack layouts, select unapproved products, or settle a disputed scope in the corridor. It should record the conflict, assign an accountable decision owner, and hold only the affected work until the decision is issued.
Use one controlled checklist by area, phase, or work package. Name the drawing issue, specification revision, approved submittals, site walk date, attendees, open-item log, and release authority. A green status without that evidence is only optimism.
BICSI describes its ITSIMM 8th edition as covering space preparation, cable installation, testing, firestopping, bonding and grounding, project management, and retrofits. The active TIA infrastructure set lists the current 568, 569, 606, and 607 documents used across premises cabling. Use the purchased standards, adopted code, project specification, approved submittals, and safety plan for actual requirements.
1. Freeze the work package and document basis
- Identify the exact building, floor, area, system, phase, and limits being released. Do not mark an entire project ready when only one zone is clear.
- Record the current-for-construction drawing index, specification issue, addenda, approved RFIs, sketches, bulletins, and owner standards available to the crew.
- Confirm that plan symbols, risers, room elevations, schedules, details, specifications, and bill-of-material assumptions describe the same scope.
- List every delegated-design, shop-drawing, permit, PE, RCDD, AHJ, or owner approval that applies, and record its status without treating one approval as a substitute for another.
- Separate inclusions, exclusions, alternates, allowances, owner-furnished equipment, contractor-furnished equipment, and work by others.
- Name the person authorized to release the field package and the process for replacing superseded sheets in print and digital locations.
2. Verify the actual site, access, and sequence
- Walk the released areas against the current drawings. Record photographs, measurements, markups, and unresolved conditions through the approved project system.
- Confirm site access, badging, escorts, keys, working hours, shutdown windows, occupied-area restrictions, noise and dust controls, and protection requirements.
- Check that predecessor work is complete enough for telecom: walls, ceilings, paint, millwork, doors, housekeeping pads, sleeves, tray, conduit, backboards, and equipment supports as applicable.
- Coordinate the installation sequence with architectural, electrical, mechanical, fire protection, security, AV, DAS, controls, and other trades sharing rooms, ceilings, risers, or pathways.
- Identify hazardous, controlled, clinical, secure, or operational areas and the approved work method before tools or project files enter them.
- Confirm staging, unloading, secure storage, waste handling, lifts, ladders, carts, parking, freight elevators, and protection of finished work.
3. Release telecommunications spaces by evidence
A room name on a plan does not prove the room can receive racks and cable. Release each entrance facility, equipment room, telecom room, cabinet, and serving enclosure individually. Use the 72-item telecom room design checklist for the full programming and coordination pass; use this make-ready gate to confirm that the approved decisions now exist in the field.
- Confirm the room or enclosure identity, serving area, rack and cabinet locations, wall fields, door/access path, and reserved service zones against the approved layout.
- Verify that the room is weather-tight, secure, clean, illuminated, and at the environmental condition required by the project before equipment and termination hardware arrive.
- Confirm architectural finishes, backboards, housekeeping provisions, anchors or supports, sleeves, tray entries, and penetrations are complete or have a dated owner.
- Verify coordinated power, dedicated receptacles where specified, emergency or UPS interfaces, lighting, cooling, leak risk, bonding points, and other discipline inputs against the issued documents.
- Record unrelated piping, ductwork, storage, ceiling conflicts, access restrictions, and unapproved equipment as hold items instead of working around them silently.
- Confirm rack, cabinet, ladder, tray, pathway, patching, testing, maintenance, and replacement access will remain available after every trade completes its work.
4. Prove pathways and supports are usable
- Trace representative routes from outlet or device locations back to the serving space, including transitions, risers, sleeves, pull points, cable tray, conduit, J-hooks, and entrance pathways.
- Confirm the installed pathway matches the released route, size, count, fill basis, bend and pulling plan, support intent, and approved change record.
- Check pathway continuity, bushings or fittings, pull strings, covers, grounding where required, accessibility, debris, water, sharp edges, and damage before cable is placed.
- Verify supports are attached only to approved building structure or support systems and that shared supports or pathways have an identified capacity and owner.
- Coordinate separation and crossings with power, lighting, mechanical equipment, sources of interference, heat, wet locations, hazardous conditions, and other systems under the project criteria.
- Confirm fire-resistance-rated penetrations have an approved system, responsible installer, inspection path, and temporary or final firestopping sequence. Do not invent a system in the field.
5. Close the power, bonding, and environmental interfaces
Telecommunications work often depends on electrical and mechanical conditions without owning their design. Make the interface explicit. ANSI/TIA-607-E is the active TIA bonding and grounding standard, but the project electrical documents, adopted code, licensed design responsibility, and approved submittals determine what the contractor installs.
- Identify each telecommunications bonding point, conductor, busbar, rack or cabinet connection, pathway connection, and responsible trade shown in the released package.
- Verify the upstream electrical grounding interface is available and accepted by the responsible electrical party before closing walls or energizing equipment.
- Confirm power circuits, receptacles, branch-circuit identification, surge protection, UPS or emergency-power interfaces, and equipment cord/plug assumptions match approved equipment.
- Confirm the planned environmental condition, heat load, ventilation or cooling, filtration, leak protection, and monitoring interfaces are available before sensitive equipment is stored or energized.
- Record cross-discipline inspections and test evidence instead of signing off another discipline’s design responsibility.
6. Match materials, submittals, and logistics
- Build the delivery list from approved submittals and the current work package: cable, connecting hardware, racks, cabinets, pathways, supports, firestop systems, bonding components, labels, consumables, and test adapters.
- Verify manufacturer, product family, performance category, media, listing, environmental rating, color, connector, polarity, compatibility, warranty conditions, and approved substitutions where the project defines them.
- Check quantities by released area with spare, scrap, pull-length, packaging, and lead-time assumptions visible. A purchase order total is not a field quantity check.
- Inspect deliveries for damage, moisture, temperature exposure, reel or box identification, lot information where required, and storage conditions. Quarantine nonconforming material.
- Confirm specialty tools, calibrated test equipment, launch and receive cords, reference cords, cleaning supplies, fusion or termination equipment, lifts, and access equipment are on hand and suitable.
- Tie owner-furnished or active-network equipment to a named delivery, configuration, security, and acceptance owner rather than allowing it to become an installer assumption.
7. Release the crew, work method, and communication path
- Confirm staffing, supervision, qualifications, manufacturer requirements, permits, licenses, site orientations, and task-specific training required by the contract and jurisdiction.
- Review the approved safety plan, hazard assessment, fall protection, lift plan, confined-space or hot-work requirements, energized-work restrictions, and emergency process with the responsible safety authority.
- Hold a pre-installation briefing on scope, current documents, sequence, workmanship sample, labeling, testing, protection, housekeeping, photos, redlines, RFIs, and stop-work triggers.
- Name the field lead, design/RCDD contact, general contractor coordinator, owner contact, responsible discipline contacts, test witness, and after-hours escalation path.
- Define how the crew reports conflicts. Field improvisation must not replace an RFI, approved sketch, or documented direction when design intent changes.
8. Set labeling, testing, and closeout before pulling cable
- Approve the labeling scheme, identifier list, label material, print format, placement, owner record fields, and change-control method before bulk labels are produced.
- Confirm test limits, link or channel configuration, instrument capability, current calibration, adapters, reference method, file naming, retest rules, and witness requirements for each media type.
- Create the test-result and administration-record structure before testing begins so every result resolves to the same identifiers used on drawings and labels.
- Define redline frequency, photograph requirements, daily reports, concealed-work records, RFI incorporation, and the party who reconciles field changes into record documents.
- List closeout deliverables, formats, naming, folder structure, warranties, training, spare material, test exports, as-builts, administration records, acceptance forms, and turnover dates.
- Run a first-work sample for cable routing, support, dressing, termination, labels, firestopping, bonding, testing, and records. Release production only after the sample is accepted by the named reviewer.
9. Use a short no-go list
A checklist fails when every open item becomes an exception. Define the small set of conditions that stop the affected work package. The project team may add others, but these are practical defaults:
- No current released drawing/specification basis or no process for controlling superseded documents.
- Unresolved scope ownership, permit, licensed-discipline, AHJ, or owner approval that affects the planned work.
- Unsafe or unauthorized access, incomplete predecessor work, unavailable shutdown, or an occupied-area restriction without an approved method.
- Telecommunications space, pathway, support, firestopping, power, bonding, or environmental condition that prevents compliant installation.
- Unapproved, incompatible, damaged, or missing material, tooling, or calibrated test equipment.
- No accepted labeling/test/record method, no escalation contact, or no authority to approve a field change.
10. Record the release and keep it alive
End the review with a dated status for each area: released, released with named conditions, or held. Every open item needs a description, evidence required, owner, due date, affected work, and decision path. Publish the record where the field team already works, not in a private meeting notebook.
Re-run the affected sections when drawings, submittals, sequence, access, existing conditions, material, or responsible parties change. Make-ready is not a permanent certificate; it is the current evidence that a defined package can start.
Download the free telecom installation make-ready checklist for the project record. It is an editable coordination aid, not a safety plan, code review, site survey, installation standard, or substitute for approved construction documents.
Common telecom make-ready questions
What does make-ready mean for a telecom installation?
It means a defined work package has the current documents, approvals, access, spaces, pathways, materials, coordination inputs, test method, and closeout path needed to begin without undocumented design decisions. The evidence and responsible parties should be recorded.
Who should sign off the make-ready checklist?
The contract should name the release authority. Inputs commonly come from the general contractor, installing contractor, ICT designer or RCDD, owner, responsible licensed disciplines, safety authority, and other coordinating trades. One signature should not imply responsibility for every discipline.
When should the make-ready review happen?
Run it early enough to close long-lead and coordination items, again shortly before the affected crew mobilizes, and whenever a material change affects the released package. Large projects should release and recheck by building, floor, zone, system, or phase rather than waiting for one project-wide event.
Does this checklist replace a site survey or approved drawings?
No. It uses field-verification evidence and approved documents; it does not create them. Project drawings, specifications, standards, code, safety requirements, manufacturer instructions, approved submittals, and responsible-professional decisions still govern.
Principal of ICT Design Partners, a focused, remote-first ICT design, QA, and white-label practice for contractors and design firms.
About the firm