Why Construction Contracts Are Broken

Stop Signing Dumb Contracts: The Construction Industry’s Self-Inflicted Problem

There is a pattern in construction contracting that has become so normalized that most people in the industry have simply accepted it as the cost of doing business. Intellectual property clauses that transfer ownership of everything you have ever developed to a client who barely knows your name. Flow-down provisions that bind you to a prime agreement you have never seen and have no ability to influence. Payment terms that let owners pay sixty, ninety, or one hundred and twenty days out while trades are expected to finance the project in between. Risk transfer language that makes you responsible for the performance of contractors you have no relationship with. And when you ask for modifications, someone tells you they do not do contract write-ins.

We have got to stop signing these contracts. Not because they are inconvenient. Because they are wrong. And we allowed them to happen.

The Story That Prompted This

A significant client a major company approached for consulting work. The contract that arrived was remarkable, and not in a good way. The language essentially said: we own all of your intellectual property, including anything you have developed prior to this engagement. You are bound to the terms of our prime agreement. Should we fail to hit a scheduled date, you absorb the risk. The provisions flowed down liability from a contract the consulting team had never seen, for performance by contractors they had no relationship with. Eight or nine provisions, each one more unreasonable than the last.

When revisions were sent back, the project manager responded with a version of the phrase that has become the modern construction industry’s way of telling people their concerns do not matter: we do not do contract modifications.

That response deserves a direct reply. They are a general contractor. That means writing professional contracts with trade partners is literally their job. It is the function their organization exists to perform. A general contractor saying they do not modify contracts is like a restaurant saying they do not adjust recipes. The contract is the product. Producing fair contracts is the professional responsibility.

The engagement was declined. When someone tells you the terms are not a big deal and to just sign anyway, here is the only question worth asking: if it is not a big deal, why is it in the contract? A contract is a legal agreement between two parties about what they are consenting to. The terms are in the contract precisely because they matter. Nobody adds language to a legal document about things they consider trivial.

What Bad Contracts Actually Reveal

Contracts that transfer intellectual property, bind parties to unseen risk, and are designed to be impenetrable to negotiation are not signs of sophisticated legal work. They are signs of several things: legal teams that have prioritized covering themselves over doing fair work, organizations that have decided relationship management is less important than documentation, and a broader industry culture that has normalized one-sided risk allocation because enough people kept signing.

The best lawyers in any field know how to protect their clients while treating the counterparty fairly. They know that fair contracts produce better relationships, reduce disputes, and lead to better project outcomes. They know that outlandish contract terms especially ones that survive unchallenged actually signal organizational weakness rather than strength. If the contract has to be that aggressive to protect the company, it suggests the company does not trust its own ability to manage disputes through relationship and performance. The contract is doing the work that competent project management would otherwise do.

When a project manager or legal team insists that modifications are non-negotiable, they are telling you something important about how they operate. They are telling you that the relationship between parties is contractual, not collaborative. They are telling you that their starting assumption is adversarial. And they are telling you that if something goes wrong on the project, their first instinct will be to reach for the contract rather than pick up the phone and solve the problem together.

The Specific Terms Worth Pushing Back On

Intellectual property clauses that transfer ownership of work product created before the engagement are unreasonable on their face. No consultant, no trade partner, no service provider should sign away the tools, methods, frameworks, and knowledge they built over years of practice. Engaging with a client does not entitle that client to everything the firm has ever developed. Clients are paying for access to the expertise and the output of the engagement not for ownership of the institutional knowledge behind it.

Flow-down provisions that bind a subcontractor or consultant to a prime agreement they have not reviewed and cannot access are equally unreasonable. You cannot assume risk for obligations you have not seen. Agreeing to be responsible for prime agreement terms sight-unseen is agreeing to a blank check of liability. The appropriate response is simple: provide the prime agreement, identify which clauses flow down, and negotiate only the provisions that have a direct and reasonable connection to the scope of work.

