Telecom and infrastructure project management: multi-phase tracking and field operations

Telecom and infrastructure project management is the coordination of physical buildouts, such as fiber routes, tower sites, and network upgrades, through a fixed sequence of phases: design, permitting, procurement, construction, testing, and handover. Field crews do most of the work at dispersed sites. Success depends on tracking phase-gate dependencies, because a permitting delay pushes back everything after it.

Most project management advice assumes a desk-based team, a flexible timeline, and people you can reach in a chat thread. Telecom and infrastructure delivery has none of those. The work happens at hundreds of physical sites, the schedule is gated by approvals the project team does not control, and the people doing the work are often subcontractors standing in a trench with patchy signal.

In Birdview’s own sales conversations, telecom and infrastructure buyers describe two problems that generic tools miss: tracking projects that move through many phases and coordinating field operations. This article covers both. It explains the six-phase structure, why field coordination is a different problem, how to see a portfolio of many concurrent sites, and where execution usually breaks.

If your projects are better described by permit numbers and site visits than by sprint boards, this article is written for you. One note on terms: “infrastructure” here means physical network and construction work, not IT infrastructure such as servers or cloud environments.

What are the phases of a telecom or infrastructure project?

Most telecom and infrastructure projects move through the same six phases, and the sequence itself is what needs managing. Each phase has its own owner, typical duration, and exit criteria. A slip in an early phase travels downstream into every phase after it.

Design and engineering

The design phase covers site surveys, network or structural design, and engineering sign-off. Its gate is an approved design package that is complete enough to submit for permits.

Design errors are the cheapest problems to fix here and the most expensive to find later. A routing conflict spotted on a drawing costs an afternoon. The same conflict found by a crew in the field costs a re-permit, a re-design, and idle labor. Reviewing constructability during design catches many of these conflicts before the package leaves the office.

Permitting and regulatory approval

Permitting is the phase the project team controls least, which makes it the highest-leverage phase to track proactively. Submissions go to municipalities, utilities, railways, and regulators, and each sets its own review clock.

Permitting clocks differ by jurisdiction, and Canadian rules are more defined than many teams assume. Under ISED’s antenna siting procedure, CPC-2-0-03, land-use and public consultation is expected to finish within 120 days. That clock starts only once every plan the land-use authority requires has been formally submitted.

Ontario goes further for provincially designated broadband projects, part of a nearly $4 billion commitment to connect every region by the end of 2028. The province’s Building Broadband Faster guideline, version 5.0 (August 2026), sets service levels for each step. The table combines those with the federal antenna clock:

One clock rule changes how teams should submit. When an Ontario municipality finds a material deficiency, the review does not resume where it stopped; it restarts at day 1 after resubmission. A complete first package is worth more than a fast one.

Rail crossings are slow on both sides of the border. Ontario’s guideline flags railway permits for CN, CPKC, and Metrolinx as having longer approval timelines and offers a turnkey crossing process. In the US, a 2024 GAO review found federal agencies missed the 270-day statutory deadline on more than one-third of communications siting applications. At a February 2026 panel reported by Broadband Breakfast, Conterra Networks cited an average of 12 to 15 months for railroad crossing permits.

A permitting delay does not push back one phase. It pushes back procurement deliveries, crew bookings, testing windows, and handover dates in a chain, the same compounding pattern described in how schedule slippage spreads. Crews and equipment booked against the original date either sit idle or get rebooked at short notice.

Practical implication: track permit status as its own portfolio-level view, with submission date, agency, expected response date, and days outstanding. Buried inside a generic task list, a permit looks like one small task. Its downstream impact is far larger than its size on a Gantt chart.

Procurement

Procurement covers ordering cable, electronics, poles, enclosures, and specialized equipment, often with lead times of several months. The gate is having materials on site, or firmly scheduled, before the crew arrives.

Procurement and permitting usually need to run in parallel, not in series. Teams that wait for every permit before placing orders stack two long delays on top of each other. The trade-off is real: ordering early ties up cash and storage if a permit is denied. Most mature teams order long-lead items once a design is approved and permit risk is known, and hold commodity items until approvals clear.

Construction and installation

Construction is where field operations dominate: crews on site, physical work, and the most exposure to weather, site access, and subcontractor schedules. The gate is a physically complete installation ready for testing. The next section covers why coordinating this phase is a different problem from office-based delivery.

Testing and commissioning

