Build-to-Suit Playbook: 15 Fiber Milestones From Letter of Intent to Light-Up

Build-to-Suit Playbook: 15 Fiber Milestones From Letter of Intent to Light-Up

In a build-to-suit, the path from “yes” to “light-up” is a sequence of paperwork, fieldwork, and approvals that can stall or speed your date. These first five milestones are where most timelines are won or lost. Use the checklists to lock deliverables and keep vendors honest about scope, risk, and time.

1️⃣ LOI and Commercial Skeleton
The Letter of Intent sets the promise in simple terms: where the fiber starts and ends, when you want service, and how money will move. Treat it as the outline of the job so nobody can change the story later without rewriting this page.
What this step does
  • Names endpoints and any meet-me room you will use
  • Sets a target ready-for-service date and who controls delays
  • States the model you prefer: IRU, lease, or lit wave
  • Calls out any special construction costs and how they will be handled
Ask for these files
  • LOI document with term, bandwidth targets, and pricing approach
  • Rough order of magnitude cost with a line for special construction
  • Draft SLA outline for latency, jitter, packet loss, and MTTR
  • Contact list for design, permits, and construction leads
Special construction cost helper
Buyer NRE after credits
$0
Amortized per month
$0
Tip
Push credits into month one
This is a simple view. Confirm how credits are paid and if any are contingent on milestones.
2️⃣ Desktop Route Study and High-Level Design
Before anyone walks the street, the design team checks maps and data to choose a best path on paper. The goal is to spot bridges, railroads, and busy roads early so the route is short, legal, and easy to permit.
Inputs
  • GIS layers for conduit, poles, utilities, and easements
  • Known restrictions like school-zone work bans and holiday moratoria
  • Existing carrier routes and possible handholes
Outputs
  • Primary and backup paths with kilometers labeled
  • Early bill of materials by segment
  • Risk list ranked by schedule impact
Your ask
  • KMZ or PDF map with all crossings called out
  • Early choice of pole vs conduit by block
  • Photo examples of a typical handhole and manhole
3️⃣ Field Surveys and Make-Ready Discovery
Crews walk the route with measuring wheels and cameras. They confirm where the fiber can enter buildings, where poles have space, and where the ground hides surprises that change cost and time.
What happens
  • Measure lateral distances and pick safest entrance points
  • Request utility locates so no one drills into gas or power
  • Check poles for space, clearance, and load
  • Verify handholes and vaults and take photos
Keep these deliverables
  • Photo set with first handhole and each building entrance
  • Marked drawings with measured depths and offsets
  • Pole survey sheets with make-ready notes
  • Updated risk list with fixes and owners
Watch for private laterals that are not on city maps. These can change the dig plan and budget.
4️⃣ Permits, Rights of Way, and Approvals
Paperwork moves the project. As soon as the route is stable, submit permits so reviewers can start while you finish design details.
Common items
  • City encroachment permits for streets and sidewalks
  • State DOT right-of-way for highways
  • Railroad crossing agreements
  • Pole attachment applications
  • Private easements on campuses or parking lots
Speed helps
  • Complete plan set with plan and profile views
  • Traffic control plan by block
  • Access letters from property owners
  • Environmental or cultural checks when required
Checklist
  • Who submitted each permit and on what date
  • Named reviewer and promised response date
  • How long a resubmittal takes if changes are requested
Permit lead-time estimator
Likely critical path
Estimated weeks to green-light
0
Tip
Submit in parallel
This assumes parallel submittals. The longest item is usually your critical path.
5️⃣ Final Design and IFC Package
The Issued for Construction set is the playbook crews will follow. It nails down where to dig, how to protect traffic, how to splice, and how you will test the finished route.
The IFC set includes
  • Plan and profile drawings for each block or span
  • Splice plan with trays, counts, and labels that match your inventory
  • Bill of materials with part numbers and quantities
  • Traffic control plans and safety notes
Acceptance rules inside
  • OTDR thresholds per span and light-level targets
  • As-built file formats and photo requirements
  • Cutover method of procedure for turn-up
Quick latency estimate
Estimated RTT
0.00 ms
Tip
Shorter path saves delay
Note
Model is conservative
6️⃣ Procurement and Long-Lead Orders
Order the items that take the longest first so they arrive before crews do. Think cable, handholes, vault lids, duct, pull tape, and any optics or shelves for turn-up.
Priorities
  • Place cable and handhole orders as soon as IFC is stable
  • Reserve construction crews to match permit windows
  • Order optics, shelves, and power gear early for cross-connect day
Proof to keep
  • POs and promised ship dates
  • Warehouse receipts when items land
  • Substitution approvals if a part changes