Pay-when-paid provisions that indefinitely defer payment to subcontractors pending the owner’s payment to the general contractor transfer the financial burden of project execution to the parties least able to carry it. Trade partners and consultants are not banks. They should not be financing large corporations’ project costs. Payment terms should reflect the actual scope of work and the reasonable administrative timeline for processing not the outer limit of what the party with leverage can extract from the party without it.

And risk allocation language that holds one party responsible for delays, quality failures, or schedule impacts caused by other contractors or by the owner’s decisions should be challenged every time. You are responsible for what you control. You are not responsible for what you do not. Any contract that says otherwise is redistributing risk rather than allocating it fairly.

Here are the contract terms that every trade partner, consultant, and service provider in construction should push back on:

• IP clauses that transfer ownership of work developed before the engagement
• Flow-down provisions tied to a prime agreement the party has not seen
• Pay-when-paid terms that defer payment indefinitely pending owner payment
• Risk transfer language for delays or failures caused by other contractors
• Indemnification clauses that extend beyond the party’s actual scope of control

Why We Have to Stop Accepting This

The reason these contracts exist and persist is simple: the people on the receiving end kept signing them. Not because they agreed. Because they needed the work. Because they did not want to lose the relationship. Because someone told them the terms were not a big deal and they took that at face value. Because the friction of pushing back felt harder than the risk of the terms.

Every time someone signs a contract with unreasonable IP clauses, they teach the other party that those clauses are acceptable. Every time a trade partner accepts flow-down provisions they have not reviewed, they normalize that practice for the next trade partner in the same position. The industry is in this condition because it allowed itself to get here one signed contract at a time. And the only way it changes is if enough people push back consistently enough that the parties holding the leverage learn that the old terms will not fly anymore.

This is not naive optimism. This is how markets work. When enough participants refuse to accept terms, those terms change. The same general contractors who say they do not do modifications absolutely make modifications when the alternative is losing a partner they actually need. The position is a negotiating posture, not a legal reality. And knowing the difference is one of the most valuable things anyone in construction can carry into a contract conversation.

Connecting to the Mission

At Elevate Construction, the commitment to respect for people extends to the contractual relationships that govern how this industry operates. Fair contracts are not just legally defensible they are a form of respect for the parties who sign them. They communicate that both sides of the agreement believe the relationship is worth treating fairly. They create the conditions in which genuine partnership is possible. And they protect the workers and families downstream from the financial instability that bad contracts create when they go wrong. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Stop signing contracts that do not represent fair agreements. Push back on the IP clauses, the flow-downs, the pay-when-paid terms, and the one-sided risk transfers. You are a professional. The terms you agree to are the terms the industry will continue offering until you stop accepting them.

On we go.

Frequently Asked Questions

Why should a trade partner or consultant refuse to sign a contract with IP transfer clauses?

Because signing transfers ownership of work developed before and during the engagement institutional knowledge the party spent years building. Clients are entitled to the output of the engagement, not ownership of the expertise behind it.

What is a flow-down provision and why is it problematic?

A flow-down provision ties a subcontractor or consultant to the terms of a prime agreement often one they have never seen. Agreeing to absorb risk from an unseen contract is agreeing to undefined liability, which is both unreasonable and legally dangerous.

What is the appropriate response when a client says they do not do contract modifications?

Recognize it as a negotiating posture, not a legal absolute. Push back respectfully and specifically identify the exact terms that are unreasonable and propose specific revisions. If the client genuinely refuses all modification, that tells you something important about how they manage relationships.

Why does the industry still have these contract terms if they are so problematic? Because parties kept signing them. Every signed unreasonable contract validates those terms and teaches the other party that they are acceptable. The terms change when enough participants push back consistently enough that the leverage holders learn the old approach will not work.

What contract terms are worth pushing back on in every construction engagement?

IP clauses transferring pre-existing work product, flow-down provisions for unseen prime agreements, indefinite pay-when-paid terms, risk transfer for other contractors’ failures, and indemnification extending beyond the party’s actual scope of control.