How Excavators Delay Projects by Waiting Too Long to Schedule Locate Requests
- sdmac2
- Aug 18
- 9 min read
A crew can lose a full day before the first bucket hits the ground. Not because the machine broke down. Not because the operator was late. The delay often starts earlier, when the locate request was scheduled too late, too large, or too far out of step with the real work plan.
Utility locating is not just a box to check before digging. It is part of production. When excavators wait until the last minute and submit one weekly request due in two days, they create a bottleneck that slows down the entire project. If the crew cannot realistically complete the planned excavation in that short window, the schedule starts to fall apart.
A better approach is to plan locate requests on a rolling basis. That means scheduling work every day, often a week out, so each dig area is ready when the crew reaches it. The goal is simple: keep locates ahead of the machines without flooding the system with work that is not ready to dig.
Locate requests should match the excavation schedule
A locate request works best when it follows the actual excavation plan. The request should cover the area where digging will happen, within the timeframe when the crew can do the work.
Problems start when the request does not match reality.
A contractor may submit one large locate request for a long stretch of work, due in two business days, even though the crew can only excavate a small section each day. On paper, the request looks efficient. In the field, it creates confusion.
The locate technician may have to mark more area than needed right away. Marks can fade, get covered, or become unclear before the crew reaches later sections. Weather, traffic, grading, and other trades can damage the markings. By the time the crew is ready to dig, the information may no longer be useful.
That leads to repeat calls, remark requests, and idle equipment. The excavator waits because the locate was treated as a single event instead of a continuing part of the schedule.
A daily rolling plan works differently. The project team looks ahead and schedules locate requests in smaller, realistic segments. If the crew will dig on Monday in one area, Tuesday in the next, and Wednesday farther down the line, the requests should mature in that same rhythm.
The result is cleaner:
Crews know where they can work each day.
Locate technicians can focus on areas that are truly ready.
Marks are fresher when excavation begins.
The project avoids stop-and-start digging.
This is especially important on utility, road, fiber, sewer, water, and site development projects where work progresses in sections.
The two-day mindset creates avoidable pressure
Many excavators think of the locate timeline as a minimum waiting period. In many parts of the United States, a common rule is to notify the 811 center at least a set number of working days before digging. The exact timing and rules vary by state, utility owner, and type of work.
The mistake is treating the minimum notice as the planning standard.
If a ticket is due in two days, that does not mean the project is ready to dig productively in two days. It only means the locate process may satisfy the required notice period, assuming there are no issues.
A lot can happen between request and excavation:
The locate area may be too broad or unclear.
Access may be blocked.
The work description may not match the field conditions.
Utilities may need extra time for complex facilities.
Weather may slow marking or wash away paint.
Crews may shift to another priority.
The site may not be ready when the locator arrives.
When excavators wait until the minimum window, every small issue becomes a schedule problem. There is no buffer. The field team either waits, moves to another task, or digs later than planned.
That delay spreads. One missed day can affect trucking, pipe delivery, paving, backfill, traffic control, inspection, and restoration. A locate request may seem like a small administrative step, but it can control the pace of the whole job.
Minimum notice keeps the work legal. Better scheduling keeps the work moving.
Large weekly requests can slow everyone down
Submitting a single weekly request can feel efficient. One ticket, one due date, one task off the list.
But efficiency in paperwork is not the same as efficiency in production.
A large weekly request often asks locators to mark more than the crew can dig before the marks become stale or disrupted. It can also make the request harder to understand. If the description covers too much ground, the locator may spend extra time figuring out where the real excavation will happen.
That creates problems for both sides.
For excavators, broad requests can lead to:
Delayed responses when the request is complex.
Marks that do not match the immediate work area.
More time spent verifying what was marked.
More remark requests.
More crew downtime.
For utility owners and locate teams, broad requests can lead to:
Extra mileage and field time.
Marking areas that will not be excavated soon.
Increased risk of marks being destroyed before use.
Trouble prioritizing urgent, active work.
More return visits to the same site.
A weekly request can work for small, contained jobs where all excavation will happen in a short period. It breaks down when the project covers multiple days of moving excavation.
A rolling request plan helps avoid that. Instead of forcing one ticket to cover too much work, the project creates a steady pipeline of locate-ready areas. Each request is tied to a reasonable section of work and a realistic start date.
That does not mean submitting careless or duplicate tickets. It means planning with discipline. A rolling plan should be specific, organized, and based on real production.
A rolling one-week lookahead keeps crews working
The best locate schedules are built from the same lookahead used to plan labor, equipment, materials, and inspections.
If the crew needs locates ready next Monday, the request should not be an afterthought on Thursday or Friday. It should already be part of the plan. Many excavation teams benefit from reviewing the next week of work every day and submitting locate requests for the next planned segment.
That creates a rhythm:
Poor planning pattern
Better planning pattern
Submit one large request once a week, due in two days, then hope the crew can finish everything before conditions change.
Submit focused requests daily for work planned several days ahead, so locates mature in sequence with the excavation schedule.
The rolling approach gives the crew room to handle normal jobsite changes. If Monday’s work slips, Tuesday’s locate area may still be ready. If production moves faster than expected, the next area is already in the pipeline.
This matters because excavation rarely moves in a perfectly straight line. Crews hit rock. Spoils pile up. Water shows up. A driveway needs access. A delivery arrives late. An inspector asks for a change. When the locate plan is too tight, every field issue turns into downtime.
With a one-week lookahead, the team can adjust without starting over.
A strong rolling locate plan should answer five questions:
Where will digging happen first?
Break the project into practical sections, such as station ranges, addresses, intersections, lots, or utility runs.
How much can the crew actually complete each day?
Do not base the request on the best possible day. Base it on normal production.
When does each section need to be ready?
Work backward from the planned dig date, not from the day someone remembers to call.
What information does the locator need?
Give clear limits, access notes, contact information, and the type of excavation.
When will marks need to be refreshed?
Track ticket life, site disturbance, weather, and any changes in scope according to local rules.
This turns utility locating into part of the production system, not a last-minute scramble.
Waiting too long creates hidden costs
The most visible cost of a late locate is an idle crew. An excavator, operator, laborers, traffic control, and trucks may be on site with no safe place to dig.
The hidden costs can be worse.
Late locate scheduling can force crews to jump around the project. That may look productive for a few hours, but it often creates extra mobilization, uneven restoration, and more coordination work. Crews may open small areas out of sequence, then return later to finish what could have been done once.
The project may also lose trust across the team. Superintendents get frustrated with dispatch. Operators get frustrated with management. Utility owners and locators get frustrated with unclear or rushed requests. The owner sees slow progress and asks why equipment is sitting.
A late request can also increase risk. When crews feel schedule pressure, they may rush verification, misunderstand marks, or fail to pause when something does not match the field. Safe excavation depends on clear information and enough time to use it well.
Good scheduling reduces that pressure. It gives the crew a clean start each day. It also gives locate technicians a fair chance to do accurate work.
The goal is not to blame one side. Most delays come from weak handoffs. The excavation plan changes, but the locate plan does not. The ticket gets submitted, but the work area is vague. The request is made on time by rule, but late by production reality.
A locate request is only useful when it is ready before the crew needs it and still accurate when the crew starts digging.
Better locate scheduling starts with smaller commitments
A good locate request does not need to cover everything. It needs to cover the next real work.
That shift can improve the whole project. Instead of asking, “What can we get marked?” the better question is, “What will we actually dig, and when?”
Smaller, better-timed requests help control the work. They reduce wasted marking, lower the chance of stale marks, and make it easier to confirm that the limits are correct. They also help the excavation team see schedule problems earlier.
For example, imagine a crew installing a new utility line along several blocks. The crew can complete about one block per day under normal conditions. A single request for the full stretch due in two days may not help much. By the end of the week, the last blocks may need to be checked again.
A rolling plan would request the first block for the first dig day, the second block for the next day, and continue placing requests ahead of the crew. The team still respects required notice periods, but the locates arrive in the order the work will happen.
This does not remove the need for communication. If the crew changes direction, the requests must change too. If production slows, future tickets may need adjustment. If the scope grows, the work area should be updated before digging.
The best excavation teams treat locate planning like traffic control or material delivery. It has to be ready before the crew arrives.
Field crews need a simple process they can repeat
Locate scheduling breaks down when it depends on memory. A superintendent gets busy. A foreman assumes someone else called it in. A project manager thinks the existing ticket covers the next area. Then the crew arrives and waits.
A simple process prevents that.
Use a daily locate review as part of the work plan. It does not need to be complicated. The review can take a few minutes, but it should happen consistently.
A practical daily check might include:
Confirm tomorrow’s dig area is marked and valid.
Confirm the next several days of work have requests submitted.
Check whether any marks were damaged by grading, traffic, rain, or other work.
Verify that the scope on each request matches the planned excavation.
Note ticket expiration dates or required refresh timing under local rules.
Cancel or adjust requests that no longer match the work plan.
The key is ownership. One person should be responsible for making sure requests are submitted, tracked, and matched to the schedule. That person does not have to make every decision, but the task cannot float between roles.
Crews also need clear field feedback. If a locate is missing, unclear, or marked outside the work area, that information should move quickly to the person managing tickets. Waiting until the next morning wastes another day.
The takeaway is to schedule locates like production work
Excavators delay projects when they wait too long to schedule locate requests, especially when they submit one weekly request due in two days for work that cannot be completed in two days. That approach puts too much pressure on the locate process and gives the crew too little room to work safely and efficiently.
A better plan uses a rolling lookahead. Schedule focused locate requests every day for work planned several days out. Keep the requests tied to real production. Make the areas clear. Track ticket status and mark conditions. Adjust when the field changes.
This small planning habit can prevent idle machines, rushed decisions, repeated marking, and missed start dates.
The crew should never be standing beside an excavator asking whether anyone called in the next locate. By then, the delay has already started.
Comments