Contracts
Red Flags in a Service Agreement (and How to Fix Them, 2026)
By FixMyContractLast updated August 20, 20268 min read

A service-agreement red flag is a clause that quietly shifts cost, risk, or control to you — usually hidden in standard-looking boilerplate. The ten most common are open-ended scope, payment on completion, sole-satisfaction acceptance, IP transfer before payment, perpetual one-way confidentiality, uncapped indemnification, no liability cap, one-way termination, auto-renewal traps, and a distant jurisdiction.
Most unfair contracts aren't obviously unfair. The risky clauses are buried in standard- looking boilerplate, written in a way that sounds reasonable until you need them to protect you. This guide is a field manual: ten red flags that show up again and again in service and client agreements, why each one matters, and the language to ask for instead.
1. Open-ended scope with a fixed price
Looks like: "Provider will perform the Services and such other related tasks as the Client may reasonably require." Why it's risky: "related tasks" is unbounded. You agreed to a price for a defined job; this lets the work grow without the fee growing. Ask for: a scope tied to a specific deliverable list, plus "Additional work is billed separately upon written approval."
2. Payment "on completion" with no deposit
Looks like: "Fees are payable upon completion and acceptance of all Services." Why it's risky: you finance 100% of the project and carry all the non-payment risk. Ask for: a deposit (25–50%) and milestone payments, with Net 15–30 terms.
3. "Sole satisfaction" acceptance
Looks like: "Deliverables are subject to acceptance at the Client's sole and absolute discretion." Why it's risky: the other party can refuse to accept — and refuse to pay — for any reason or none. Ask for: objective acceptance criteria and a deemed-acceptance window: "accepted if no written objection within 7 business days."
4. IP transfer that ignores payment
Looks like: "All work product shall be the exclusive property of the Client upon creation." Why it's risky: they own your work the moment you make it — even if the invoice never gets paid. Ask for: "Ownership transfers upon receipt of full payment," plus carve-outs for your pre-existing tools and your right to portfolio use.
5. One-sided, perpetual confidentiality
Looks like: a multi-page NDA that binds only you, "in perpetuity," covering "any and all information." Why it's risky: unlimited duration and scope is impossible to comply with and exposes you to claims for years. Ask for: mutual confidentiality, a 2–3 year term, and standard exclusions (public, already-known, or independently-developed information).
6. Uncapped or one-way indemnification
Looks like: "Provider shall indemnify, defend and hold harmless the Client from any and all claims..." with nothing the other direction. Why it's risky: indemnification means you cover the other side's legal costs and losses. Uncapped and one-way, this can dwarf your entire fee. Ask for: mutual indemnification, limited to losses caused by your breach or negligence — not the client's own actions.
7. No limitation-of-liability cap
Looks like: silence on liability, or your liability capped at an amount unrelated to the deal. Why it's risky: without a cap, a small project can expose you to a large claim. Ask for: "Total liability shall not exceed the fees paid under this Agreement," and a mutual exclusion of indirect/consequential damages.
8. Termination for convenience — one way
Looks like: "Client may terminate at any time for any reason upon notice," with no matching right for you and no payment for work done. Why it's risky: you can be cut loose mid-project with nothing for completed work. Ask for: mutual termination rights, a notice period, and a kill fee covering work completed plus a portion of the remaining fee.
9. Auto-renewal you can't easily exit
Looks like: "This Agreement renews automatically for successive 12-month terms unless cancelled 90 days before renewal." Why it's risky: miss a narrow cancellation window and you're locked in for another year. (Common in retainers, tooling, and SaaS — see auto-renewal traps.) Ask for: a shorter notice window (30 days), or month-to-month after the initial term.
10. Lopsided governing law / venue
Looks like: disputes governed by a distant jurisdiction convenient only to the other party. Why it's risky: enforcing your rights across a border is often impractical for a small business — the clause becomes a shield for them. Ask for: a neutral or local jurisdiction, or mediation/arbitration as a first step.
What are the 10 biggest service-agreement red flags? The quick scan
| Red flag | The fix in one line |
|---|---|
| Open-ended scope | Tie fee to a defined deliverable list |
| No deposit | 25–50% up front + milestones |
| "Sole satisfaction" acceptance | Deemed-acceptance in 7 days |
| IP transfers before payment | Transfer on full payment |
| Perpetual one-way NDA | Mutual, 2–3 yrs, with exclusions |
| Uncapped indemnification | Mutual, fault-based |
| No liability cap | Cap at fees paid |
| One-way termination | Mutual + notice + kill fee |
| Auto-renewal trap | 30-day exit / month-to-month |
| Distant jurisdiction | Neutral/local venue |
Don't memorize them — let the AI flag them
You can keep this list handy, or FixMyContract can check for all ten (and more) for you: upload the agreement and the risky clauses it finds are highlighted, scored, and paired with a plain-English fix.
👉 Check your agreement free — your first analysis is free, no card, no deadline to use it.
Reviewing contracts regularly? See plans.
How this guide was made
Prepared by the FixMyContract team in plain English.
Last reviewed: August 20, 2026. This is general information, not legal advice.
Try it on your own contract
See your two most important findings in full, no card.
Try it — no account