# Fiber Network Survey Project Management: Scope, Crews, Access, and the Design Handoff

**Title tag:** Fiber Network Survey Project Management 2026
**Meta description:** fiber network survey project management: unit definitions, crew schedules, pole-owner access, daily QA gates, exception queues, and the design handoff.
**Author:** Devin Martinez
**Published:** September 25, 2026  
**Last updated:** September 25, 2026  
**Category:** OSP Engineering & Field Services
**URL:** https://draftech.com/blog/fiber-network-survey-project-management
**Primary keyword:** fiber network survey project management
**Word count:** 2820
**Read time:** 11 minutes

![Two field engineers organize survey gear at a pickup tailgate before a route walk.](../../blog/img_fiber_network_survey_project_management.webp)

---

A survey can close the last assignment on Friday and still leave design idle on Monday. The usual cause is not a missing photograph. It is a fielding phase that was never run as a project. Crews moved by mile markers while pole-owner access sat in a spreadsheet. The daily report counted every synced record as done.

This guide covers project management of the fielding phase only. We define survey units, then schedule crews against access rather than against a mile target. Daily QA and an exception queue feed the design handoff. Data-platform governance and construction-build PM are different jobs.

## What Fiber Network Survey Project Management Controls

Fiber network survey project management is the fielding-phase control of survey units and crew assignments against pole-owner access. Daily QA and an exception queue feed the design handoff. 47 CFR 1.1411 gives a utility 45 days to complete a Regular Order survey after a complete application. That clock bounds the window. It does not start the crew.

The FCC Fifth Report and Order, FCC 25-38 in WC Docket 17-84, published in the Federal Register on August 26, 2025 (90 FR 41726), amended 47 CFR 1.1411. The PRA-covered amendments took effect May 7, 2026 under Wireline Competition Bureau public notice DA-26-446. A Regular Order still carries a 45-day survey. A Large Order, above the lesser of 3,000 poles or 5 percent of the utility's poles in a state, carries 90 days. The utility must notify the new attacher within 15 days of a complete application if it knows the survey deadline cannot be met.

Those clocks bind the pole owner under 47 CFR 1.1411 as amended, and they still do not write your crew calendar or tell a technician which gate is open on Tuesday. A fielding plan that treats the 45-day figure as a start order will still stall when a joint-meet has not been granted or a private-road key is missing. The PM job is to occupy the window with released work, not to confuse a regulatory deadline with production.

### The utility clock is not a crew start

We run fielding as our own service, not as a subcontracted collection pass. Engineering stays in-house under the [Draftech partner model](/about), so the person who accepts the package is the person who will design from it. Device output is evidence. It is not a schedule. Our [IKE survey services buying test](/blog/ike-survey-services) covers the record itself. This page covers the operating system that decides when a crew may start a unit and when that unit may go to design.

The six controls below are the fielding-phase work, and each later section expands one row. Scope and units come first because a crew calendar cannot repair an unbounded assignment. Access sits beside the schedule because a released mile with a locked gate is not a released assignment. Daily QA exists so design does not become the first review. The exception queue exists so a held unit has an owner before Friday. The handoff is the only place an engineer should meet a held unit, and then only as a named hold, never as a surprise inside an otherwise complete folder. Read the table as a map of releases, not as a dashboard of completion percentage.

**Table: Fielding-phase controls and what each one actually releases**

| Control | What it releases | Cadence | Common failure |
| --- | --- | --- | --- |
| Scope and units | Crews may be assigned | Before mobilization | Mile markers treated as units |
| Crew schedule | An assignment may start | Weekly, then daily | Calendar ignores access holds |
| Pole-owner access | The crew may occupy the pole | Per owner rule | Verbal clearance treated as a release |
| Daily QA | Records enter the review queue | Same day | Synced equals done |
| Exceptions | Held work has a named owner | Continuous | A notes field used as a queue |
| Design handoff | An engineer may start | Per package | Design starts on held units |

## Define Survey Units Before You Schedule Crews

A unit is the smallest route piece that can be assigned on its own, then reviewed and released without opening the next mile. It is not a mile. It is not a shapefile color. A railroad or irrigation crossing often stays one unit because a single access hold blocks the whole passage. An aerial run may follow one pole and the spans that depend on it, because a missing neighbor record makes the pole unusable for design even if the form is complete.

Rural aerial work in the 50-mile class has a published scoping duration of 1 to 2 days before the first crew rolls. That is the unit-definition pass, not a padded kickoff. The split follows access and decision boundaries: public road and the crossings that need a separate owner contact. A crew that starts on an unsegmented 50-mile line will look busy. Design will still wait on the pieces that were never bounded.