7️⃣ Traffic Control Plan and Construction Schedule
Work happens in the road, so lanes and sidewalks must be protected. A clear schedule with traffic control plans prevents last-minute denials and keeps your crews moving.
What to include
  • Block-by-block control drawings with cones and flaggers
  • Work windows that respect school zones and rush hours
  • Emergency contact info and detour notes
Ask for
  • Weekly schedule with crew counts and locations
  • Daily permit log listing what is active and what expires
  • Photo of the first work zone set up correctly
8️⃣ Civil Construction: Trenching, Boring, Conduit
This is the physical build. Crews trench, bore under roads, and place conduit so the fiber can be pulled later. Good drawings turn into good footage per day.
What good looks like
  • Straight runs where possible with clear depth notes
  • Clean bores under driveways and roads with minimal patches
  • Conduit and pull tape placed and labeled
Your checklist
  • Daily footage report with start and end photos
  • Locations of each handhole and any field change
  • Safety and traffic control verified by photos
Civil build time helper
Estimated crew days
0
Calendar days at 5-day weeks
0
Tip
Add weather float
9️⃣ Aerial Construction: Pole Attachments and Lash
If the route uses poles, crews attach strand and lash fiber along the line. Pole make-ready can be slow, so schedule it early and track it closely.
Watch for
  • Mid-span transfers that need other utilities to move first
  • Clearances at road crossings
  • Correct hardware and bonding at each pole
Proof to keep
  • Pole numbers with photos before and after
  • Any load calculations or clearance sheets
  • List of poles waiting on make-ready
🔟 Laterals and Building Entrances
Each building needs a clean path from the street to your demarc. This usually means a short trench or conduit run, a core drill, proper firestop, and a labeled handoff.
Good practice
  • Shortest safe path with drawings and landlord approval
  • Sealed sleeve at the wall and a proper firestop
  • Demarc in a dry, secure, power-ready location
Ask for
  • Entrance photo set and as-built sketch with measurements
  • Labeling that matches your inventory names
  • Grounding and bonding notes where required
1️⃣1️⃣ Splicing and Enclosures
Splicers join fibers in trays inside sealed closures. Clear labels and a simple numbering scheme save headaches later when you expand or troubleshoot.
What to see
  • Splice plan with tray numbers and positions
  • Closure photos with GPS location
  • Slack loops placed and documented
Quality checks
  • Splice loss within spec on the OTDR
  • Labels match the inventory and maps
  • Closures sealed and mounted correctly
1️⃣2️⃣ Testing and Validation
Testing proves the route performs to spec. The two main tests are OTDR, which checks fiber health, and light-level tests, which confirm the path supports your optics.
OTDR basics
  • Each span is tested from both ends
  • Splice loss and connector loss must be under thresholds
  • Results exported as PDFs and native files
Light levels
  • Transmit and receive levels match your optics data sheet
  • Margin left for future patching and aging
  • Document the exact test gear used
1️⃣3️⃣ As-Builts, GIS, and Documentation
As-builts are the record of what actually got built. You want maps you can open, photos you can trust, and labels that match the route in the ground.
Deliverables
  • GIS files with coordinates for handholes, closures, and slack loops
  • Photo library organized by station and date
  • Label map that matches trays, strands, and ports
Why it matters
  • Speeds repairs after a cut
  • Makes future adds simple
  • Helps insurance and audits
1️⃣4️⃣ Service Turn-Up: Cross-Connects and Optics
This is the handoff to your equipment. You schedule a cross-connect, plug in optics, and pass traffic on a quiet window so you can roll back if needed.
Day-of steps
  • Confirm cross-connect order and location in the meet-me room
  • Verify optics model and patch cords
  • Bring up light and check errors and levels
Monitoring
  • Add the path to your NMS and alarm thresholds
  • Log latency, jitter, and packet loss for a baseline
  • Share graphs with the provider if anything drifts
1️⃣5️⃣ Acceptance, Punch List, and Start of Term
Acceptance starts the clock. You compare the build to the contract, list anything that is not complete, and agree on how and when those items will be fixed.
Before you sign
  • All OTDR and light-level results in your hands
  • As-built maps and photo sets delivered
  • Cross-connect working and monitored
Punch list rules
  • Each item has an owner and a due date
  • Credits or holdbacks if anything blocks service
  • Final acceptance letter when all items are closed
Keep a copy of everything in one folder. Future you will thank present you on cut day.

Close strong by keeping the build simple and visible: one owner, one checklist, one folder for maps, permits, photos, tests, and dates. Track three things weekly, permit status, crew locations, and any design changes and update your calculators when quotes shift. Do not accept service until OTDR and light-level results are in your hands, labels match the maps, and cross-connects pass traffic without errors. Write down who fixes each punch-list item and by when, and use credits or holdbacks if something blocks service. Keep both routes and building entrances truly diverse, and save baseline latency and jitter so you can compare performance later. When everything is documented and measured, your build-to-suit stays on schedule and your network is ready for growth.