9 Contract Red Flags That Should Make You Pause Before You Sign

Red Flag 01

Mandatory Arbitration With a Class Action Waiver

This is the single most impactful clause most people never notice. Mandatory arbitration means you agree in advance to resolve disputes with a private arbitrator instead of in court. When it's paired with a class action waiver — which prohibits you from joining a collective lawsuit with others in similar situations — the practical effect is that small-dollar systematic harm becomes essentially unremedied.

No attorney takes a $300 case on contingency. But when a company does the same thing to 500,000 people, the $150 million aggregate claim is exactly why class actions exist. The waiver eliminates that mechanism. Look for phrases like "binding arbitration," "no class action," and "waive your right to jury trial." For a full breakdown, see our guide to arbitration clauses.

Red Flag 02

Unilateral Right to Modify Terms Without Notice

The language usually reads something like: "We may update these terms at any time. Your continued use of the service constitutes acceptance of the revised terms." This means the contract you agreed to today might be materially different next month — and your continued use of the product or service counts as consent to the new version, even if you never read it.

For consumer SaaS products, this is so common it's nearly universal. But in a B2B vendor agreement or a service contract, it should raise questions. What can they change? Pricing? Liability caps? Data use rights? Push for language that requires material changes to be sent with reasonable advance notice and requires affirmative acceptance — not just silence.

Red Flag 03

Limitation of Liability Set to $0 or $1

Limitation of liability clauses are common and often reasonable — they cap how much one party can recover from the other if something goes wrong. A cap at the total contract value is fair. A cap at the prior 30 days of fees is aggressive but arguably defensible for low-cost services. A cap of $1 or $0 is a signal that the vendor has decided liability is entirely your problem.

Watch especially for the exclusion of "consequential, indirect, incidental, or punitive damages." This language, combined with a low cap, means if their software goes down and you lose a week of business, they owe you nothing beyond a nominal amount. For mission-critical tools, negotiate for at least a cap at total fees paid over the prior 12 months. Read more in our limitation of liability guide.

Red Flag 04

IP Assignment Broader Than the Actual Work

Employment agreements and freelance contracts often include intellectual property assignment clauses — you agree that work you create for the company belongs to the company. This is normal. What's not normal is when the clause extends beyond what you're actually being hired to do.

Watch for phrases like "during the term of this agreement" or "using any of Company's resources." The first can sweep in side projects built entirely on your own time. The second can sweep in anything you created while connected to the company WiFi or using a company laptop. If the clause doesn't explicitly carve out inventions made on your own time with your own resources, ask for that carve-out. Many states have laws that limit how broad these assignments can be, but the contract still shapes what you have to fight about if a dispute arises.

Red Flag 05

One-Sided Indemnification

Indemnification means one party agrees to cover the other's losses, legal costs, and damages in specified situations. Mutual indemnification — where both parties protect each other from their own failures — is standard and fair. What you want to watch for is one-sided indemnification where only you indemnify them.

The extreme version looks like this: you agree to defend and hold harmless the company from any claim arising out of your use of the service, including their own negligence. This language, if enforced, means if they make a mistake that harms a third party and that third party sues them, you might be on the hook for their legal defense. Always check whether indemnification runs both ways, and ensure that you're not indemnifying against the other party's own negligence or misconduct.

Red Flag 06

Approval-Based Payment With No Definition of Approval

This one hits freelancers and agencies hardest but shows up in all kinds of service agreements. Payment is conditioned on "client approval," "acceptance," or "satisfactory completion" — with no definition of what approval means, what process constitutes acceptance, or how long the client has to accept or reject.

Without a defined acceptance process, clients can move the goalposts indefinitely. There's no mechanism to say "you've had ten days and haven't responded, so this is deemed accepted." Push for language that defines acceptance criteria upfront, establishes a specific review period (commonly 5–10 business days), and includes a deemed-acceptance provision if the client doesn't respond within that window.

Red Flag 07

Auto-Renewal With a Long Cancellation Notice Window

Annual contracts that auto-renew are standard. What's worth noticing is how much advance notice you must give to cancel before the renewal. A 30-day window is common and reasonable. A 60- or 90-day window means you have to decide to cancel two or three months before the renewal date — which for an annual contract means deciding in Q3 whether you want to renew in Q4.

Miss the window and you're locked in for another full year. This isn't nefarious — vendors need planning time — but it's easy to forget, especially for services you set and stop thinking about. Calendar the cancellation window the day you sign. And watch for contracts that allow price increases at renewal without capping them — paying 30% more for the same service because you missed the cancellation deadline is an unpleasant surprise.

Red Flag 08

Non-Compete Broader Than the Actual Engagement

Non-compete clauses restrict what work you can do for competing companies during and after your engagement. The reasonableness standard varies significantly by state — some states (like California) refuse to enforce non-competes almost entirely; others enforce them broadly. But the contract you sign shapes the fight you'd have to have even in a favorable jurisdiction.

Watch for non-competes that extend far beyond what you actually do: a contract to build landing pages that includes a non-compete covering "web development, software engineering, and digital marketing services" in "any market the Company serves or has reasonably considered serving." That language could cover your entire career in your field. Push for scope limited to the actual service provided, geography limited to where you actually competed, and duration limited to six months to one year at most.

Red Flag 09

Governing Law Set to a Jurisdiction Far From You

Governing law clauses determine which state's (or country's) law applies to the contract and, often, where disputes must be litigated. For large companies doing business nationally, it's standard to specify their home state. What makes this a red flag is when it's combined with a venue clause requiring all disputes to be litigated physically in that jurisdiction.

If you're a freelancer in Denver signing a contract with a company in Delaware and the venue clause requires disputes in Delaware state court, your practical ability to pursue a small claim just dropped to near zero. The travel cost alone exceeds most individual dispute values. Push for your own state as governing law, or at minimum for virtual/remote arbitration or litigation in a neutral forum. This matters more when arbitration is not in play — if the contract already has an arbitration clause, the venue clause governs where the arbitration physically happens.

The Common Thread

None of these clauses are inherently illegal. That's the point. They're all legal, they're all common, and they're all asymmetric — written to protect the party that wrote the contract, not the party who signs it. The goal of the drafter was to create a document that is technically enforceable, apparently standard, and as advantageous as possible for their client.

The solution isn't to walk away from everything. It's to know what to look for, to ask the right questions, and to push back on the clauses where the asymmetry is genuinely unreasonable. Most people never push back. The ones who do often find that half of what they asked for was negotiable all along.