Application counters follow those units. If a pole-attachment filing later needs a count, we report the units the owner asked for. We do not let a filing counter redefine the field assignment after mobilization. Changing the unit mid-route is a controlled scope revision. It is not a hallway request to collect a little more while production continues.

> **Unit rule:** if a reviewer cannot accept or return the piece without opening the next mile, it is not a unit yet. Split it before the crew leaves the shop.

### Freeze the schema with the units

The form travels with the unit. We lock the required fields and photo views, plus the exception codes and receiving format, before assignment. A later owner request for an extra attribute is a schema revision with an effective date. Completed units keep the form they were collected under unless we issue a named backfill. Mixing two form revisions in one design batch is how a complete-looking export becomes an unusable model.

Inherited plant is a separate question. Our [existing infrastructure survey guide](/blog/osp-existing-infrastructure-survey-guide) covers reuse decisions on records you did not collect. Fielding PM still has to say which of those inherited assets are in this assignment and which stay out of scope. Context-only plant is marked, not edited. A crew that edits a pole the assignment never owned will collide with the next visit.

## Crew Scheduling and Pole-Owner Access Rules

Schedule the crew to the access that is actually released. A linear mile target that ignores the owner calendar will produce a high pole count on the wrong side of a locked gate. The assignment package names the route segment and the expected asset set. It also names the schema version and the access state. Visible-but-out-of-scope plant stays marked that way so two crews do not edit the same pole while a short side road receives no visit.

A 1,000-pole survey in rural or mountainous conditions sits in the 5-to-7-week range we already publish. Walking speed is not the constraint. Pole-owner access is. Advance notice and private-road holds set the calendar. Treating the route as 1,000 poles at a fixed daily rate forecasts a finish date the access rules cannot support.

Pole-owner clocks are not the same as crew clocks. Our pole-owner make-ready response-time guide walks the 1.1411 phases the utility must meet. Fielding PM still needs the owner's own access instructions: where to stand and who may escort, plus the notice rule and what happens when a meet is cancelled. A verbal "you're fine" from a local contact is not a release, even when that contact has opened the same road for the last three jobs and the crew is already on the mile. The assignment stays held until the documented rule is satisfied.

### Access released, then the assignment

OSHA 29 CFR 1910.268, Telecommunications, is the federal rule covering specified work conditions and practices at telecommunications centers and field installations. Applicability follows the work performed and the employer's program. It is also a scheduling constraint. If the only measurement setup would put a technician in a live traffic lane or inside a clearance the safety plan does not allow, the pole is an exception, not a forced complete. We do not recover a day of production by manufacturing a record from an unsafe stance.

Weather and a cancelled escort produce different holds, and treating both as a generic missed-production day hides which one can be cleared by a phone call versus which one needs a new access window. The schedule should show them as holds, not as missed production. A crew that is sent to a held unit to "see if they can get it" will either take a bad record or burn a day that belonged to a released assignment. We reassign to released units and leave the hold on the exception queue with a next action.

## Daily QA Gates and Exception Handling

The same-day gate is a sample, not a full engineering acceptance. Our field lead reviews identity discipline and photo-to-asset links on the first records from that day's assignments. Open exceptions are part of the same pass. The point is to catch a repeated capture error while the location is still reachable. A Friday dashboard of completion percentage cannot do that, because the crew has already left the span where a recycled pole ID or a missing photo view could still have been fixed in minutes.

One thing I have always over-weighted is poles per day. It looks like production. It hides access holds and QA returns until the design engineer opens the package. We still track daily volume because a stalled crew is a real cost. We no longer treat volume as the release metric. A day that produces a green tracker and recycled IDs is a failed day.

> **Same-day rule:** do not release the next assignment until the sample from this one has a named disposition. Synced is a transport state. It is not QA.

On a multi-crew overbuilder assignment, the first-day sample exists to catch recycled pole IDs before the second crew rolls. Stop that assignment until the naming rule is reissued. The delay is hours, not weeks. Letting the second crew continue writes the same defect down a parallel road. That is the whole argument for a daily gate: cheap correction while the trucks are still in the workzone.

### An exception needs an owner

Access denied, asset not found, unsafe setup, and obscured hardware lead to different next actions. A free-text notes field cannot run that queue. We use a controlled exception type with a short narrative, plus a responsible role and a status. No one should have to read every comment to discover which units block design. Free text explains the condition. The code drives the work.

