Project Scoping for Infrastructure: A Guide

A water main replacement gets scoped at $4 million. The pipe size is right, the length is right, the unit costs are right. Then the design team learns the street is under a five-year paving moratorium, a gas transmission line crosses the alignment twice, and the city wants a richer backfill mix than the estimate assumed. The project scoping wasn't wrong on paper. It was wrong about the ground.

This guide covers what project scoping is, who does it, the steps, and what to check on an infrastructure site before the scope is locked.

What is project scoping?

Project scoping is the process of defining a project's goals, boundaries, work, cost, schedule, and risks before design and budget are locked. The Texas Department of Transportation's project development manual describes it as "determining and documenting a list of specific project goals, objectives, deliverables, costs, outcomes and deadlines."

A good scope answers four questions:

• What problem are we solving? The need, and how success will be measured.
• Where are the limits? The physical extent of the work and what's out of bounds.
• What will it take? The work, the deliverables, and a planning-level cost and schedule.
• What could change it? The assumptions, constraints, and risks.

The output is usually a scoping document, a planning estimate, an initial schedule, and a risk register that the team keeps updating as the project moves forward.

Who does project scoping, and when does it start?

Project scoping starts as soon as a project is identified as a need, well before preliminary engineering. Who leads it depends on the project:

• The utility or agency often scopes its own capital work, such as a main replacement or undergrounding program, before funding is requested.
• Engineering firms scope work when they bid on it, turning an owner's request into a proposed scope of work, fee, and schedule.
• A larger agency may lead scoping for big programs. On a highway widening or port expansion, for example, the transportation or port agency sets the scope, and affected utilities scope their relocations around it.

On many projects, scoping happens more than once: the owner scopes to get funding, then the engineer re-scopes in more detail to price the design. Each pass is a chance to catch what the last one missed.

Why project scoping matters more in infrastructure

Scope changes are one of the main reasons projects run late and over budget. A 2020 study of highway and bridge projects by Kermanshachi and colleagues, published by ASCE, found that changes to project scope are "critical root causes" of delays and cost overruns at state transportation agencies.

Infrastructure adds a problem most industries don't have. The biggest scope risks are often site conditions no one can see from the plan view:

• utilities that aren't where the records say, or aren't in the records at all
• a street that can't be cut for years because it was just repaved
• another agency's project planned for the same block
• permit conditions that change how the work has to be built

When these surface after the scope is set, the result is redesign, change orders, and a budget conversation nobody wanted.

The project scoping process, step by step

Most agencies and owners follow some version of this sequence:

1. Define the need. State the problem, the goal, and how you'll measure success.
2. Set the project limits. Draw the boundary and the candidate alignments. Where there's more than one possible route, plan to compare them before choosing.
3. Gather site data. Pull utility records, aerials, parcels, existing plans, and anything else known about the ground.
4. Identify conflicts and constraints. Check each alternative against utilities, moratoria, nearby projects, crossings, and environmental limits. Some routes will be far more congested than others.
5. Identify stakeholders and permits. List every agency, utility owner, and jurisdiction the project touches, and the permits each will require.
6. Estimate cost and schedule, with contingency. Build a planning-level estimate and schedule, and size the contingency to the risks you found.
7. Document and baseline the scope. Record the scope, assumptions, and a risk register, and get sign-off.

The risk register deserves special attention. On most projects, the risks found during scoping roll up into a master risk register or risk matrix. From there, each group, such as engineering, land and right of way, and permitting, owns and updates its own risks through the life of the project. TxDOT's manual makes the same point: the risk register is a living document, updated at each milestone.

What to check when scoping an infrastructure site

These are the site conditions that most often change an infrastructure scope:

