When Ticket Volume Exceeds Capacity: The Construction Season Problem Nobody Budgets For

Every spring, the same thing happens.

Construction activity accelerates. Locate requests climb. Ticket volumes that were manageable in March become unmanageable by May. And the response from most operations is the same one it was last year: work longer hours, push crews harder, and hope the backlog doesn’t get bad enough to trigger regulatory attention.

It works until it doesn’t. And when it doesn’t, the consequences compound fast.

The Backlog Arithmetic

The math behind peak season backlogs is straightforward and unforgiving.

A typical locate contractor runs a fixed number of crews. Each crew completes a predictable number of locates per day, field time plus the post-field administration required to document each locate, generate reports, and close tickets. During off-peak months, capacity and demand are roughly balanced. During construction season, demand can spike 40 to 60 percent above the winter baseline while crew count stays flat.

The gap between incoming tickets and completed locates starts small. A few dozen tickets behind on a Monday. A hundred behind by Friday. Two hundred behind the following week. The backlog grows geometrically because every incomplete ticket from today becomes tomorrow’s work on top of tomorrow’s new tickets.

For the contractor, the backlog means overtime costs, crew fatigue, and increasing pressure to cut corners on documentation quality, which is precisely the wrong thing to compromise during the highest-risk period of the year. For the utility, the backlog means delayed construction projects, missed completion windows, frustrated excavators, and regulatory risk if locate response times breach prescribed limits.

The industry’s standard response, hire seasonal staff, addresses one variable but introduces another. Seasonal locators require training, supervision, and time to become productive. By the time a seasonal hire is operating at full capacity, the peak is often half over.

Where the Time Actually Goes

Ask any experienced locator where their day goes during peak season, and the answer is consistent: it’s not the field work that creates the bottleneck. It’s everything that happens after.

A standard locate involves driving to the site, performing the locate, and marking the utilities. That field work takes a relatively predictable amount of time per ticket. What varies wildly is the post-field administration: constructing the sketch, placing dimension lines, adding labels, generating the report, assembling the documentation package, and closing the ticket in the management system.

On a simple residential locate, the post-field work might take 15 to 20 minutes. On a complex commercial or multi-utility locate, it can take 30 to 45 minutes or more. Multiply that by 15 to 20 locates per day and the documentation burden alone can consume three to four hours of a locator’s shift.

This is where the backlog lives. Not in the field. In the office. In the truck. On the laptop at the end of a 10-hour day when the locator is documenting the last five tickets before going home.

The locates that get rushed are the ones documented at 7 PM after a full day. The sketches that get simplified. The dimension lines that get estimated instead of measured. The reports that get generated with incomplete boundary documentation. These are the documentation gaps that show up in post-incident investigations six months later.

The Throughput Question

The conventional approach to peak season capacity is to add people. More crews, more trucks, more locators. It’s the obvious answer and sometimes it’s the right one. But it’s not the only variable.

The other variable is throughput per locator. If each locator can complete their documentation faster without sacrificing quality, the same crew count handles more tickets per day. The backlog shrinks or never forms in the first place.

This isn’t about asking people to work faster. It’s about removing the manual steps that consume time without adding value. A locator who manually constructs sketch boundaries, places dimension lines by hand, types in label text, and assembles report pages is doing work that a system can do in seconds, and do more consistently.

The difference between a locator who spends 20 minutes on post-field documentation and one who spends 8 minutes is 12 minutes per locate. At 15 locates per day, that’s three hours recovered. Three hours that can be redirected to completing additional tickets, or, just as importantly, to going home at a reasonable hour during the most demanding period of the year.

Across a fleet of 50 locators, 12 minutes per locate at 15 locates per day is 150 hours recovered per day. That’s the equivalent of adding 18 to 20 full-time locators to your operation without hiring anyone.

What the Utility Sees

Utilities don’t experience locate backlogs as an internal contractor problem. They experience them as project delays, missed service level targets, and risk.

When a major capital project, a main replacement, a service upgrade, a new subdivision, is waiting on locates to proceed, every day of delay has a cost. Construction crews sitting idle. Equipment on rent. Subcontractors rescheduling. The downstream cost of a locate backlog is almost always larger than the direct cost of the locates themselves.

The utilities that manage this well aren’t necessarily the ones with the most generous LSP contracts. They’re the ones whose contractors have the operational infrastructure to scale with demand. The right technology, the right workflows, and the right documentation systems to maintain quality at volume.

That’s not a technology pitch. It’s an observation from watching this cycle repeat every year for 25 years.

The Question Worth Asking Before May

If your operation ran last year’s peak season ticket volume with no additional staff, how many days would it take before the backlog became unmanageable?

If the answer is less than two weeks, the problem isn’t peak season. The problem is that the baseline operation doesn’t have enough capacity margin to absorb normal demand variation.

The time to solve that is now, before the volume arrives. Not in June when every day of backlog makes the next day worse.

The crews that built capacity before they needed it are about to have a different summer than the ones that didn’t.