Testing verifies that the built infrastructure meets technical and regulatory specs before it goes live. Fiber gets loss and continuity tests; tower and radio sites get performance and safety checks.

Treat testing as a true gate, not a formality before handover. A failed test can send a crew back to a site the schedule shows as finished. Teams that skip or rush this gate move defects into the client handover, where fixing them costs more and damages trust. Setting testing as a formal milestone with sign-off criteria keeps it from being skipped when the schedule is tight.

Handover

Handover is the formal transfer to the client or operating entity, with final documentation and close-out. Client sign-off, final billing, and a lessons-learned review work the same way here as in any other service delivery engagement.

What is specific to this vertical is the paperwork. Handover packages often include as-built drawings, permit close-out records, and test certificates tied back to the permitting and testing phases. Collecting these during the project, not at the end, is what makes handover take days instead of weeks.

Why are field operations a different coordination problem?

Field operations are harder to coordinate than office work because the constraints are physical, not calendar-based. A crew’s availability depends on where it is, what the weather allows, whether the site is accessible, and whether the right equipment is there. A free slot in someone’s calendar means little if the crew is three hours away.

Four variables shape almost every field schedule, and most generic project tools model none of them well:

• Travel time between sites. A crew that finishes a splice in one town cannot start a tower job 150 km away the same afternoon. Schedules that ignore drive time overstate real capacity.
• Weather windows. Aerial work, trenching, and tower climbs can stop entirely in high wind, frozen ground, or lightning. A week of rain removes capacity that no reassignment can recover.
• Equipment availability. A bucket truck, directional drill, or fusion splicer is often the true bottleneck, not a person. Two crews cannot use one drill on the same day at sites 50 km apart.
• Subcontractor commitments. Many crews are not the firm’s own employees. They work against purchase orders and committed windows, so a reschedule is a commercial conversation, not a task reassignment.

Equipment is the variable teams most often leave out of planning. Specialized gear is a resource with its own calendar, cost rate, and maintenance downtime, just like people, as the breakdown of resource types in project management shows. Field crew and equipment capacity also behave differently from billable-staff capacity: they are lumpy, location-bound, and weather-dependent. Modeling them as their own capacity category, rather than as hours in a staff pool, is the core idea behind resource capacity management applied to field work.

Mobile access decides whether field data exists at all. Crews update status from a phone at a job site, often with weak or no signal. A tool that only works well on a desktop will not get used in the field. The result shows up back at the office as stale status: sites marked “in progress” that finished last week, or “complete” sites that still need a return visit. Offline-capable mobile updates, photo uploads, and short status fields that take under a minute to fill in are what keep field data current.

When field status goes stale, the cost is not just reporting quality. Dispatchers book crews to sites that are not ready, and project managers chase updates by phone instead of planning the next week.

How do you get portfolio visibility across many concurrent sites?

Portfolio visibility in telecom and infrastructure means seeing how many sites sit in each phase right now, not just the status of individual projects. A rollout can include dozens or hundreds of sites or route segments, each at a different phase. At that scale, a project list stops being useful.

The questions a PMO director or operations leader actually asks sound like this: How many sites are stuck in permitting? Which sites are permit-ready but have no crew assigned? Which completed installs are waiting on testing? These are phase distribution questions, and they need a phase-distribution view to answer.

Here is what a simple phase-distribution snapshot looks like for a hypothetical 120-site fiber rollout:

Read site by site, this portfolio looks like 41 separate permitting conversations. Read by phase, it shows that 23 permits are overdue at once, which usually points to a single agency, a missing document type, or a submission pattern the team can fix in one move. The same view shows 18 completed sites waiting on testing, which means testing capacity, not construction, is the next constraint.

The same principle of portfolio-level visibility applies across professional services. In this vertical, it takes a specific form: phase distribution at scale, refreshed as often as field data allows. Useful portfolio dashboards for this work typically combine three views: sites by phase, days in current phase against target, and ready-for-crew sites with no assignment.

Scale makes this non-optional. Advanced 1, an engineering services firm for the telecom industry, completes more than 5,700 projects and 24,000 tasks per month. At that volume, nobody can track status from a spreadsheet or a weekly call; phase-level reporting is the only practical way to see where work is piling up.

Where does telecom and infrastructure project execution usually break?

Most telecom and infrastructure delays trace back to a handful of repeatable failures, and almost all of them are visibility problems before they are field problems. Permitting is the most common. The Fiber Broadband Association’s 2025 deployment cost report, as summarized by the James Madison Institute in April 2026, found that nearly half of broadband deployers had projects delayed by permitting, and 62% expected more of the same.

