A drawing set can leave the office as issued-for-construction and still not be occupiable this week. Make-ready listed as complete on a pole-owner letter can still be sitting on the pole as an unresolved rearrangement. An approved permit can carry a night-work window that never made the look-ahead.
This article is the construction-management gate that compares that released design to the field as it sits today, then writes a go or a no-go before notice to proceed. It is not a design-error QC pass. It is not a documentation completeness test. Those reviews live on different paper.
Network Design Review for Construction Readiness: The Go/No-Go Before NTP
A network design review for construction readiness is the construction-management comparison of the released design against current field state, ending in a written go or no-go before NTP. We run seven field checks. OSHA 29 CFR 1926.651(b), eCFR current September 11, 2026 after Title 29 was last amended September 9, 2026, requires locates before excavation opens.
That sentence is the whole job. The drawings say what to build. This review asks whether the route will accept that build on the date crews are told to start, including the pole IDs and the workfront the NTP letter actually names. A cover sheet dated last month does not answer it. Neither does a bid tab.
We run the gate in-house against our own issue set. Engineering stays a Draftech function. When the owner also wants the plant installed, full turnkey construction uses Draftech-managed subcontract crews under our QA/QC and safety program, so one accountable party stays on the work from the go record through installation. The construction side is full turnkey, not a management-only overlay.
EJCDC C-700, Standard General Conditions of the Construction Contract (2018 Edition), is the construction general-conditions book we reference when the contract family is EJCDC. C-700 treats notice to proceed as the start authorization. It does not inspect poles. It does not refresh an 811 ticket. The field-state review is the condition that authorization should sit on before anyone occupies a named workfront.
Network Design Review for Construction Readiness Versus Design QC
Design QC and this gate share a drawing set and almost nothing else. The LLD quality-control checklist for fiber design errors hunts mismatches that should never have left engineering, starting with fiber-count errors and missing spans. That work happens before issue. This work happens after issue, against the field.
Document completeness is a third review. The OSP documentation construction-handoff standard asks whether the package a crew receives is controlled and complete. A complete package can still describe a pole that is not ready. Completeness is not occupancy.
The bid package is a fourth document. Fiber project design for construction bidding is how contractors price the same units. Award is not a field go. A priced schedule can still point at make-ready that has not happened.
Keep the four records separate. Mixing them is how a design fix gets treated as permission to occupy, and how a tidy transmittal gets treated as a locate.
Field-State Checks That Must Pass Before NTP
Owners often ask for a single ready flag on the look-ahead. That flag hides the workfront that is actually blocked. We keep the checks on separate rows so a clear pole batch cannot launder an open bore, and so a current permit cannot launder a stale 811 ticket. The NTP letter then names the row that failed instead of painting the route green.
The table below is the map the rest of this guide expands. It is a Draftech construction-readiness control set, not a claim about how every owner writes an NTP letter.
| Field-state check | Evidence on the go record | No-go if missing | Owner action before NTP |
|---|---|---|---|
| Pole and make-ready status | Pole ID, rearrangement complete, attachment authority current | Crews lash to a pole the owner has not cleared | Walk the batch against the issued pole list |
| Permit conditions in hand | Permit number, condition list, work-hour window | An approved stamp hides a night-only clause | Assign each condition to the look-ahead |
| ROW and easements | Recorded instrument or license for the occupied strip | The drawing assumed a corridor nobody conveyed | Match stationing to the recorded document |
| Utility locates | Ticket number, lawful start, positive response | Excavation opens on a stale or uncalled ticket | Confirm the ticket is live on NTP day |
| Material lead times | Identity, quantity on hand, delivery date for the batch | The crew mobilizes against a back-ordered closure | Hold the batch until the named part is on the yard |
| Crew sequencing | Predecessor complete, next trade named, hold owner | Splicers arrive before the span is in the air | Release only the workfront whose predecessor is done |
| Traffic control | Approved TCP, Revision 1 typical, device list on site | Lane work starts on a drawing the county did not stamp | Stage the TCP with the same workfront ID |
Seven checks, because those are the seven things that actually stop a start. We do not collapse them into a single "ready" checkbox. A pole batch can be clear while the bore still waits on locates. The record has to say that.
Paper complete is not field complete: A pole-owner letter that make-ready is finished is not evidence until the issued pole still shows the rearrangement on the stick.
Each row needs an owner. If the permit condition has no name on the look-ahead, it will be discovered by the first cop who asks why the cone taper is in a daylight lane. If the locate ticket has no refresh date, a weather hold will eat the lawful window and nobody will notice until the bucket is already on site.
Poles, Make-Ready, and Locates Against the Released Design
The issued pole list is a claim about the field. This review tests that claim. We take the construction-issue pole IDs and ask whether each pole still exists and still belongs to the owner the application named. The attachment height the loading report used has to match what is on the stick. A transferred pole with a new owner is a no-go on that ID until the new owner has spoken, because the issued attachment authority still names the prior owner of record.
47 CFR 1.1411 (Timeline for access to utility poles), displayed on the eCFR as current as of September 14, 2026 after Title 47 was last amended September 14, 2026, is the federal pole-access clock we cite when the pole owner is a utility subject to those rules. For a Regular Order, 1.1411(f)(1)(ii) sets communications-space make-ready completion no later than 30 days after the utility's notification is sent. Mid-Sized and Large Orders add days under 1.1411(h). That clock is pole-owner process. It is not a field photograph.
What 1.1411 Does Not Prove
A 30-day date that has passed does not prove the rearrangement is on the pole. The communications-space date can run, and the issued pole can still carry the prior attacher at the height a lashing plan occupies. The FCC clock expires. The stick has not moved. NTP on that batch would be a trespass dressed as a schedule win.
Walk the batch. Photograph the attachment space. Match the photo to the pole ID on the issued list. If the rearrangement is not visible, the go record says no on that ID, even if the utility's letter says the work is done. Letters close invoices. They do not close clearance.
Underground is a different test, and it is not optional. 1926.651(b)(1) requires the estimated location of underground installations determined before an excavation is opened. 1926.651(b)(2) requires utility owners contacted within established or customary local response times. When they cannot respond within 24 hours, unless a longer period is required by state or local law, the employer may proceed only with caution and with detection equipment or another acceptable means. State 811 statutes routinely require longer than that 24-hour default. We do not treat the OSHA floor as the ticket we will actually hold.
Common Ground Alliance Best Practices Version 22.0, published February 26, 2026, is the consensus locate playbook we write the go record against. Version 22.0 added Practice 5-35 for large and complex project locate requests. A fiber bore that crosses a corridor with stacked foreign utilities is that class of request. A single ticket drawn around a whole mile is how overnotification hides an unmarked lateral. White-line the work. Bound the ticket to the workfront being released. Keep the ticket number on the same row as the segment ID.
One thing I still catch on our own go records is a locate ticket whose lawful start window closed during a weather hold. That limitation is on us. The ticket date has to be current on the morning of NTP, not on the afternoon of the last pothole, because a weather hold can close the lawful start window overnight. A refresh after the hold is not paperwork. It is the difference between a legal excavation and a strike.
Permits, ROW, Easements, and Traffic Control Already in Hand
An approved permit is not a work-hour release. The stamp gets the owner through intake. The conditions decide whether a daylight crew can occupy the lane. We read the condition list onto the look-ahead before anyone loads cones. A night-only window that nobody staffed is a no-go, even if the permit number is painted on the title block and the county stamp is still current on the cover sheet.
The Manual on Uniform Traffic Control Devices for Streets and Highways, 11th Edition with Revision 1, dated December 2025, took effect on March 5, 2026 and is the edition in force. Revision 1 governs the temporary-traffic-control sheets in this package. County reviewers stamp against it. A TCP drawn to the December 2023 original, without Revision 1, is the wrong manual on a 2026 submittal. We do not send a crew out on a typical the receiving agency has already rejected on paper.
Permit Approval Is Not a Work-Hour Release
ROW is the same kind of mismatch. The drawing can show a corridor. The recorded easement can stop ten feet short of the bore pit. We match stationing to the instrument, not to a GIS color. A license that expires before the restoration window closes is a hold, because the crew that leaves a trench overnight is occupying land the license no longer covers.
Private easements and public ROW fail for different reasons. A county permit does not convey the private strip behind the sidewalk. A recorded easement does not waive the county's lane-closure rules. The go record names both, or it names the one that is missing. Silence on the private strip is how a landowner meeting happens at 7 a.m. with a crew already in the ditch.
Traffic control has to travel with the workfront, not as a binder in the office. Revision 1 typicals and device counts sit on the same row as the segment being released, with the approved hours. If the county requires a certified flagger and the shift does not have one, that is a no-go with a named cause. It is not a field improvisation.
Condition assignment: Every permit condition that can stop a shift needs a name on the look-ahead. An unassigned night window will be discovered by the first stop, not by the go record.
We have issued a go where the permit was current and the TCP was not the sheet the county stamped. That one is ours. The approved drawing number has to match the sheet in the truck. A later revision that never went back through intake is not a field improvement. It is an unpermitted typical.
Materials, Crew Sequence, and the Written Go/No-Go
A crew that mobilizes against a back-ordered splice closure will stand in the ROW burning permit hours. We do not treat "on order" as on hand. The go record names the identity and the quantity sitting on the yard for that batch. If the closure on the BOM is not the closure on the pallet, hold the batch. Substitution is an engineering revision, not a warehouse courtesy.
Lead time is a date, not a vendor promise. We put the promised delivery on the look-ahead and we put the received date on the go record. Those two dates disagree more often than purchasing wants to admit. The go uses the received date. A promised Tuesday does not staff a Wednesday shift.
Crew sequence is the last check because it is the one production managers skip when the calendar is loud. Aerial work does not share prerequisites with underground work. Splicing waits on plant already in the air. Restoration waits on an open trench being closed. A splicer on a span that is not in the air is idle cost. A restoration crew on an open trench is a safety event. The predecessor has to be complete on the named workfront, not "mostly done" on the route.
What the Go/No-Go Record Has to Carry
The record is short on purpose. Workfront ID. Issued revision. The seven checks, each with evidence or a named hold. Who signed the go. Who is forbidden to occupy a held batch. A percentage complete does not belong on it. Route-level green does not belong on it. If a row is blank, the answer is no.
Partial NTP is the honest form of this gate. Aerial batch A can go. Underground batch B waits on locates. The letter says both. A blanket NTP that "excepts" the blocked work in a hallway sentence is how the excepted work gets built anyway. Write the exception on the same page as the go and put the segment ID on that line. If you cannot name the held batch, do not issue the go.
This is the function fiber construction management is hired to own: freeze a workfront when the field has not caught the drawings, and release it only when the seven checks are evidenced. Inspection after the fact cannot recover a strike, a trespass, or a night-work citation that the go record should have prevented.
Recommendation: Who Should Release NTP
Small ISP, single-state build, one contractor: run the seven checks on the first workfront before anyone loads a reel. Do not NTP the whole route because the first mile looks clear. A 30-day 1.1411 clock on the pole application is not a pole walk. Hold the second mile until its own row is filled, even when the owner wants one NTP letter covering every workfront on the bid form.
BEAD subgrantee on a 2026 build calendar: write the go/no-go as a grant record, not a text to the superintendent. The same segment IDs should appear on the permit log and the locate ticket. The pay application should use those IDs too. A start that cannot be reconstructed in the file is a later audit finding. Keep the BEAD Checklist beside the go letter so the field gate and the grant file use the same identifiers.
Overbuilder with aerial and underground on the same notice: split the go. Aerial does not wait on 811 if no earth is moving. Underground does not start because the lashing crew is free. Two methods on one NTP letter is how a locate miss gets blamed on the aerial superintendent.
Owner who already named a construction manager: do not hand that person an issued set and a start date with no field-state row. The manager can freeze a workfront only against evidence. Give them the seven-check record as the first deliverable, then let construction management run the work from that baseline.
The NTP letter is the decision this review exists to write. Draftech writes the issued design in-house, and when the owner wants the plant built under the same accountability, we deliver full turnkey construction through Draftech-managed crews under one contract. Active in 24 states. Available across all 50 U.S. states.
If the go/no-go is the document you need written, reach out at info@draftech.com. We will look at whether the issued revision and the current field actually agree.
Before NTP, an owner can test Draftech's release discipline on a qualifying route. Through our free design offer, Draftech engineers the first 20,000 linear feet at no cost, from feasibility and field survey through permit approval. A Draftech owner reviews each request before we commit the package.
Need the field-state go/no-go before NTP? Talk to our construction team about the readiness review.