• Existing utilities. What's in the corridor, who owns it, and how reliable the records are. This sets how much survey and subsurface utility engineering (SUE) the project will need. See What Is a Utility Survey? for how that work is done.
• Paving moratoria. Many cities restrict cutting recently paved streets for several years, or require full-width repaving if you do.
• Overlapping capital projects. Another agency's work on the same street can be a conflict or a chance to share a trench and restoration.
• Road, rail, and transit crossings. Each crossing can add a permit, a specialized method like boring, and schedule time.
• Right of way and land rights. Whether the work fits in public right of way, or needs easements from private owners.
• Environmental constraints. Waterways, wetlands, habitat, and contaminated sites.
• Jurisdictions and permit conditions. Which cities, counties, and districts the project crosses, and what each requires. For utility work in paved streets, backfill rules are a common surprise. Some cities accept a low-cement slurry, while others require a richer mix with more sacks of cement per cubic yard. On a large project, that difference adds up fast, and it's sometimes not known until the approved permit comes back.

Common project scoping mistakes

The same mistakes show up across many infrastructure projects:

• Scoping from old records. Utility maps and as-builts can be decades out of date. A scope built on them inherits their gaps.
• Finding moratoria and permit conditions at permitting. By then, the design and budget are set. Check moratoria and typical permit requirements, such as backfill and restoration standards, during scoping.
• Under-scoping survey and SUE. Trimming field work to hit a budget often moves the cost into change orders later.
• Skipping risk contingency. A single-number estimate with no contingency hides risk instead of managing it.
• Taking a bid at face value. Some bidders price exactly the scope they're given, knowing gaps will turn into change orders later. Owners should value a bid that points out mistakes or oversights in the scope. It's a sign the bidder read it closely.

Scoping a single project vs. a portfolio

Scoping one project well is hard. Utilities and agencies with a capital program have a bigger opportunity: scoping projects together.

Looking across a portfolio shows where projects overlap. Two projects on the same street can be bundled to share excavation and paving. A project on a street that comes out of moratorium next year can be sequenced to that window, instead of fighting the restriction now. These decisions can only be made when every project's limits and constraints are visible at the same time.

How CivilGrid helps with project scoping

Most of the site data that changes a scope already exists. The problem is that it's scattered across dozens of utilities, cities, and agencies, so it often isn't gathered until design is underway. We call this the pre-construction research tax.

CivilGrid sources utility maps and as-builts directly from the owners, with chain of custody documentation for every record, and puts them on one map with the rest of the site's context. Teams can see which utilities and agencies sit along each alignment they draw. They can also spot potential conflicts around a project, such as paving moratoria and nearby paving projects, road, rail and transit crossings, and the jurisdictions a project spans. Coverage depends on the agency data available in each area.

CivilGrid cuts research time, reduces rework and dig-ins, and helps teams scope accurately before committing work. It doesn't replace survey, SUE, or 811. It gives them a better starting point.

Project scoping FAQ

What is the difference between scope and scope of work?

The scope is the overall definition of a project: its goals, limits, deliverables, cost, schedule, and risks. A scope of work is a document, usually part of a contract, that describes the specific tasks a firm will perform, with deliverables and timelines.

What is scope creep?

Scope creep is the gradual growth of a project's work beyond what was originally agreed, without matching changes to budget or schedule. In infrastructure, it often comes from site conditions found late, such as unknown utilities or permit requirements, which turn into change orders.

Who is involved in project scoping?

Project scoping usually involves the project owner's project manager, planners, and engineers, plus specialists in right of way, environmental, permitting, and utility coordination. Utility owners, cities, and other agencies along the project are key stakeholders.

What is a scoping document?

A scoping document records a project's agreed scope: the need, limits, deliverables, assumptions, planning estimate, schedule, and known risks. It becomes the baseline that later changes are measured against.

Scope your next project with the full picture

Ready to see what's on and under your next site before the scope is locked? Book a demo, or read What Is a Utility Survey? and browse our preconstruction glossary.

The short version

• Project scoping defines a project's goals, limits, work, cost, schedule, and risks before design and budget are locked.
• In infrastructure, the biggest scope risks are site conditions you can't see: buried utilities, paving moratoria, overlapping projects, and permit conditions.
• The best defense against scope creep is finding conflicts and constraints at scoping, then tracking them in a living risk register.