The signed change order is no longer where a construction dispute is won or lost. It’s in the group chat. Superintendents thumb-type approvals from the cab of a truck, project managers fire off “go ahead, we’ll paper it later” between meetings, and owners nod along in a WhatsApp thread at 9 p.m.
Months later, when the invoice arrives and somebody balks, the paper trail everyone assumed existed doesn’t exist. The text thread does.
That thread is the contract now. Courts are reading it that way, and by the time a construction dispute attorney gets the call, the pattern of texted approvals is usually already set. The assumptions the industry still carries about what “counts” as an approval are catching people off guard, and a few of the most common ones are worth taking apart.
Myth: A Text Isn’t a Real Contract
A text can absolutely be a contract, and it doesn’t take much for one to qualify. If the exchange shows an offer, an acceptance, and something of value moving between the parties, courts have treated text messages as enforceable agreements in construction disputes. The medium doesn’t downgrade the deal. A “yes, do it” answering a scoped request for extra framing can bind a company the same way a signed proposal would.
The trap is tone. People type on their phones the way they talk on site. Shorthand, jokes, half-sentences. None of that stops a judge from reading the thread as a meeting of the minds.
Myth: The Written-Change-Order Clause Protects You
Almost every construction contract requires changes to be in writing, signed, and priced before the work starts. Owners lean on that clause. The problem is that the clause can be waived by conduct, and jobsite messaging is exactly the conduct that waives it. When a project runs for months on texted approvals that everyone honors, and invoices get paid on that basis, a court can find the parties adopted a new practice and stopped enforcing the formal procedure.
If you want the clause to hold, enforce it from day one: rejected extras sent back in writing, verbal go-aheads followed by a same-day confirmation, and no payment slipping through on work that skipped the process.
Myth: Group Chats Are Just Coordination, Not Authority
The person tapping “approved” in a group chat may not be the person the contract names as authorized to approve. Owners often assume that limits their exposure. It doesn’t usually. If a superintendent, PM, or owner’s rep has been sending directives all project without correction, courts can find they had apparent authority to bind the company on the extras they signed off on.
The fix is unglamorous. Name the people who can authorize changes, in writing, at the start of the job. Tell the other side. And when someone outside that list starts issuing directions in the chat, correct it in the same thread, in the same hour.
Myth: The Messages Will Still Be There Later
Phones get replaced. Apps get uninstalled. Employees leave and take their devices with them, and auto-delete settings erase threads on a rolling window without anyone thinking about it.
By the time a claim gets serious, the messages that would have decided it may already be gone, and the party that can’t produce them is the party that loses the argument.
Where This Actually Lands
The through-line in the emerging case law is simple: courts look at how the parties actually behaved, not how the contract said they were supposed to behave. If the jobsite ran on texts, the texts are the contract. Send every message like it will be read back to you later, and the disputes that do come get a lot shorter.