Our [fiber field condition report services](/blog/fiber-field-condition-report-services) treat the unit-level finding as evidence for a named decision. Fielding PM uses the same discipline at route scale: every held unit has an owner and a next method. Sending the same crew back with the same photo request usually reproduces the first gap. The return assignment states the missing view or the alternate method, or it stays held.

## Fiber Network Survey Project Management Handoff to Design

Fiber network survey project management pays off at the handoff, or it does not. The receipt names the schema version and the reviewer. It also names the intended use and the units that remain held. Accepted units may enter design. Held units stay out of the model. A package that arrives as one complete folder with no exception register forces the engineer to reconstruct the fielding decisions from filenames.

We test the export in the receiving GIS or CAD path before calling the package delivered. One ordinary unit and one difficult exception are enough to prove that identifiers and geometry survived the translation. Photos and status have to survive it too. If either loses its key or its limitation, the export has not passed. Device dashboards are not that test, because a green sync light can still hide a dropped key or a photo that never attached to the unit it was supposed to document.

Draftech's [OSP field survey services](/services/field-survey) put fielding control on the same desk as in-house engineering. A green tracker is not the deliverable. The deliverable is a package the receiving engineer can open without rebuilding fielding decisions from a file dump. Active in 24 states. Available across all 50 U.S. states.

## Recommendation: Next Steps by Reader Type

Pick the operating recipe that matches the route you actually have, not the software stack a vendor demoed, because a Regular Order with one crew fails in a different place than a multi-crew overbuilder with recycled IDs.

**Small ISP on a single-state Regular Order:** freeze the units and the form before the first truck rolls. One crew is enough when access is simple. Keep the daily sample. Require a handoff receipt even if the export is a geopackage and a spreadsheet. Complexity should follow risk, not software ambition.

**Regional overbuilder, several crews:** assignment control is the job. Publish the access calendar with the crew calendar. Run the same-day sample on every crew, not on a blended dashboard. Hold recycled IDs at the assignment, not at design. The exception queue has to be visible to the person who can change the next day's work.

**Cooperative or pole-owner inventory:** prioritize identity and access over attachment-level collection you will not use. Do not buy a make-ready fielding plan for an inventory decision. Keep an exception model that distinguishes blocked observation from a genuinely absent asset, then hand the accepted inventory to the owner system with limitations intact.

If the current fielding plan cannot tell an engineer which work is usable tomorrow, the package is not ready. Email [info@draftech.com](mailto:info@draftech.com) with the route class and the decision the survey has to support. We will say whether the next action is a schema freeze or a return assignment.

Before mobilizing the full fielding program, an owner can test Draftech on a qualifying route. Through our [free design offer](/free-design), 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.

> **Talk to our field survey team about your fielding plan.** Bring the route file and the pole-owner access rules so the review starts with the real interfaces.

## Frequently Asked Questions

**What is fiber network survey project management?**

Fiber network survey project management is the fielding-phase control of survey units, crew assignments, pole-owner access, daily QA, exceptions, and the design handoff. 47 CFR 1.1411 gives a utility 45 days to complete a Regular Order survey after a complete application. The fielding plan occupies that window. A synced form is not a finished day.

**How should a fiber survey unit be defined?**

Define a unit as the smallest route piece that can be assigned, reviewed, and released on its own. A crossing may stay one unit because one access hold blocks the passage. An aerial run may follow a pole and the spans that depend on it. The engineering decision sets the unit. Application counters follow those units, not a mile marker.

**How do pole-owner access rules change crew scheduling?**

Schedule the crew to the access that is actually released, not to a linear mile target. A pole owner may require advance notice or a named escort. OSHA 29 CFR 1910.268 also limits where a technician may stand. If access is not released, the assignment stays held. Counting that day as production hides the real constraint.

**What belongs in a daily field-survey QA gate?**

The same-day gate reviews identity discipline, required fields, photo-to-asset links, and open exceptions on a sample from that day's assignments. It is not a full engineering acceptance. The reviewer names the disposition before the next assignment is released. A first-day sample that catches recycled IDs is worth more than a Friday dashboard of completion percentage.

**When is a survey package ready for design?**

A package is ready when accepted units and open exceptions are visible in the receiving GIS or CAD path, with known limitations stated on the receipt. The handoff names the schema version and the intended use, with the reviewer on the receipt. Design may start on accepted units while held units stay out of the model. Completeness of the last sync is not the test.

**Does the FCC 45-day survey clock start the field crew?**

No. 47 CFR 1.1411, as amended by FCC 25-38, gives the utility 45 days for a Regular Order survey after a complete application, 90 days for a Large Order, and a 15-day notice if the deadline cannot be met. Those clocks bind the utility. Your crew starts when units, access, and the safety plan are released.