It’s a Tuesday morning. The hotel project is 20 months in. Drywall is up, the rough mechanical is signed off, and the finishes are starting to land on site.
The tile sub gets the phone call he has been dreading. His supplier is on the other end. The price is up 20%, and the tile is now on back order — four more months.
He sits in his truck in the parking lot for a minute. He does the math in his head. The 20% bump is fifty grand he doesn’t have. The four-month delay means he loses the next job on his calendar, the one with the half-million-dollar margin he has been counting on since February.
The General Contractor (GC) is a tough customer, and he’s going to have a fit.
He stares at the number on his phone, pauses, takes a breath, and hits call.
The GC answers, a little too quickly: “It’s Friday, my friend, give me some good news.” The tile sub explains the situation, hits him with the $50,000 change order, and follows up with the next job loss of profit to set the stage for his predicament. The GC does not like what he hears: “It isn’t my problem, buddy. You should have bought that tile months ago, and we aren’t moving the schedule four months because you screwed up. You had better find a solution ASAP and don’t pull that lost profit nonsense with me — we all have our scheduling problems. Fix it or else.” The “or else” means he’s off the job and probably not working for this GC again.
Although he was hoping for a better answer, it went the way he expected. He calls his lawyer.
And just like that, on a perfectly ordinary Friday morning, in a perfectly ordinary hotel project, a small fire becomes a wildfire. The tile sub is going to walk off the job. The GC is going to hire a replacement at a premium. The replacement is going to come back to the owner with a change order. The owner is going to ask the GC why he didn’t manage his subs properly. The GC is going to remember that the original tile sub had a point. The lawyers are going to send their first letters. And 18 months from now, after the hotel has opened anyway, because hotels always do, three sets of attorneys will be billing by the hour to figure out who owed whom what on a Friday morning that nobody in the room can quite remember anymore.
This is a true story. It happens, in some version, with multiple trades on every construction project I have ever seen. And it is entirely preventable.
The Wildfire Was a Phone Call
Notice what just happened. The dispute didn’t begin with a lawsuit. The dispute began with a phone call from a tile supplier. The wildfire was an ember for about 12 minutes.
In those 12 minutes, the tile sub had a problem. By minute 13, after the GC told Juan to “fix it or else,” he had a grievance. By the following week the tile sub either walked off or was fired, and then lawyered up just about the time he filed his mechanics lien for past due invoices, which the GC was now holding as ransom for the new premium he would have to pay for replacement tile and a new tile sub who would certainly be charging him more to fix the problem left by Juan the tile man. By the time the lawyers were selecting mediators, 18 months had passed; the project had limped to completion with a substitute sub at premium pricing; three relationships had been incinerated; and the legal bills were already deep into six figures.
If somebody, anybody, had been on the phone with the tile sub at minute 13 — a calm, neutral, technically fluent somebody who already knew the project, already knew the GC, already knew the contracts — the wildfire never starts. The tile sub gets heard. The GC gets reminded that tariff increases are not entirely the sub’s fault. A creative solution emerges. Maybe the owner absorbs part of the increase to keep the schedule. Maybe the GC agrees to release the sub for the lost job in exchange for a discount on labor. Maybe the tile gets re-specified to something that ships in four weeks instead of four months. Nobody walks off. Nobody hires a lawyer. The project keeps moving.
That somebody on the phone has a name. We call him a Standing Construction Mediator.
And Now a Word About the Dispute Review Board
Right about now, the construction lawyers reading this are saying, "Joel, we already have a tool for this." It’s called a Dispute Review Board. We’ve had it since 1975, and the Dispute Resolution Board Foundation has been leading the way since 1996. Every serious infrastructure project uses them.
They’re right. Sort of.
The Dispute Review Board was born in the second bore of the Eisenhower Tunnel in Colorado in the mid-1970s. The first bore had been a litigation bloodbath. Then somebody had a radical idea: what if we put three smart, neutral construction people on the project from day one, hearing disputes as they came up, issuing recommendations before everybody lawyered up?
It worked. Spectacularly well. The DRB became the gold standard for mega-projects. The World Bank requires it on big infrastructure deals. The Dispute Resolution Board Foundation reports that on projects with DRBs, something like 98% of disputes resolve without litigation. That’s not a typo. Ninety-eight percent.
And so, for 50 years the construction ADR community has been politely telling the rest of the construction industry: “Hey, you should try this. It’s great.” And the construction industry, equally politely, has been responding: “That sounds expensive, complicated, and designed for somebody other than us.” And then everybody goes back to litigating.
Here is the thing nobody likes to say out loud. The DRB has been a success on roughly 5% of construction projects and a non-event on the other 95%. It is a skyscraper crane where most projects just need scaffolding.
What a DRB Actually Does
A DRB is three neutrals. Each side picks one. The two picks pick a third. They sit on the project for the life of the work. They visit the site quarterly. They review the project record. And when a dispute is referred to them, they hold a hearing. Position papers get submitted. Lawyers argue. The panel issues a recommendation, or in some structures a binding decision.
If that sounds like litigation light or a mini courtroom trial, it’s because it is. The DRB is faster than court and fundamentally adjudicative. Somebody wins. Somebody loses. Somebody appeals to arbitration.
On a $2 billion tunnel, this is exactly the right tool. You need engineering rigor. You need a record. You need somebody who can read a delay claim with engineering expertise and tell you whether the contractor’s critical path analysis is real or imaginary. The DRB delivers all of that, beautifully.
But notice what the DRB does not do. It does not prevent the dispute. It processes the dispute. By the time the panel hears it, the parties have lawyered up, marshaled their evidence, taken positions, and committed in writing to a version of events. Even if the recommendation is non-binding, the relationships are already bruised. People remember being cross-examined by their counterparty’s engineer. The DRB is a brilliant adjudicator. It was never trying to be a peacemaker.
Now play the tile sub scenario through a DRB.
Friday morning. The supplier calls. The tile sub calls the GC. The GC rebuffs him. Here’s the first problem: the tile sub may not even be able to take it to the DRB on his own. DRBs are typically owner-GC mechanisms, and unless the sub-tier has been carefully written into the dispute board agreement, the tile sub has no standing to file. He has to work through the GC — the same GC who just told him to fix it or else. But assume the contracts pulled him in. He files a Notice of Dispute. The DRB schedules a hearing in eight weeks. Position papers get drafted. Lawyers get involved anyway, because of course they do. Six weeks later the parties present their cases. Eight weeks later the panel issues a recommendation. By that point, the tile sub has already lost the next job, the GC has already started looking for a replacement sub, and the relationship is already in the ground. The DRB recommendation, even if it’s perfectly fair, lands on a dead body.
That’s not the DRB’s fault. The DRB was designed to resolve a dispute, not to prevent one. The Eisenhower Tunnel was not the Friday morning phone call. The Eisenhower Tunnel was a $250 million differing-site-condition claim with a hundred boxes of geotechnical reports. Different problem. Different tool.
Same Standing, Different Job
The Standing Construction Mediator, like the DRB, gets engaged from day one. Like the DRB, the SCM stays on for the life of the project. Like the DRB, the SCM is written into the contracts, flowed down to the subs, and is very familiar with the full scope and vision of the project. The goal is the same: to resolve disputes. However, the SCM does it at the inception of the problem.
A DRB is a standing adjudicator after the fire is blazing. The SCM is a standing facilitator putting out the embers before they become full-blown forest fires.
The SCM is not waiting for the dispute to crystallize so she can rule on it. The SCM is on the phone with the tile sub at minute 13. The SCM is the calm, neutral voice that says: Hold on. Don’t call your lawyer yet. Let me call the GC. Let me talk to the owner. Let me see if there’s a creative way through this before anybody starts a war.
The SCM does not issue findings or rulings. The SCM does not hold hearings. The SCM is a senior, neutral, construction-fluent project advisor whose only mandate is to keep the project moving and the parties talking and working out their problems. When the SCM works, there is nothing for anyone to adjudicate, because the dispute was resolved at the field level before it ever became a claim.
If the DRB is a tribunal you keep on retainer, the SCM is the wise neighbor who stops the argument before the cops have to come.
The Eight Things That Are Actually Different
Every time I pitch the SCM idea to owners, GCs, and lawyers, I am told it’s just a twist on DRBs — nothing new, just new packaging. Here are the eight differences that matter.
- Adjudicative versus facilitative. The DRB hearing is a positional exercise. Each side argues. The panel decides. The SCM does the opposite — caucus, joint session, shuttle diplomacy, interest-based problem solving. The DRB asks who is right under the contract. The SCM asks what we need to do to keep the job moving and the relationships intact.
- Timing. A DRB engages when somebody formally files a dispute. By that point, the issue has been escalated, documented, and positions cemented, and weeks and months have gone by. The damage is done, and now it’s about who is responsible. The SCM engages days after the tile sub had that hard conversation with the GC. The intervention threshold is dramatically lower. Mediate a solution that keeps the project moving and addresses all concerns before it develops into a full-blown fire.
- Outcome. DRB recommendations are imposed outcomes. Somebody wins, somebody loses; the loser may or may not appeal. SCM outcomes are negotiated agreements that both sides own. This matters more than people think. The contractor who lost a $400,000 DRB recommendation on a project versus a SCM where both parties agree to his payment of $200,000 and he stays on the project makes for a very different relationship and outcome. Construction is a small world. Memories are long. Relationships and reputation matter. The $400,000 DRB recommendation kills the relationship and most likely results in arbitration. The $200,000 mutually agreed resolution saves the relationship and keeps the job running.
- Cost. A DRB is three neutrals, three sets of fees, three sets of travel, formal hearings with prep time and submissions. Industry estimates put DRBs at roughly 0.05% to 0.25% of project value, before hearing costs. An SCM is one neutral, lighter touch, no hearing infrastructure. Significantly more affordable than the DRB fee structure. For a $60 million project, the difference between “line item we can absorb” and “line item that gets cut” is the difference between having dispute prevention and not having dispute prevention written into the contract.
- Project size. This is the part the construction ADR community has politely refused to deal with for 50 years. DRBs are essentially the standard of care on $500 million-plus infrastructure projects. They are almost never used on a $40 million multifamily, a $25 million hospitality renovation, or a $75 million mixed-use. That’s the gap. That is where construction disputes actually live and breed and litigate. The SCM model fills that gap because the cost structure scales down. You cannot use a skyscraper crane on a project that needs scaffolding.
- Skill set. DRBs are built around technical adjudication. You want engineers who can read a delay claim with surgical precision. SCMs are built around facilitation. You want a neutral with construction law fluency and mediation expertise, enough that nobody questions the credibility, but whose primary skill is process management, communication, and dispute resolution. These are genuinely different professional profiles. A great DRB member is not automatically a great SCM. Pretending otherwise has done the field no favors.
- Confidentiality. DRB recommendations are often admissible in subsequent arbitration or litigation. Sometimes that is the whole point. SCM communications carry mediation privilege under California Evidence Code 1115 through 1128, and similar statutes everywhere else. That privilege is not a technicality. It is the input that makes early resolution possible. Parties cannot speak candidly about weaknesses in their own positions in front of a panel that may use what they disclose against them later. They can speak candidly to a mediator. Candor is the raw material of mediated resolution.
- Subs and suppliers. DRBs are typically owner-GC mechanisms. The sub-tier disputes, which, let’s be honest, are where most real construction conflict actually lives, are usually outside the DRB’s reach unless the contract has been carefully drafted to pull them in. The SCM model, structured properly with mandatory flow-down clauses, brings subs and major suppliers into the same dispute-prevention framework from day one. On a project where the real fight is going to be between the GC and the tile sub, that is not a small detail. That is the whole game.
Where the DRB Still Wins
The DRB is one of the great inventions of post-war construction, and I have nothing but respect for the people who built it into what it is. There are projects where the DRB is the right tool and the SCM is not.
On a $2 billion tunnel, you need a panel that can adjudicate complex differing-site-condition claims with engineering rigor. SCM is not designed for that volume of technical adjudication, and pretending otherwise would be foolish.
On public works and mega-projects, DRBs are the proper framework. The nature of those projects has long recognized DRBs as the most efficient form of dispute resolution — primarily driven by the need for high technical proficiency in the construction industry by the DRB members.
And on projects where the parties actually want a binding ruling — some sophisticated owners do, because they want a record and an appealable decision — the SCM intentionally does not produce that. If that’s what you need, an SCM is the wrong tool. Use a DRB.
This is not an argument for using SCM instead of DRB. The SCM is the right mechanism for the enormous middle market of construction projects. Lightning quick. Keeps the project moving. Gives every party a chance to be heard during the life of the project. The SCM does not replace the DRB. It fills the crack the DRB was never designed to fill.
The Part Nobody Talks About
There is one more fundamental difference between SCM and DRB: preserving the relationships by facilitating a resolution that everyone can live with.
Construction is a relationship business. The same developer hires the same GC on three projects. The same GC hires the same framer on twenty. The same architect refers the same waterproofing consultant for a decade. Reputations are built brick by brick — sometimes literally — and they get destroyed in a single bad hearing where somebody’s project executive got cross-examined about an email he wishes he had not sent.
A DRB recommendation, even when it is right, leaves a scar. The losing side may pay, but they remember. They will not call you for the next project. They will not refer you. They will, in the quiet moments at the industry conference, mention to a colleague that they had “a tough one” with you. The construction world is small; people talk, and reputation matters.
An SCM resolution, when it works, leaves a handshake. The parties walked into the room with a problem and walked out with an agreement. Nobody got cross-examined. Nobody had to explain a loss to a board. The relationship survives. The next project gets called. The referral gets made. The industry, slowly and quietly, gets a little less adversarial.
That is not a small thing. That is the entire reason this practice exists.
And Then California Did It Again
Which brings us, at long last, to Section 8850.
On October 10, 2025, Governor Newsom signed SB 440 into law. It is now codified as California Civil Code section 8850. As of January 1, 2026, it applies to virtually every private construction contract in the state, with a narrow carve-out for residential projects four stories or less and not mixed use. If you are a private owner, contractor, or sub working on anything bigger than that, this statute now governs how disputes get handled. And here is the kicker: the core requirements cannot be waived by contract. Try to waive them, and the waiver is void as against public policy.
So what does 8850 actually require?
When a contractor or sub submits a claim — payment, time extension, damages, change orders, the whole catalogue of construction grievances — the owner has 30 days to respond in writing and identify what is disputed and what is not. Undisputed amounts get paid within 60 days. Late, and you are paying 2% per month interest, which annualizes to 24%, which is the kind of number that gets a CFO’s attention. If a dispute remains, the parties go to a meet-and-confer. If the dispute survives that, they go to mandatory non-binding mediation. If the parties cannot agree on a mediator within 10 business days, the contractor picks one. Costs are split equally.
Read that again. The State of California has just decided, by statute, that the structural answer to private construction disputes is mediation. Not arbitration. Not litigation. Not a DRB. Mediation. And not as an option. As a non-waivable requirement.
This is not a small statute. This is California codifying, as a matter of public policy, that mediation is the correct first-line process for resolving private construction disputes. The legislative intent language talks about prompt and fair payment, reduced litigation costs, and economic stability in the construction industry. The mechanism the legislature picked to achieve those goals is a mediator.
Now think about 8850 reactively versus proactively.
Reactively, 8850 is a statutory backstop. A claim arises, the clock starts, the parties grind through the meet-and-confer, they hire a mediator they have never met, that mediator parachutes into a project she has never seen and tries to resolve in a few hours something that has been festering for months. Better than nothing. Much better than nothing. But it is the same problem the construction ADR community has been complaining about for 50 years — the mediator does not know the project, the relationships, or what is really driving the dispute. Not to mention, try getting a calendar date with a well-respected construction mediator within a six-month period. Good luck.
Proactively, 8850 is the most aggressive endorsement of Standing Construction Mediation any legislature has ever passed, even though the statute does not use that term. Because the SCM is exactly the mechanism that makes 8850 work the way the legislature wanted it to work. The mediator is already on the project. The mediator already knows the contracts, the people, the history. The meet-and-confer happens before there is anything to confer about. The dispute gets resolved before it ever becomes a 30-day clock running on a registered claim. The 24% per annum interest never accrues because the payment never gets disputed in the first place.
8850 is the statute. SCM is the operational answer. They were made for each other, and one of them just became the law of California.
Let AI Read the Mountain
There is one more piece of this that is worth talking about, because it changes the economics of being an effective mediator on a construction project.
Construction disputes come buried in paper. Not metaphorical paper. Actual mountains of it. The prime contract is two hundred pages. The subcontracts are another 50 pages each, times 20 subs. The plans are 1,000 sheets. The specs are 800 pages. The submittal log has 600 entries. The RFI log has another 600. The change order log has 200. The daily reports go back 20 months. The pay applications come monthly with backup. The schedule updates come monthly. The emails number in the tens of thousands.
When a dispute lands on a mediator’s desk — reactive or standing — the first 40 hours of work are not mediation. They are document grinding. Read the contract. Read the relevant subcontract clauses. Cross-reference the change order in dispute against the original scope. Find the RFI that may have authorized the work. Find the email thread that may have rescinded that authorization. Check the daily reports for the relevant week. Check the pay app for what was billed and what was paid. Check the schedule for what the impact actually was.
It is exhausting. It is mind-numbing. And it is exactly the kind of work that drains the cognitive battery you need for the actual mediation. By the time you have read the mountain, you have used up the very mental energy that the parties are about to need from you in the room.
This is where AI changes the game for the SCM. Not as a replacement for the mediator’s judgment. As a research assistant who never gets tired.
Feed the prime contract, the relevant subcontracts, the change order log, and the RFI log into a properly configured AI tool. Ask it: which clauses of the prime contract govern tariff increases on owner-supplied versus contractor-supplied materials? Show me every RFI that touches the tile scope. Show me every change order that was approved in the first 18 months and the average cycle time from submission to approval. Build me a chronology of the tile-related correspondence with citations to the source documents. Tell me what the contract actually says about delay damages when the delay is caused by a supplier disruption outside the contractor’s control.
Thirty minutes. Done. What used to take a paralegal or junior associate three days takes the SCM half an hour. The mediator’s brain stays fresh. The mediator’s energy stays directed at the actual mediation work — the listening, the empathy, the creative problem solving, the reading of the room, the careful management of the relationships. The grinding gets outsourced to the machine. The judgment stays human.
This is the part the reactive mediator cannot replicate. The reactive mediator gets dropped into the project at month 18, with no document context, and has to start from zero. The SCM has been on the project from day one. She already knows where the contract speaks to the issue. She already knows which RFI matters. She uses AI to confirm and to cite, not to discover from scratch. The grunt work gets compressed from days to minutes, and the mediator shows up to the actual mediation rested, clear-eyed, and ready to do the human work.
On a $60 million hotel project with twenty months of accumulated documents, the SCM with AI assistance can pull the relevant material on a brewing dispute in the same afternoon the dispute is raised. The reactive mediator showing up 18 months later, with no AI workflow and no prior project knowledge, is still going to spend a week reading. By the time she has read enough to be useful, the parties have spent another $50,000 in legal fees and another month of bad blood.
That is not a small efficiency gain. That is the difference between resolution at minute 13 and resolution at month 13.
Back to Friday Morning
Let’s go back to the tile sub for a minute.
Same Friday morning. Same supplier phone call. Same 20% increase. Same four-month delay. Same lost half-million on the next job.
Only this time, before the tile sub calls the GC, he calls the SCM. Or he calls the GC, the GC gets upset, and then he calls the SCM. Either way, by next week, the SCM is on the phone with the GC. A few days later, the SCM is on the phone with the owner. Next, the three of them are on a Zoom together, with the SCM running the conversation, and somebody is suggesting that the owner might absorb half the tariff increase if the GC releases the sub to start the next job and finds him a way to come back in two months instead of four. Days later, there is a one-page memorandum signed by all three. The tile sub buys the tile. The project keeps moving. Nobody walks off. Nobody hires a lawyer. The wildfire never starts.
That is the whole pitch. Not complicated. Not expensive. Not revolutionary. Just somebody on the phone at minute thirteen, who already knows the project, who has the trust of all three parties, and whose job is to make sure the wildfire never starts.
The DRB taught the construction industry that standing is better than reactive. The SCM finishes the lesson by adding that facilitative is better than adjudicative on the projects most of us actually work on. AI lets the SCM offload the document grind, so her judgment stays sharp for the human work. And as of January 1, 2026, California has put a statutory thumb on the scale and said: on private projects, mediation is the answer.
If you are an in-house counsel, a developer, a GC, or a sophisticated sub working on a private project, the question is no longer whether you will be in a mediation. The legislature has answered that for you. The only question left is whether your mediator will know your project before the dispute, or after.
I know which one I would pick.