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.
- 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
- 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
- GIS layers for conduit, poles, utilities, and easements
- Known restrictions like school-zone work bans and holiday moratoria
- Existing carrier routes and possible handholes
- Primary and backup paths with kilometers labeled
- Early bill of materials by segment
- Risk list ranked by schedule impact
- 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
- 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
- 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
- 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
- Complete plan set with plan and profile views
- Traffic control plan by block
- Access letters from property owners
- Environmental or cultural checks when required
- Who submitted each permit and on what date
- Named reviewer and promised response date
- How long a resubmittal takes if changes are requested
- 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
- OTDR thresholds per span and light-level targets
- As-built file formats and photo requirements
- Cutover method of procedure for turn-up
- 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
- POs and promised ship dates
- Warehouse receipts when items land
- Substitution approvals if a part changes
- Block-by-block control drawings with cones and flaggers
- Work windows that respect school zones and rush hours
- Emergency contact info and detour notes
- 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
- Straight runs where possible with clear depth notes
- Clean bores under driveways and roads with minimal patches
- Conduit and pull tape placed and labeled
- Daily footage report with start and end photos
- Locations of each handhole and any field change
- Safety and traffic control verified by photos
- Mid-span transfers that need other utilities to move first
- Clearances at road crossings
- Correct hardware and bonding at each pole
- Pole numbers with photos before and after
- Any load calculations or clearance sheets
- List of poles waiting on make-ready
- 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
- Entrance photo set and as-built sketch with measurements
- Labeling that matches your inventory names
- Grounding and bonding notes where required
- Splice plan with tray numbers and positions
- Closure photos with GPS location
- Slack loops placed and documented
- Splice loss within spec on the OTDR
- Labels match the inventory and maps
- Closures sealed and mounted correctly
- Each span is tested from both ends
- Splice loss and connector loss must be under thresholds
- Results exported as PDFs and native files
- Transmit and receive levels match your optics data sheet
- Margin left for future patching and aging
- Document the exact test gear used
- 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
- Speeds repairs after a cut
- Makes future adds simple
- Helps insurance and audits
- 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
- 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
- All OTDR and light-level results in your hands
- As-built maps and photo sets delivered
- Cross-connect working and monitored
- Each item has an owner and a due date
- Credits or holdbacks if anything blocks service
- Final acceptance letter when all items are closed
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.