The same analysis describes a rural cooperative in Monroe County, Michigan, that needed more than 100 permit applications for the first 68 miles of a fiber network. Each county agency accepted only two applications at a time, which pushed construction back at least a year. That is a sequencing problem a project team can only manage if it sees it early.

The failure patterns below show up repeatedly:

• Permitting delays discovered late. Nobody tracks regulatory status as a portfolio metric, so a stalled permit surfaces only when a crew is already booked. Consequence: idle crews and rebooking fees.
• Incomplete permit packages. Teams submit fast instead of complete. Under Ontario’s rules, a deficient application restarts its review clock at day 1. Consequence: a 10-day review turns into a month.
• Procurement run strictly after permitting. Orders wait for every approval, so a three-month lead time stacks on top of a four-month permit. Consequence: months added to the schedule for no technical reason.
• Locates requested for the whole route at once. In Ontario, a completed locate stays valid for a minimum of 60 days, and faded markings count as expired. Consequence: blanket requests expire before crews reach later segments, and work waits on fresh locates.
• Stale field status. Crews have no fast way to update status from the job site. Consequence: the office plans next week from last week’s data.
• Equipment double-booked across sites. Capacity planning tracks people but not the drill, truck, or splicer that is the real constraint, which is how resource overbooking shows up in field work. Consequence: a crew arrives with no equipment and loses the day.
• Testing treated as a formality. Testing gets compressed when the schedule slips. Consequence: defects reach handover, where fixes cost more and the client notices.
• Close-out documents collected at the end. As-builts, permit close-outs, and test certificates are gathered only after construction. Ontario’s designated projects, for example, expect a notice of work completion and as-built drawings within 15 to 20 business days. Consequence: final invoicing waits weeks on paperwork.

Bringing phases and field work into one view

Telecom and infrastructure projects succeed or slip on three things: treating permitting as the phase to watch most closely, coordinating field crews and equipment as a physical capacity problem, and reading the portfolio by phase distribution instead of one site at a time. Teams that get these right spot backlogs while there is still time to resequence work.

The next step is usually structural: setting up the six phases, permit tracking, and field updates in one system so the phase-distribution view builds itself. Birdview’s telecom project management software is organized around exactly these phases and field realities. Teams whose immediate question is how to plan crews and equipment can start with capacity management for field resources.

For Canadian carriers and contractors on publicly funded builds, where project data lives matters as much as how it is tracked. Permit records, as-builts, and crew data often fall under public program rules, which is why many of these teams choose Canadian project management software with Canadian hosting.

FAQ

What makes telecom project management different from standard project management?

Telecom project management differs in two ways. Projects follow a fixed phase-gate sequence where outside agencies control key approvals, so one permitting delay shifts every later phase. And most work happens through field crews at dispersed sites, constrained by travel, weather, equipment, and subcontractor windows rather than calendar availability. Standard project management advice assumes neither condition.

How do you track multi-phase infrastructure projects?

Track multi-phase infrastructure projects with a phase-distribution view: a count of sites in each phase, days spent in the current phase against target, and sites ready for the next gate. Give permitting its own tracker with agency, submission date, and days outstanding. This approach exposes systemic bottlenecks, such as one agency holding 20 permits, that site-by-site reports hide.

How do field crews update project status without office access?

Field crews update status through mobile apps built for job sites. The tools that get used work with weak or no signal, sync when the connection returns, and take under a minute per update. Photo uploads and simple status fields replace long forms. If updating requires a laptop, field status goes stale and office planning runs on outdated data.

Why do permitting delays affect the whole project timeline?

Permitting delays affect the whole timeline because later phases depend on approvals. Procurement deliveries, crew bookings, testing windows, and handover dates are all scheduled against the expected permit date. When a permit slips by three months, each of those commitments must move, and crews or equipment booked against the original date either sit idle or need rebooking at extra cost.

How long does telecom permitting usually take?

Telecom permitting ranges from two weeks to more than a year, depending on the jurisdiction and crossing type. In Ontario, municipalities must review complete permits for designated broadband projects within 10 to 15 business days, while ISED expects antenna siting consultation to finish within 120 days. In the US, federal agencies missed a 270-day deadline on over one-third of applications, and railroad crossings can take 12 to 15 months.