HFC Construction Drawings: Coordinate Fiber and Coax Sheets Before Release

A fiber-route sheet can leave the design desk on revision C while the coax-strand sheet still shows revision A. The node ID on the BOM matches neither. Crews then pull the PDF in the truck, not the revision the operator thinks it released. The failure is coordination, not drafting talent.

This guide is a cable-operator walkthrough of construction-document coordination and release QA. RF design choices and live cutover stay off this page. Engineering stays in-house. Construction, when in scope, is full turnkey work by Draftech-managed crews.

What HFC Construction Drawings Must Keep on One Revision

HFC construction drawings are the issued construction package that keeps fiber-route sheets and coax-strand sheets on 1 revision, with device IDs matching the schedules they cite. CableLabs specifications and the SCTE standards catalog do not prescribe one universal drawing set. The operator, AHJ and manufacturer control the sheet list.

We treat the package as a single issued object, not as two live files that happen to share a job number while the sheet families still disagree on node identity. If the fiber-route family can be plotted without the coax-strand family, the package is not coordinated yet. The operator's CAD standard names which files belong. We do not invent a default sheet count to close the gap.

CableLabs DOCSIS 4.0 Physical Layer Specification, CM-SP-PHYv4.0-I07-250627, released June 27, 2025, defines physical-layer interfaces for DOCSIS 4.0 systems. It does not publish a construction drawing list, a scale, a symbol library or a title-block rule. Using that specification as a substitute for the operator's CAD standard is a category error. Interface language belongs in design basis notes when the operator asks for it. It does not become a sheet index.

SCTE 180 2025, Recommended Practices for Coaxial Cable Construction and Testing, posted November 2025, is a construction-practice manual for coaxial plant. SCTE 181 2025, Recommended Practices for Optical Fiber Construction and Testing, is the companion manual for optical-fiber construction. Both describe field work. Neither one issues a universal HFC construction drawing set. We cite them when a note on the sheet points at a construction practice the operator has adopted. We do not treat either document as the drawing standard.

The controlling list is local. The operator's CAD manual sets the sheet list. AHJ submittal instructions can add exhibits, and manufacturer installation drawings can add product sheets for that job. Our HFC network design and coax plant engineering service produces the coordinated package against that list. Architecture questions live in hybrid fiber coax engineering. This page does not redo that work.

Synchronize Fiber-Route Sheets with Coax-Strand Sheets

Two sheet families have to describe the same plant object. The fiber-route family shows optical path and the fiber identity that arrives at the node. The coax-strand family shows the coaxial plant that leaves that node. If those families disagree on the node ID or the serving leg, a crew can build the wrong half of a correct-looking job from a package that looks complete on paper.

We start with identity, not with line weight. Every node ID that appears on a fiber-route sheet has to appear on the matching coax-strand sheet. Serving-leg IDs follow the same rule. Where the operator uses a GIS key plus a field label, both keys travel. A pretty overlay that drops one of them is not coordination.

Shared work limits matter as much as shared IDs. A fiber-route sheet that stops at the node housing while the coax-strand sheet starts three spans later leaves a gap no crew can fill from the package. We mark that gap as an open coordination item. We do not shade it in and hope the field lead notices.

The table below is a preview of the checks the later sections expand. It is not a scoring rubric and it is not an acceptance test. The operator's CAD standard still decides which files are in the issued set.

That last row is the one that fails quietly. A matching pair of sheets can still be the wrong revision if the operator never released them. We will get into that hold in the revision section below.

Keep Device IDs Tied to Schedules and BOM References

A callout on a strand sheet is not a material authorization. The schedule row and the BOM line have to name the same device ID and the same manufacturer document revision the plan view uses, or the warehouse pick will not match the sheet. When those disagree, the sheet is describing a plant the warehouse will not pick.

We check node IDs first because they bind the two sheet families. Amplifier and power IDs follow on the coax-strand sheets, each against the operator's naming rule. Passives use that same rule. A housing family name is not a device ID. If the operator requires a module or faceplate identity, the schedule has to carry it. We do not invent a generic SKU to make the row look complete.

One thing I still get wrong is treating a clean title block as proof the BOM line and the strand callout share the same device ID. They often do not. That limitation is mine: the title block can be current while a tap value or a power-inserter tag still points at last week's file. The check is a row-by-row comparison, not a glance at the plot stamp.

Manufacturer installation drawings stay references. They tell the crew how a listed product is assembled. They do not replace the operator's sheet list and they do not set a Draftech threshold. When the BOM cites a manufacturer document, we preserve the document revision on the BOM and on the note that points at it. A later vendor PDF dropped into the job folder is not an issued change until the operator says it is.

