Pricing Standby, Show-Up Time, and Cancellations on Traffic Control Jobs

Standby, show-up time, and cancellations are the most under-priced hours in traffic control. Nobody bids them, most rate sheets do not name them, and by the time they happen the crew is already on the clock and the conversation is a negotiation you are losing. The fix is not better arguing. It is putting the terms in the rate sheet before the trip.

Three different situations, three different charges

Lumping these together is why they get argued. They are not the same event.

Crew shows up and the job does not happen. The site is not ready, the utility never located, the GC cancelled and nobody called, or nobody can find the person who is supposed to authorize the closure. You have burned the drive, the load-out, and a block of payroll. This is show-up time or a trip charge.

Crew is on site and held. Devices are staged or set, and you are waiting on the GC, a utility crew, an inspector, or an agency sign-off. The crew is present, under someone else's direction, and unavailable for other work. This is standby.

Crew is released early. The job was scheduled for ten hours and wrapped in four. Whether you bill the remaining hours depends entirely on whether you have a minimum, and whether that minimum is written.

Each of these needs its own line on the rate sheet, its own trigger described in plain language, and its own rate. A customer who will accept a two-hour show-up charge without blinking may fight a full-day minimum, and if both are on the same line you will lose both.

Put it in the rate sheet, not the argument

The single highest-leverage change is moving these terms out of the dispute and into the document the customer already agreed to. That means the rate sheet or the master service agreement carries, at minimum:

• An hourly minimum per crew per call-out. Stated in hours, not implied.
• A show-up or trip charge, with the conditions that trigger it written out: crew arrived at the scheduled time and location and the work could not proceed for reasons outside your control.
• A standby rate, which may or may not equal your productive hourly rate. Some contractors bill standby at the same rate on the theory that the cost is identical. Some discount it as a relationship concession. Either is defensible; being silent is not.
• A cancellation window. Cancel more than the stated number of hours before the scheduled start and there is no charge. Inside the window, the minimum applies. Same-day or on-arrival, the show-up charge applies.
• After-hours and weekend treatment, because a Saturday cancellation costs you more than a Tuesday one.

If you already have a structured rate sheet for devices and labor, these belong right next to the device day rates — see traffic control device rental rates and pricing for how the rest of that document should be organized, and master service agreements and rate sheets for traffic control work for getting the whole thing attached to a customer relationship rather than re-quoted every call.

The number itself should come out of your cost model, not out of a competitor's rate sheet. If you have not built the loaded cost of putting one flagger on the road for one hour — wages, burden, vehicle, fuel, insurance, overhead — flagger labor cost per hour and the loaded rate is where to start. A minimum that does not cover the loaded cost of the trip is a discount you did not mean to give.

Documenting it so it survives a challenge

A standby charge lives or dies on four facts:

1. When the crew arrived. Timestamped, at the site.
2. Who directed them to wait. Name and company. "The GC" is not a name.
3. What they were waiting on. One line. Utility locate, inspector, deck pour, access.
4. When they were released. Timestamped, and by whom.

All four belong on the daily ticket, signed on site by the person who directed the wait. That signature is the whole argument. A ticket signed at 7:40 a.m. by the superintendent, showing arrival at 6:55 and release at 11:20, with "held for utility locate" written on it, is very hard to dispute six weeks later at invoice review. A recollection is not.

This is the same discipline that prevents ordinary ticket disputes — see preventing daily ticket disputes. The difference with standby is that the field crew has to know to capture it in the moment. A flagger who has been told "just wait" for three hours will not spontaneously document who told them, unless the ticket has a field asking.

Traffic OS captures the daily ticket in the field with a GPS stamp and an on-site signature, and standby has its own line on the ticket rather than being written into the notes. That matters mainly because a note is not a billable quantity and a line is.

Job costing: keep standby out of the productive bucket

Here is the quieter damage. If standby hours land in the same cost code as setup, flagging, and teardown, then your cost per productive hour is wrong, and every bid you build from historical job costs inherits that error.

Say a crew books ten hours on a job and three of them were standby waiting on a utility. If all ten hours are coded as production, the job looks like it took ten hours of work and your future estimates for that work type get padded. If the three are coded as standby, you learn two useful things: how much of your labor is non-productive, and which customers generate it.

That second one is the real payoff. Standby is not evenly distributed. A small number of general contractors will generate a large share of it, and until you can see it by customer you will keep treating them as good accounts. Pull standby hours by customer for the last two quarters and the picture usually surprises people. Job costing for traffic control companies covers the coding structure; the point here is simply that standby needs to be its own code.

It also feeds crew utilization honestly. A crew that is 78 percent utilized on paper but spends a fifth of that on standby is not the same asset as one at 78 percent productive — see crew utilization metrics for traffic control.

The negotiation reality

A general contractor will push back. Expect it, and expect the push to sound reasonable: we are all in this together, weather happens, nobody controls the utility.

Two things help.

Have the window in the document from day one. A term that was in the rate sheet when they signed is a term. A term produced after a bad Tuesday is a penalty, and it reads as opportunistic even when it is fair. This is one of the strongest arguments for an MSA with an attached rate sheet on repeat accounts — the conversation happens once, in a calm room, instead of every time something slips.

Make the window generous enough to be usable. A cancellation window the customer cannot realistically hit produces charges every time, which produces friction every time, which eventually produces a lost account. A window their superintendent can actually meet gets them calling you the night before, which is the behavior you actually want. You are not trying to monetize cancellations. You are trying to stop absorbing them.

It is fair to say plainly that a written standby term also protects the relationship. Without one, every held crew becomes a judgment call by whoever answers the phone, and inconsistent enforcement across customers is worse for the relationship than a consistent policy either way.

The payroll side

Whatever you bill, the crew is still yours. Federal wage and hour rules treat waiting time as fact-specific: 29 CFR 785.14 frames the question as whether the employee was engaged to wait or waited to be engaged, and says the answer depends on the agreements between the parties, their conduct, the nature of the service, and the surrounding facts. 29 CFR 785.15 addresses on-duty idle time, where the employee cannot effectively use the time for their own purposes and it counts as work time.

Overtime sits on top of that. Under 29 U.S.C. 207, covered employees who work more than 40 hours in a workweek must receive at least one and one-half times their regular rate for the excess. Standby hours that count as hours worked count toward that 40.

States add their own layer, and some have reporting-time or show-up pay requirements that have no federal equivalent. This post is not legal advice and cannot tell you how any of it applies to your crews. Confirm your obligations with your own employment counsel, and confirm state specifics for every state you operate in.

The operational takeaway is narrower and safe: assume you owe the crew for held time, price accordingly, and never let a billing decision drive a payroll decision. If you decide as a business matter not to bill a customer for standby, that is a margin choice. It does not change what you owe the people who sat in the truck.

What to do this week

Pull your last twenty jobs. Count the hours where a crew was on site and not working, and the trips where a crew arrived and turned around. Multiply by your loaded rate. That number is what the missing rate sheet lines are costing you annually.

Then write three lines — minimum, show-up, cancellation window — attach them to your standard rate sheet, and put them in front of your three highest-volume customers before the next slip happens. Getting paid on time for what you did bill is a separate problem, and getting paid faster on traffic control invoicing covers that side.