Review a Freelance Contract in Plain English and Flag Risky Clauses
Paste a client contract and get a plain-English risk table covering IP, payment, liability, termination and non-compete, with a suggested redline for each clause.
You getSummary and table with columns
Prompt
Act as a contract reviewer who helps freelancers understand client agreements before they sign.
I will paste a freelance or consulting contract right after this message. Review it in plain English and flag the clauses that create risk for me as the freelancer.
Rules:
1. Check at least these areas: intellectual property and ownership, payment terms and late fees, liability and indemnity, termination and kill fees, non-compete and non-solicit, and scope or revision limits.
2. For every flag, cite the clause number or a short quoted excerpt so I can find it.
3. Rate each risk High, Medium or Low, and explain in one sentence what could happen to me in practice.
4. Give a suggested redline for each flag. Write replacement wording I could send the client, not general advice.
5. If an important protection is missing entirely, such as a late-payment term, list it as a flag.
Output format:
- Summary: 3 sentences on overall risk and the top 2 issues to negotiate.
- Table with columns: Clause | Area | Risk | What it means for you | Suggested redline
- Missing protections: bulleted list
- Questions to ask the client: 3-5 bullets
This is not legal advice. State any assumptions about jurisdiction, and remind me to have a lawyer licensed where I work check the contract before I sign, especially for high-value or long-term work.Example output
Tips and common edits
Why this works
- Naming the six risk areas stops the model from skimming past IP, indemnity or kill-fee terms.
- Asking for ready-to-send redline wording turns a review into something you can use in negotiation.
- Flagging missing protections catches gaps such as no deposit, which a clause-by-clause read would miss.
Use before signing a new client agreement or renewal. Paste the full contract text into ChatGPT, Claude or Gemini right after the prompt. Remove bank details or personal IDs first.
Common edits
- Add your country or state so the review uses the right jurisdiction assumptions.
- Ask for a polite email to the client proposing the top three redlines.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Explain a Contract Clause in Plain English and What It Means for You
Paste one contract clause and get a line-by-line plain-English translation, vague terms flagged, a worst-case example, and three questions to ask the other side.
Build a New-Client Onboarding Email Sequence and Kickoff Checklist
Get a dated onboarding email sequence, focused intake questions, exact access requests, a timed kickoff agenda and a checklist so day one isn't blocked.
Draft a Scope of Work with Deliverables, Exclusions and Revision Limits
You get a client-ready scope of work with a deliverables table, acceptance criteria, a specific 'not included' list, revision caps and a change request process.
Plan a Weekly Freelance Schedule for Client Work, Admin and Outreach
Get an hour-by-hour weekly plan that blocks deep client work, invoicing and new-business outreach, keeps buffer time for overruns, and flags overbooking.
Politely End a Bad-Fit Client Relationship with a Clean Handover Plan
Get a calm, firm exit email plus a wrap-up checklist and pushback reply, so you can end work with a difficult client and keep your reputation intact.
Raise Your Freelance Rates with Existing Clients Without Apologizing
You get a short rate increase email with notice date, new rate and one reason, plus ready reply scripts for pushback, delay requests and a client who leaves.