Payment Bond Claims on Public Traffic Control Jobs: How the Process Works

A traffic control subcontractor on a public job carries a risk that does not exist on private work: you cannot lien the road. Public property is generally not subject to the mechanic's lien remedy that protects subs on a private site. If the prime does not pay, the leverage that would normally exist simply is not there.

What replaces it is a payment bond. On federal construction work that mechanism is the Miller Act; on state and local work it is whatever the state's equivalent statute provides. Both come with deadlines that are short, that run from events on your own job rather than from anything the prime does, and that are unforgiving when missed.

This post explains how the process generally works and what a traffic control company should have in place before it ever needs to use it.

This is not legal advice, and it is not a substitute for a construction attorney. Bond claim law is statutory, jurisdiction-specific, and unusually punishing about procedure. Nothing here interprets whether any right or deadline applies to your situation. If you think you have a claim, or might, talk to counsel licensed where the project sits — early, because the clock is often already running.

Why traffic control subs are unusually exposed

Three features of this trade compound the underlying risk.

You are often a second- or third-tier sub. Traffic control is frequently contracted to a subcontractor of the prime rather than by the prime directly. That tier position is exactly the situation the federal notice requirement is written around, and it is the situation in which the sub often does not know who the surety is or whether a bond exists.

Your work is spread out and hard to date precisely. A paving sub finishes a section. A traffic control sub sets up, maintains for weeks, comes back for phase two, and eventually picks up. "The last day labor was performed" — the date both federal clocks run from — is genuinely ambiguous on a job like that unless the records are good.

Devices left on site blur the picture further. If barricades stayed out for three weeks after the crew's last visit, was that furnishing material? Reasonable people argue about it, and the argument is worse when nobody wrote down the pickup date.

The practical consequence is that the single most valuable thing you can do about bond risk is entirely non-legal: know, from your own records, exactly what you furnished, where, and on what dates — especially the last one. Our post on preventing daily ticket disputes covers what belongs on a ticket; this is the other reason it matters.

The federal framework, in outline

When a bond exists

Under 40 U.S.C. 3131, before a contract of more than $100,000 is awarded for the construction, alteration, or repair of a federal public building or public work, the contractor must furnish a performance bond and a payment bond. The payment bond is for the protection of persons supplying labor and material.

In practice the operative threshold most contractors encounter is the acquisition regulation's. FAR 28.102-1 requires performance and payment bonds for construction contracts exceeding $150,000, and for contracts greater than $35,000 but not exceeding $150,000 it directs the contracting officer to select two or more alternative payment protections — a payment bond, an irrevocable letter of credit, a tripartite escrow agreement, certificates of deposit, or another approved deposit of security.

That middle band is worth knowing about, because on a smaller federal job the protection may exist in a form other than a bond, and "there is no bond" is not the same as "there is no protection."

The 90-day notice

This is the provision that catches lower-tier subs.

40 U.S.C. 3133 provides a right of action on the payment bond to a person who furnished labor or material and has not been paid in full within 90 days. But for a claimant who had a direct contractual relationship with a subcontractor and no contractual relationship with the prime contractor, the statute conditions that right on notice. In the statute's words, such a person may bring an action only after giving “written notice to the contractor within 90 days from the date on which the person did or performed the last of the labor or furnished or supplied the last of the material.”

The statute also specifies service. Notice must be served by any means providing written, third-party verification of delivery to the contractor at its office, place of business, or residence — or by a means that a United States marshal could use to serve process in that district.

Two things follow that are worth internalizing:

The clock runs from your last work, not from a payment failure. You can be entirely current on communication with the prime, be told repeatedly that payment is coming, and let the window close while waiting politely.

"Written, third-party verification of delivery" is a real requirement. An email you sent is not obviously that. This is a place where doing it the boring, documented way costs almost nothing and doing it casually can cost the claim.

The one-year deadline

Separately, the Miller Act provides that an action must be brought no later than one year after the day on which the last of the labor was performed or material was supplied by the person bringing the action.

Again: it runs from your last work. Not from the invoice, not from the final payment application, not from the day the prime stopped returning calls. On a multi-phase traffic control scope stretched across a long project, identifying that date correctly is a records question before it is a legal one.

State and local work: the Little Miller Acts

Most public traffic control work is not federal. It is state DOT, county, or municipal — and there the governing statute is the state's own public works payment bond law, commonly called a Little Miller Act.

The critical point is simple and frequently ignored: these statutes differ from the federal version and from each other. Thresholds differ. Notice windows differ. Some require a preliminary notice at the start of work rather than only at the end. Limitation periods differ. Some have distinct requirements depending on whether the owner is the state, a county, a city, or a special district.

Do not carry a deadline across a state line. Do not apply the federal 90-day rule to a state job because it sounds familiar. For a company working in more than one state — which is common in this trade — the practical answer is to identify the governing statute and its deadlines at contract signing, record them against the job, and treat them as project data rather than as something to look up in a crisis. This is the same discipline as multi-jurisdiction permit tracking, applied to a different set of dates.

What to do at the start of every public job

Bond claims are won and lost in the setup, not in the dispute. A short checklist that costs almost nothing:

Get a copy of the payment bond, or confirm none exists. On federal jobs the bond is obtainable. Ask the prime; if that fails, the contracting agency is a route. Knowing the surety's name before there is a problem is worth a great deal.

Record the governing statute for that project. Federal, or which state's act. Put it on the job record.

Record the deadlines the statute creates, keyed to fields you will actually have. Notice window and limitation period, both measured from last-work date.

