Identify broad indemnity, unlimited revisions, unclear ownership, and payment traps.
Key takeaways
- Compare liability caps with the total contract value.
- Limit revisions by count, scope, and feedback timing.
- Make ownership transfer conditional on payment.
Red flags worth slowing down for
A one-sided agreement asks a freelancer to indemnify the client for every possible loss, allows unlimited revisions, transfers all rights before payment, and lets the client terminate without paying for completed work. Each provision shifts a different risk; reviewing them as a group shows the real commercial imbalance.
Run a contract-specific review
Review risk-shifting clauses together rather than one at a time. Unlimited liability, subjective acceptance, immediate ownership transfer, and termination without payment can combine to leave one party carrying nearly every commercial risk even if each clause looks familiar in isolation.
1. Rank the exposure
Estimate the realistic loss under indemnity, warranty, confidentiality, and delay provisions.
2. Compare obligations
Check whether notice, cure, cooperation, insurance, and liability duties apply to both parties fairly.
3. Test a dispute
Walk through late feedback, rejected work, a third-party claim, and early termination.
4. Record exceptions
Put negotiated carve-outs and precedence between the main agreement and attachments in writing.
Stress-test the difficult case
A common failure appears when the main agreement, statement of work, purchase order, and online policy allocate the same risk differently. One document may cap liability while another requires broad indemnity, or a statement of work may promise a result that the master agreement describes only as a service. Check the order-of-precedence clause and every incorporated document, including policies that can change by URL. If the contract does not establish which term controls, the apparent protection in one section may disappear when the documents are read together.
Verification pass before signing
Create a short risk register with columns for the event, responsible party, notice deadline, cure right, financial exposure, insurance response, and controlling clause. Populate it for late delivery, data loss, infringement, confidentiality breach, nonpayment, and early termination. Compare the maximum credible exposure with project fees and available insurance rather than relying on the heading of a liability clause. Any blank or contradictory row becomes a negotiation item. Attach the final register to the project file as evidence of what the business actually reviewed before signature.
Evidence to retain
Save every redline, comment thread, approved exception, referenced policy, exhibit, and the final clean copy so later readers can reconstruct the negotiation.
Worked example
A liability cap equal to fees paid may still exclude confidentiality or infringement claims. Those exclusions should be evaluated separately because they can make the stated cap largely ineffective.
What to verify
1. Scope
Compare liability caps with the total contract value.
2. Trigger
Limit revisions by count, scope, and feedback timing.
3. Evidence
Make ownership transfer conditional on payment.
4. Fallback
Require payment for accepted work at termination.
Build the decision record
| Review item | Record before signing |
|---|---|
| Rank the exposure | Estimate the realistic loss under indemnity, warranty, confidentiality, and delay provisions. |
| Compare obligations | Check whether notice, cure, cooperation, insurance, and liability duties apply to both parties fairly. |
| Test a dispute | Walk through late feedback, rejected work, a third-party claim, and early termination. |
| Record exceptions | Put negotiated carve-outs and precedence between the main agreement and attachments in writing. |
Warning signs
- Broad “any and all losses” language.
- Acceptance controlled only by subjective satisfaction.
- Non-compete language broader than the project.
Questions to resolve before signing
- What would prove that “rank the exposure” is satisfied if the parties later disagree?
- What would prove that “compare obligations” is satisfied if the parties later disagree?
- What would prove that “test a dispute” is satisfied if the parties later disagree?
- What would prove that “record exceptions” is satisfied if the parties later disagree?
Sources and further reading
- IRS: Independent contractor status
- U.S. Copyright Office: Works made for hire
- FTC: Endorsements and testimonials
External sources explain general rules and terminology. Your signed agreement, current policy, jurisdiction, provider documents, and individual facts control the actual outcome.
Open the related ContractFixPro tool