Credit Applications and Payment Terms for Traffic Control Customers

Every traffic control company is a lender, whether it thinks of itself that way or not. A crew installs a closure on Monday, the ticket is signed Monday afternoon, the invoice goes out that week, and the money arrives thirty, sixty or ninety days later — if it arrives. Between the ticket and the payment, you have financed the customer's job with your labor, your trucks and your devices.

Most of the painful collection stories in this trade start at the beginning, not the end: a new customer, a rushed first job, no application, no agreed terms, and an invoice that goes to someone who never approved the work.

This post covers setting up credit for traffic control customers: what the application should capture, how to decide terms, and the legal notice rules that apply when you say no. It is general information, not legal advice. Credit law, lien and bond rights vary by state; have a lawyer review your application form and process.

What the credit application should capture

The point of the application is not only a credit decision. It is the information you will need if something goes wrong.

• The customer's exact legal name and entity type. "Smith Paving" and "Smith Paving Holdings LLC" are different debtors. Invoice the entity you contracted with.
• Addresses and billing contacts, including where invoices go and who approves them.
• Who is authorized to order work and sign tickets. This is the traffic control-specific item most applications miss. If the customer later says "that foreman couldn't authorize a night closure," the application is your answer.
• Trade and bank references, if you check them.
• Tax status and exemption documentation, where it affects your invoices.
• The customer's own customer, where relevant — the owner or prime above them, which matters for bond and lien rights on public and private work.
• Signature on your terms, so the payment terms, late charges and any damage or loss terms are accepted in writing.

Decide terms by customer type

Terms work best as a policy, not a per-customer negotiation.

One-time private customers — a homeowners' association, a small event, a property manager — are the highest-risk group and the easiest to protect: payment up front, a deposit, or a card on file before the crew rolls. Our post on taking card payments for barricade rentals covers how companies handle this.

Small and new contractors get limited terms until they have paid on time a few times: a credit limit, shorter net terms, or deposits on larger jobs.

Established contractors and utilities get standard net terms and a credit limit you review periodically.

Public agencies pay on their own schedules, which are set by statute and contract. You rarely negotiate terms with them; you manage the paperwork so the clock starts. Our post on retainage and cash flow on traffic control contracts covers the public side.

Whatever the tiers, write down the credit limit for each customer and check it before booking new work. A customer with $40,000 past due should not be able to order another closure because a dispatcher did not know.

The notice rules when you say no

Declining credit is a normal business decision, but it comes with legal obligations that many small companies do not know apply to business customers.

The Equal Credit Opportunity Act, 15 U.S.C. 1691, prohibits discrimination in any aspect of a credit transaction on protected bases, and it applies to business credit, not only consumer credit. Its implementing regulation, Regulation B, sets out notification requirements in 12 CFR 1002.9, including specific rules for business credit applicants in paragraph (a)(3).

In broad terms, as the Consumer Financial Protection Bureau's text describes, Regulation B treats business applicants with gross revenues of $1 million or less differently from larger businesses. For the smaller group, creditors follow the consumer notice rules with some modifications — for example, the right to a statement of reasons may be disclosed at the time of application. For businesses with gross revenues over $1 million, creditors must notify the applicant of the action taken within a reasonable time, and provide a written statement of reasons if the applicant requests it in writing within 60 days.

Whether extending net terms for traffic control services is "credit" under these rules in your specific arrangement, and exactly what your notices must say, are questions for a lawyer. The practical point is that a credit decision process should be consistent, documented and based on business factors — payment history, references, financial information — and that declined applicants should get the notice the rules require.

Protections that exist before you need them

Payment bonds on public work. On federal construction contracts above the statutory threshold, the Miller Act, 40 U.S.C. 3131, requires the prime contractor to furnish a payment bond protecting those who supply labor and material. States have their own versions for state and local public work. Bond rights come with strict notice and filing deadlines; our guide to payment bond claims on public traffic control jobs covers how they work.

Lien rights on private work. Many states give subcontractors and suppliers lien rights on private construction projects, again with strict notice requirements that often start at the beginning of the job. Whether traffic control work qualifies depends on the state and the project. Ask a lawyer before you need it.

Personal guarantees. For small corporate customers, a personal guarantee from the owner on the credit application is common. Whether and how to use one is a business and legal decision.

Make the invoice easy to pay

Most late payments are not refusals; they are invoices that stalled. The usual causes: the invoice went to the wrong person, it did not match the purchase order, or the customer had no signed ticket to support it. The fix is to capture the right information at the start and attach the signed daily ticket to every invoice. Our post on getting paid faster covers the invoicing side, and onboarding a new traffic control customer covers the first-job setup.

How Traffic OS helps

In Traffic OS, customers are set up as accounts with multiple contacts, so billing contacts and the people who order work are recorded on the customer. Signed daily tickets become invoices, invoices sync to QuickBooks Online, and customers can pay online through Stripe or Square or through the customer portal. The A/R aging and unpaid-invoices reports show who owes what and for how long, so a dispatcher can see an account's status before booking more work. See the features page or book a demo.

A short checklist

• Credit application for every customer on terms, signed with your terms attached.
• Authorized orderers and ticket signers recorded.
• Terms set by customer type, with a written credit limit.
• Card or deposit required from one-time private customers.
• Consistent, documented credit decisions and the required notices when you decline.
• Bond and lien deadlines tracked from day one on every project.
• Signed ticket attached to every invoice.