Red Flags in a Contractor Agreement
Short answer: the terms worth stopping on are the ones that move risk to you without moving money. One-sided termination, payment that depends on approval with no deadline, assignment language reaching past the deliverable, and indemnity with no ceiling. Most of them are not there to trap you. They are there because the template was written for the other side, which is also why a short list of specific edits usually gets approved.
Eight to look for
Each of these says what the clause does, what it costs you, and when it is genuinely reasonable. That last part matters. Treating every term as predatory is how people end up unable to negotiate any of them.
1. Termination for convenience on one side only
What it says. The client can end the agreement at any time on short notice. You cannot, or you need cause.
What it costs. You turned down other work to be available and can be released the week before the invoice.
When it is fair. Common and often reasonable in larger paper. Ask for notice that matches your planning horizon, payment for work performed, and a fee for the cancelled remainder.
2. Payment on acceptance, with no deadline to accept
What it says. The invoice becomes due when the client approves the work, and nothing says when approval has to happen.
What it costs. A 30-day payment term becomes indefinite, and the delay is entirely inside the client's control.
When it is fair. Fix it with a deemed-acceptance window: work counts as accepted if no written rejection arrives within a set number of days. Watch the number, though. A very short window with automatic approval cuts against whoever has to review.
3. IP assignment that reaches past the deliverable
What it says. Language assigning not just what you deliver, but what you conceive, develop or learn during the engagement.
What it costs. On a plain reading it can capture your reusable components, and sometimes the general skill you arrived with.
When it is fair. Assignment of the deliverable is normal and expected. Carve out your pre-existing tools and templates by name, and tie the transfer to full payment so ownership moves when the money does.
4. Indemnity with no cap
What it says. You agree to cover the client's losses from claims, with no ceiling on the amount.
What it costs. In the bad case your exposure has no relationship to what you were paid. This is the clause most likely to be skipped and most likely to be catastrophic.
When it is fair. A cap at the fees paid under the agreement is the ordinary ask. Carve-outs above the cap for your own gross negligence or IP infringement are normal and worth conceding.
5. Confidentiality with no end date
What it says. The obligation runs for as long as the information stays confidential, which is to say forever.
What it costs. Less dangerous than it sounds day to day, but it is an obligation you carry indefinitely with no way to close the file.
When it is fair. Perpetual protection for genuine trade secrets is standard. A fixed term of a few years for everything else is the usual compromise.
6. The client can change the terms unilaterally
What it says. A clause letting one side amend the agreement, or the rates, or the policies it incorporates, on notice.
What it costs. Whatever you negotiated is provisional. This often hides in a reference to an external policy page rather than in the amendment clause.
When it is fair. Rarely worth accepting as written. Ask that changes affecting price or scope require both signatures.
7. Expenses and taxes left unaddressed
What it says. Nothing about who pays for travel, software, subcontractors or the tax treatment of the relationship.
What it costs. It all comes out of your fee by default, and the answer arrives after you have already spent the money.
When it is fair. One sentence fixes it. Say what is reimbursable and whether it needs pre-approval.
8. Disputes routed somewhere expensive
What it says. Governing law and venue in a distant jurisdiction, sometimes with mandatory arbitration and costs split evenly.
What it costs. It can make enforcing a modest invoice cost more than the invoice. That is often the point.
When it is fair. Standard in enterprise contracts and usually not movable. It matters most on small deals, where it quietly removes your only leverage.
The flag that is not on the page
The list above is all things a contract says. A large share of real risk is what it does not say: no cap on liability, no kill fee if the project is cancelled, no consequence for late payment, nothing about who owns the work. Absence is much harder to notice than presence, because there is nothing to read. Going through a checklist of what should be present is a different operation from reading the document, and it has to be done deliberately.
Where we fit
StraightTerms runs the same fixed set of passes over every document, including a gap check for clauses that should be there and are not. Every finding quotes the exact clause it refers to, so you can hold it against your own copy and confirm it rather than trusting it.
Your first review is free with no signup, and after that an email unlocks three a month. This is AI analysis and not legal advice, and on anything with real money attached the point is to arrive at a lawyer with specific questions rather than to skip one.
Common questions
- Is it a red flag if the contract has no liability cap?
- It is worth raising every time. Without a cap, your worst case is unrelated to what you were paid. Asking for liability to be capped at the fees under the agreement is an ordinary, routine request rather than an aggressive one, and it is usually granted at freelance and small-vendor sizes.
- Can a client really own everything I make?
- They can own everything the contract says they own, and broadly drafted assignment clauses do reach past the specific deliverable. The fix is narrow rather than confrontational: name your pre-existing tools and templates in a carve-out, and make the assignment effective on full payment.
- What does termination for convenience actually mean?
- It means ending the agreement without needing a reason or any breach by the other side. It is common in larger contracts and not inherently unfair. What makes it one-sided is when only the client has it and nothing is owed on cancellation beyond work already delivered.
- Should I just refuse to sign a contract with red flags in it?
- Usually not. Most of these terms exist because the client's template was drafted for the client, not because anyone is trying to trap you. A short list of specific edits gets approved far more often than a general objection does, and refusing outright mostly costs you the work.
Related
- What a freelance contract should include
The clauses that decide what happens when the work or the money goes wrong.
- Can you use ChatGPT for contract review?
Where a chat assistant genuinely helps, and the three places it does not.
- Is an unsigned contract binding?
The five things that decide it besides the missing signature, and what to gather before you reply to anyone.
- What does indemnification mean in a contract?
Who pays whose costs when a third party brings a claim, and why a liability cap may not reach it.
- What is a liquidated damages clause?
What triggers the fixed amount, whether it accrues over time, whether it has a ceiling, and whether it is the only remedy.
- What does time is of the essence mean in a contract?
What the phrase changes about a missed date, which dates it actually covers, and where the consequences are written instead.