The fiber construction package deliverable checklist covers how a bid package ties a BOM to plan sheets on a fiber job. The HFC case adds a second sheet family that has to cite the same IDs. If the fiber BOM and the coax BOM describe different nodes, stop. Do not merge the lists to hide the split.

Carry Installation Notes and Permit References as Issued Facts

Installation notes fail when they wander into design advice. A note that says "confirm with engineering in the field" is not an installation instruction. It is a hole in the issued set. We write notes that a crew can follow against a named sheet and a named revision, or we leave the note off and keep the item on the open-coordination list.

Permit references are the same kind of fact. The sheet should name the jurisdiction and the application or permit ID that belongs to the revision being issued. A banner that reads "permits pending" on every sheet tells the AHJ nothing and tells the crew less. If the authorization is still in review, say that on the permit index and name the file that was filed. Do not imply a grant the AHJ has not written.

We do not invent a PE stamp or a Draftech certification block. Some operators require a professional-engineer seal. Some AHJs require their own approval block. Those marks follow the controlling document, not a house template. CAD layer and title-block discipline for the files themselves is the adjacent CAD/GIS documentation standard problem. Here the question is narrower: does the note or the permit citation point at the revision being issued?

AHJ instructions vary by jurisdiction. A county ROW permit and a pole-attachment application can each demand a different exhibit. We list each authorization once, with the sheet IDs that were submitted. Copying one county's block onto another county's set is how packages bounce.

Hold Revision State Until Owner Release Evidence Exists

Revision letters lie when they describe a working file. Revision C on a title block is not an issued revision until the operator's release record names that letter and those files. Mixing a live CAD save into an issued PDF set is the usual way a crew receives two truths about the same node on the same day.

We keep one issued revision across the fiber-route family and the coax-strand family. If the fiber sheets moved to C and the coax sheets stayed on B, the package is not issued no matter how clean each title block looks on its own. Partial issue is allowed only when the operator's CAD standard defines a bounded subset and the release record names that subset. Silence is not a subset.

Owner release evidence is a dated, named decision. The revision ID and the file list have to be reconstructable later. A plot log is not that record. Neither is a chat message that says the package is good to go. The HFC engineering support queue is where a later ticket should find that same issued reference. If the queue and the drawing set disagree, the later ticket will correct a plant that was never released.

We keep HFC engineering in-house. When construction is in scope, we deliver full turnkey work through Draftech-managed subcontract crews under our QA/QC and safety program, matching the accountability described in our company approach. That delivery does not transfer drawing-list control. The cable operator still writes the release. Crews build from the issued set. They do not promote a redline to issued by installing it.

Redlines belong in a change record, not in the issued PDF, until the operator accepts them onto a new revision. We can show the redline next to the issued sheet. We cannot treat the markup as the construction document. If the field condition cannot wait, the operator issues a revised package. That is slower than a verbal field change. It is the only way the next ticket sees the same plant.

Who Should Release HFC Construction Drawings, and Who Should Wait

Release is an operator decision about a named revision, not a drafting milestone. The recommendation below changes with the job you are actually running.

Cable-operator plant-records lead: freeze the node and device IDs before anyone plots. If GIS keys and field labels disagree, hold the issue. Do not let a clean title block outrun the identity table. Your CAD standard is the sheet list. CableLabs and SCTE will not supply a substitute.

Construction manager on a node-area rebuild: do not pull material until the fiber-route family and the coax-strand family share 1 issued revision and the BOM cites those same IDs. A warehouse pick against last week's BOM is a field change you will pay for twice. Ask for the release record, not for a newer plot.

Overbuilder placing fiber on incumbent coax: keep your fiber-route sheets from silently rewriting the incumbent's coax IDs. The coax-strand family still belongs to the operator's naming rule even when your fiber is new. If you cannot obtain the current coax identity, that is a hold, not a chance to assign your own numbers.

Small MSO with one CAD seat: issue one PDF package that contains both sheet families, then lock the working files. Two live DWGs with the same job number are how revision C and revision A ship together. One issued package is slower to open. It is the package a later support ticket can find.

For a node-area rebuild already sitting in CAD, the useful next artifact is the operator's dated release record naming the files the warehouse and the truck will actually use, not a cleaner title block on a plot nobody released. Hold the warehouse pick until that record exists.

If you want that issued set produced against the sheet list the operator actually controls, send the operator CAD standard with both current sheet families to info@draftech.com. Our HFC construction-document coordination does not substitute a CableLabs or SCTE drawing list for that standard. Active in 24 states. Available across all 50 U.S. states.

If hfc construction drawings is part of a qualifying route, Draftech engineers the first 20,000 linear feet at no cost, from feasibility and field survey through permit approval. Request the free design package. The owner reviews each request before Draftech commits the package.