Contract Risk Scanner
Paste your contract text to identify risky clauses, get suggestions, and understand what to negotiate.
About the Contract Risk Scanner
Paste or upload contracts to identify risky clauses, get replacement suggestions, and calculate risk scores.
What you can do with it
- Risk score (0-100)
- Color-coded findings
- Clause detection
- Replacement suggestions
Frequently asked questions
What contract clauses are dangerous for freelancers?
The usual suspects: unlimited revisions, IP transferring before final payment, kill-fee clauses that let the client cancel without paying for work done, broad non-competes, 'work for hire' language on pre-existing materials, and payment terms that let the client net-60+ while you have net-30 obligations of your own. The scanner flags each of these with a severity level.
Can I really check a contract with a free tool?
Yes — with the right caveat. The scanner applies pattern checks against common freelancer-unfriendly clauses and suggests replacement language, which catches most real-world problems (it's tuned for typical web/design/dev/service agreements). It is not legal advice; for high-value or unusual contracts, a one-hour review by a tech-savvy lawyer is cheap insurance.
What should a good freelance contract include?
Parties and project scope (with an exclusions list), deliverables and acceptance criteria, timeline and milestones, payment schedule (deposit + milestones, due dates, late-fee rate), IP transfer tied to final payment, revision limits, confidentiality, termination with a kill fee for work completed, and governing law. Missing any of those is a negotiation signal, not a formality.
Related free tools
Your results will appear here
Fill in the details on the left and hit calculate to see your numbers.
Contract Risk Scanner: Common Questions
What contract clauses are dangerous for freelancers?
The usual suspects: unlimited revisions, IP transferring before final payment, kill-fee clauses that let the client cancel without paying for work done, broad non-competes, 'work for hire' language on pre-existing materials, and payment terms that let the client net-60+ while you have net-30 obligations of your own. The scanner flags each of these with a severity level.
Can I really check a contract with a free tool?
Yes — with the right caveat. The scanner applies pattern checks against common freelancer-unfriendly clauses and suggests replacement language, which catches most real-world problems (it's tuned for typical web/design/dev/service agreements). It is not legal advice; for high-value or unusual contracts, a one-hour review by a tech-savvy lawyer is cheap insurance.
What should a good freelance contract include?
Parties and project scope (with an exclusions list), deliverables and acceptance criteria, timeline and milestones, payment schedule (deposit + milestones, due dates, late-fee rate), IP transfer tied to final payment, revision limits, confidentiality, termination with a kill fee for work completed, and governing law. Missing any of those is a negotiation signal, not a formality.
Explore the rest of the toolkit in the free tools directory, or read practical guides in the blog.