Managing Recurring Lane-Closure Contracts and Long-Term Rentals

A contractor calls with a project that runs six months of night closures on the same stretch of arterial. Same plan, same devices, four nights a week. The pricing is agreed. Then the operational question arrives: how do you actually run this?

Most companies answer it badly at first, in one of two directions. They create one enormous job and lose the ability to say what happened on any given night. Or they create a job per shift and lose the contract-level view, along with any hope of reconciling the rental.

Neither is right, and the reason is that a recurring closure genuinely has two layers.

The two-layer structure

The contract layer holds the things that are true for the duration: the customer, the approved traffic control plan, the permit and its expiry, the agreed unit prices, the closure window, the billing cycle, and the standing device inventory assigned to the site.

The shift layer holds the things that change every time: which crew worked, when they arrived and left, what actually got set and removed, what was damaged, who signed, and any deviation from the plan.

Modeling these as one thing loses the shift detail that determines whether you get paid. Modeling them as unrelated jobs loses the contract detail that keeps pricing and permits consistent — and it means every shift requires someone to re-key a plan reference, a rate, and a customer.

The correct shape is a parent contract with child shift instances that inherit from it. That is not an exotic requirement, but it is worth checking explicitly when evaluating software, because plenty of tools model recurrence — a repeating calendar event — without modeling inheritance, which is the part that saves the labor.

Device-days accrue whether or not anyone visits

This is the concept that most general-purpose field-service software gets wrong for this industry, and it is worth being precise about.

On a long-term closure, a substantial share of your revenue comes from devices standing on the road. Barricades, drums, arrow boards, portable changeable message signs, and temporary barrier accrue rental for every day they are deployed — including days when no crew went anywhere near them.

A system whose only billing input is a completed visit cannot represent that. It will bill four nights of labor and silently drop three days of standing arrow board rental, every week, for six months. The error compounds quietly because nothing about the invoice looks wrong.

What is actually required is placement and removal dates tracked per device or device group, with day accrual computed between them. Our post on automating equipment rental billing covers the mechanics in general; on a recurring contract the stakes are higher simply because the duration is longer.

The corollary matters too: when a device comes off the job — picked up, swapped, destroyed — the accrual has to stop. Rental billed on equipment that returned to the yard in March is the kind of error that surfaces during an audit and costs more than it ever earned.

The permit clock

Recurring closures live under permits, and permits expire. The failure mode is entirely predictable and happens constantly: a six-month closure under a ninety-day permit, renewed once, and then a night in month six where the closure goes up unpermitted because nobody was tracking the second renewal.

Put the permit expiry on the contract record with a lead-time reminder, not on a wall calendar in the office. Our posts on lane closure permits and right-of-way permits cover the application side; the renewal side is purely an operational tracking problem, and it is one of the few compliance risks in this trade that is entirely within your control.

The same applies to the underlying plan. If the project phasing changes — and on a six-month job it will — the approved plan governing your setup may no longer describe the site. That is a plan revision question, covered in field changes to an approved traffic control plan, not something to resolve by improvising on night forty-two.

Standing caveat: permit conditions, renewal procedures, and closure-window restrictions vary by state, county, and city. Verify with the agency having jurisdiction over your specific roadway, every time.

Crew rotation and the consistency problem

A single-shift job is set up by the crew that quoted it. A six-month recurring closure is set up by eleven different crews, several of whom have never seen the plan.

Two things prevent drift.

A setup reference attached to the contract, visible from the field. The plan, the device list, and photographs of a correct setup. If a new crew's only source of truth is "do what the last guy did," the setup migrates gradually until it no longer matches the drawing — and nobody can identify the night it stopped matching.

Per-shift setup documentation. A photo of the installed advance warning and taper, timestamped and located, on every shift. This sounds like overhead and it is the cheapest insurance available on a long job, because it converts "the setup was correct all six months" from an assertion into a record.

The safety case for consistency is not abstract. FHWA reports speeding as a factor in 281 of 821 work zone fatal crashes in 2022, with rear-end collisions accounting for 174 — roughly 34 and 21 percent respectively. Those are drivers meeting a setup later than they should have. A taper that has quietly shortened over four months is exactly the mechanism.

And the exposure is routine rather than exceptional. The Associated General Contractors of America reports from its annual survey with HCSS that "Sixty percent of highway construction firms report having at least one car crash into their work zones during the past year".

Billing cycle, not billing event

Short jobs bill on completion. Recurring contracts have to bill on a cycle, usually monthly, and the cycle assembles from three inputs:

• Shift labor, from the signed tickets for the period
• Device-day accrual, from placement and removal dates
• Extras — callouts to reset knocked-down devices, added devices, damage charges

The third bucket is where recurring contracts leak. A crew rolls out at 1 a.m. to reset devices a vehicle took down, spends ninety minutes, and nobody bills it because it was not a scheduled shift and did not fit the recurring template. Over six months that is real money. Capture it as an extra against the contract at the time it happens, or accept that it is a donation.

Damage and loss deserve their own treatment — see charging for damaged and lost traffic control devices — because on a long-term deployment the attrition is substantial and the terms usually exist in the contract already, unenforced.

What to check before signing a long recurring contract

Five things, quickly.

Escalation. Six months is long enough for labor and fuel to move. A contract with no escalation clause on a twelve-month term is a bet on stability.

Minimum shift duration. A closure that gets cancelled at 10 p.m. after your crew has mobilized still cost you a crew.

Cancellation notice. Weather and contractor schedule slips will cancel shifts. Who absorbs the cost is a contract question, and the default is that you do.

Device attrition terms. Who pays for devices destroyed by third-party vehicles. This will happen; the only question is whether it was addressed in advance.

Payment cycle and retainage. A six-month job billed monthly with 60-day terms is a substantial working-capital commitment. Our note on getting paid faster is relevant, but the structural decision is made when you sign.

The reporting you actually want

At month three, the questions worth answering are: what is our realized margin on this contract versus the bid, what share of revenue is labor versus rental, how many unscheduled callbacks have we absorbed, and how much device attrition have we eaten.

None of those are answerable if shifts and rentals live in separate systems that are reconciled by hand. They are all straightforward if the contract is the parent record and everything — shifts, device-days, extras, damage — hangs off it. That is the reasoning behind how Traffic OS models recurring work and long-term rentals, and the pricing page shows what is included at each tier. You can book a walkthrough to see the contract-to-shift structure on real screens.

Recurring closures are the best revenue in this business: predictable, staffed by a crew that knows the site, with equipment that stays put. They are also the easiest work to run at an unexamined loss for six months, because nothing about a routine night tells you the rental stopped accruing correctly in week two.