Red flags in contract language are rarely why got into the geoprofessions. Most of us got into the geoprofessions because we love the work. Something about the field investigations, the problem-solving, and the satisfaction of helping a project get built safely. Not to mention it might just be what a lot of us went to school for. But for most of us, reading contracts was not a big part of our education, and I’m probably not going out on a limb saying it’s unlikely to be a significant contributor to why we enjoy the work! But knowing what is in a contract before you sign it may be one of the most important skills a working geoprofessional can develop.
This article is the first in a series that is intended to help project managers, senior staff, and anyone who touches a consulting agreement understand the language that can quietly create real problems for your firm. Learning to identify Red Flags in Contract Language is a practical skill that can protect both your projects and your business over the long term.
The unfortunate, but honest truth about consulting contracts is that they are rarely written with your firm’s interests as the top priority. Understandably, clients and their legal teams draft agreements that protect their side of the table. But it means that we need to read agreements carefully, ask questions, and occasionally push back. Not because we are looking for a fight, but because we cannot do the good work our clients expect of us if we are exposed to risks that no project budget, or insurance policy for that matter, was designed to cover. Many of those risks stem directly from overlooked Red Flags in Contract Language.
Let’s review a few phrases and concepts that are worth being very aware of.
Red flag in contract language #1 – “Alleged negligence”
Negligence, in legal terms, means that someone failed to meet a reasonable standard of care and that failure caused harm. Negligence is usually evaluated by a court or through a legal process before anyone is held responsible. “Alleged negligence” skips that step. The word “alleged” means someone simply has to say that negligence occurred. No proof. No legal finding. Just an accusation.
This is important because most professional liability insurance is designed to respond when negligence has actually been established, not when it has only been claimed. If a contract holds you responsible based on an allegation alone, your insurance may not respond at all. That means legal costs, settlements, or damages could come straight out of your firm’s pocket, regardless of whether you did something wrong. All based on a claim.
Maybe a better way to frame this is to think of it as the difference between being held responsible because a court said you were at fault, versus being held responsible because someone pointed a finger at you. There’s clearly a pretty big difference that shifts your stance in court from defending your firm to having to prove beyond a doubt that you are innocent. Alleged negligence places the burden of proof on anyone accused of negligence rather than requiring evidence against them.
So, what do you do? Keep your eye open for the word “alleged” near any language about negligence, liability, or indemnification, and push for wording that ties responsibility to negligence that has been factually determined or proven, not just claimed. This is a classic example of how Red Flags in Contract Language can hide in plain sight.
Red flag in contract language #2 – “Threatened negligence”
This one takes the concept of alleged negligence and goes one step further. While a formal allegation typically involves a written legal claim, threatened negligence can be triggered by something as informal as a frustrated email, an escalated phone call, or an angry letter from a client or contractor who had a bad day. In other words, if someone even hints that they might hold you responsible for something before any formal process has started or before anything has been evaluated, you could already be on the hook under contract language that includes threatened negligence.
Anyone who has worked on a construction project knows that sometimes tempers can run hot, schedules can slip, scopes of work can creep, and people look for someone to blame. Contract language that creates financial exposure at the first sign of a threat puts your firm essentially in a no-win situation because the trigger is entirely outside your control.
So, what do you do? If you see language that reads “threats,” “demands,” or “claims” in the same breath as negligence, you need to red flag it. Also, you should make a habit of carefully documenting your project communications. Chances are that if something sounds like a threat, even informally, it could be one. So be sure to let your project principal or leadership know right away.
Red flag in contract language #3 – “Without limitation”
This one can be easy to miss because it sounds almost reasonable. We will be responsible “without limitation” sounds like a commitment to doing a good job. But in a contract, “without limitation” has a very specific and very significant meaning – and it is one of the more dangerous Red Flags in Contract Language if left unchecked.
Many consulting agreements include provisions that cap certain types of costs in the event of a dispute. This is very common with things like attorneys’ fees, where ceilings exist because legal disputes can be extraordinarily expensive, and without some kind of guardrail, a disagreement over a small project can generate legal bills that far exceed the value of the work itself.
“Without limitation” removes that ceiling entirely. It means that if a dispute ends up in litigation, attorney’s fees for everyone involved could go as high as the lawyers take them, and your firm would be exposed to whatever that figure turns out to be. In a long or complicated dispute, that number can be exceptionally large and will often end with the lawyers as the only winners.
So, what do you do? Look for “without limitation” anywhere near language about fees, costs, or damages. A reasonable alternative is to propose a cap on reasonable attorney’s fees that is tied to the value of the contract or your professional liability limits. You’re looking for something that keeps the exposure proportional to the value of your services to the actual project.
Red flag in contract language #4 – Consequential and incidental damages
Consequential and incidental damages should be thought of as the difference between fixing a problem and dealing with everything that flows from it. To start, let’s try to define what each of these is with an example: A water pump breaks at a manufacturing plant, requiring a corrective response.
Incidental Damages (The “Clean-up” Costs)
Example: Because the water pump broke, the client had to pay their own maintenance staff overtime to mop up the leaked water, and they had to pay a rush-delivery fee to get a replacement pump shipped overnight. Those extra administrative and clean-up costs are incidental damages. This is the effort to correct the direct and immediate impact of the incident, and likely could be estimated or predicted with some level of certainty as a potential risk associated with the situation.
Consequential Damages (The “Ripple Effect” Costs)
Example: Because the water pump broke, the client’s manufacturing plant had to shut down for 48 hours. They couldn’t produce their goods, resulting in $500,000 in lost sales. That massive loss of revenue is a consequential damage These are costs that, while a consequence of the event, could not be defined or predicted with certainty as a result of the associated situation.
Putting these into geoprofessional terms, imagine a scenario in which a geotechnical recommendation is disputed, and a client claims it caused a delay on their project. Without a clear exclusion in the contract, your firm could be held responsible for the entire ripple effect—one of the most costly Red Flags in Contract Language you can encounter. The direct cost of addressing the geotechnical issue, which might include revisiting the analysis or issuing a revised recommendation, is one thing. But what about the contractor who was sitting idle while the delay played out? The lost revenue that the developer claims they would have earned? The costs of every other subcontractor whose schedule was affected? Those downstream effects are what we mean by consequential and incidental damages.
Without a clear exclusion in the contract, your firm could be held responsible not just for the direct issue but for the entire ripple effect. That kind of exposure has almost nothing to do with the actual scope or fee of your work and is very difficult to anticipate or insure against in advance. Standard practice in professional consulting is for both parties to agree up front that neither side will seek consequential or incidental damages from the other. This is fair, common, and protects everyone at the table.
So, what do you do? Check whether the contract includes a mutual waiver of consequential, incidental, indirect, and punitive damages. If it does not, that absence is itself a red flag. Propose adding one and frame it as mutual protection for both parties, which it absolutely is. A large majority of contracts will include a waiver of consequential or incidental damages for the client alone, which can easily be negotiated to become a mutual waiver. So that’s an opportunity that you should try to work toward.
One more: the calendar days assumption
This one is short, but it catches people off guard more often than it should. When a contract refers to “days”, as is often the case for a deliverable deadline, a notice period, or a review window, it needs to specify what kind of days. The law generally treats days as calendar days, not business days. Every day of the week, including weekends and holidays.
The difference matters more than it might seem. A 10-day turnaround that lands over a holiday weekend is suddenly a much tighter window than you planned for. A 30-day deliverable schedule that includes two weeks of holidays is not the schedule your team budgeted around. A 3-day requirement to resolve a problem in many cases would leave you without any chance for resolution if the notification was received late on a Friday ahead of a 3-day holiday weekend.
If you mean business days, and most of the time that is what we mean, the contract needs to say business days every time it comes up. Do not assume the other side reads it the same way you do, because the default assumption will not be in your favor. Make sure you ask the question, get clarification, and get the contract amended.
The Bottom Line
None of this requires a law degree. It requires slowing down at the contract stage and evaluating the agreement —specifically watching for Red Flags in Contract Language that seem harmless at first glance. Even when the project feels routine, the client is familiar, or the pressure to get started is mounting. The clauses that create the most trouble are almost always the ones that seemed fine at a quick glance or maybe were inadvertently accepted before.
When something looks unusual, ask about it. Most clients are reasonable, and many contract issues can be resolved simply by raising them early and proposing fair alternative language. From my perspective, this is key! If you are requesting an adjustment to their agreement, propose one or more reasonable alternatives for consideration, along with an explanation of why you are making the amendment request. Your goal is to eliminate the challenges in the client’s review and acceptance of the change, so put it right in front of them and do the frontline work to get it pushed through. Make a phone call to discuss it, draft a detailed Email addressing your concerns and requests, but be sure you are proactively and energetically engaging in the discussion. The goal is never to be difficult, but to make sure both sides understand what they are agreeing to and that it is reasonable for the work being performed.
In Part 2 of this series, we will turn from the contract itself to the insurance coverage behind it, exploring what insurance policies actually protect, where the gaps are, and why understanding your own coverage matters just as much as reading the contract in front of you. So, until then, keep your eyes open for those red flags! You’ll be glad you did!
Check our website, BSK Associates to learn more about our work and what we do and if you would like to connect with one of our talented associates, please click on the link to schedule a meeting opportunity