Establish who you contracted with, and their tier. Whether you have a direct relationship with the prime determines whether the notice requirement applies to you at all under the federal act.

Decide in advance how you will evidence "last day of work." For most traffic control companies the honest answer is the final signed daily ticket plus the device pickup record. If those two live in different places — or one of them lives nowhere — fix that before you need it.

Prompt payment: the clock that runs before any of this

Long before a bond claim is on the table there is a different set of deadlines, and they are worth knowing because they give you something to point at while a payment is merely late rather than lost.

On federal construction contracts, FAR 52.232-27 sets the prompt payment framework. The government's due date for a progress payment is 14 days after the designated billing office receives a proper payment request, and for final payment the later of the 30th day after receipt of a proper invoice or the 30th day after government acceptance.

The provision that matters most to a subcontractor is the flow-down. The clause requires the prime to pay the subcontractor not later than 7 days from receipt of payment out of amounts paid to the contractor for the subcontractor's work. Late payment carries interest penalty obligations computed under 5 CFR Part 1315 at the rate established by the Secretary of the Treasury, and the clause contains a further penalty mechanism where the government fails to pay an owed interest penalty within 10 days and the contractor makes written demand within 40 days.

Two practical uses for this.

It converts "when will we get paid" into a question with an answer. "Have you been paid by the agency?" is a legitimate question, and once the answer is yes, a seven-day clock exists.

It gives you a documented escalation before the relationship breaks. A polite written reference to the clause is a much smaller step than a bond claim, and it tends to work on primes who are simply slow rather than distressed.

State and local contracts have their own prompt payment statutes, which — like the bond statutes — vary. Same rule applies: identify the one governing your project rather than assuming.

What actually happens when a claim is made

Companies that have never made one tend to imagine either a formality or a lawsuit. It is usually neither at first.

A claim is typically initiated by written notice to the surety, with supporting documentation of what was furnished and what remains unpaid. The surety then investigates: it will ask the prime for its version, and the prime will frequently respond with an assertion that the work was deficient, incomplete, or already paid. That is the ordinary shape of it, not a sign of bad faith.

What decides the outcome at that stage is almost entirely documentary. A claimant who can produce dated, signed tickets tying specific work to specific days, an unambiguous contract scope, and a clean invoice history is in a substantially stronger position than one submitting a summary spreadsheet. The surety is deciding whether the claim is straightforward enough to pay or contested enough to litigate, and the quality of your paperwork is a large input to that.

Note also that some states require a preliminary notice — served at or near the start of work rather than at the end — as a precondition to a later claim. This catches out-of-state contractors routinely, because the deadline passes during mobilization when nobody is thinking about payment risk. If you are working in an unfamiliar state, that is the single question most worth asking counsel before the first day, not after the last.

The records that make a claim provable

A bond claim rests on establishing that you furnished labor or material to that project, in what amount, and when. The documents that do it are ordinary:

• Signed daily tickets showing date, location, crew, hours, and devices — the same document that supports billing, which is why it is worth capturing well
• The subcontract or purchase order, and any change orders
• Invoices and payment application history, showing what was billed and what was received
• Device deployment and pickup records, dated
• The final work date, unambiguous and consistent across all of the above

That last item is where most companies are weakest, because it is derived rather than recorded. If your tickets stop on the 14th and a truck picked up barricades on the 29th and nobody wrote the 29th down anywhere, you have introduced a two-week ambiguity into a deadline calculation. Our notes on tracking traffic control devices by job site and getting paid faster on traffic control invoicing both come back to the same underlying record.

There is a systems point here that generalizes past bond claims: the daily ticket is the only document in this business that simultaneously supports billing, agency compliance, and payment recovery. A company that captures it well is solving three problems with one habit, and one that captures it badly is exposed on all three. That is the reasoning behind treating the field ticket as the primary object in Traffic OS rather than as an attachment to an invoice.

Bonding on the other side: your own capacity

A related topic that comes up in the same conversation. Getting onto larger public work usually requires bonding capacity of your own — bid bonds, and performance and payment bonds where you are the contracting party.

The Small Business Administration operates a surety bond guarantee program aimed at small contractors who cannot obtain bonds on the standard market. For a growing traffic control company, capacity is frequently the binding constraint on job size well before crew or equipment is — see insurance and bonding for traffic control contractors for how underwriters look at this trade, and retainage and cash flow for the working-capital picture that sits behind it.

Why this belongs in an operations conversation, not just a legal one

It is tempting to file bond claims under "things the attorney handles." The problem is that by the time an attorney is involved, the only facts available are the ones you happened to record months earlier.

The failure mode is specific and common: a company knows it was not paid, knows roughly when the work ended, and cannot produce a clean, contemporaneous record of the last day of furnishing or of what was on site. Everything after that is expensive reconstruction, and some of it is not reconstructable at all.

The fix is not legal sophistication. It is a field record that gets captured at the time, every time, including on the jobs that seem fine — because you cannot know in advance which prime is going to have a bad year. Our post on subcontracting traffic control work covers the contract terms worth fighting for up front; this post covers what happens when those terms turn out to matter.

If you want to see what capturing that looks like against one of your own public jobs — tickets tied to a project, devices tied to a location, a defensible last-work date — a demo is the fastest way to find out whether your current records would hold up.

And again, plainly: if payment on a public job has gone wrong, or looks like it might, talk to a construction attorney in that jurisdiction now rather than after the next milestone. The deadlines in this area are short and they do not forgive good intentions.