How to Write a Freelance Contract From Scratch (7-Point Checklist)

A client ghosts you after three rounds of revisions. A project doubles in scope but the budget stays the same. You finish the work, send the invoice, and hear nothing for 60 days. These situations happen constantly — and almost all of them come down to a weak or missing contract.

Writing a freelance contract doesn't require a law degree. It requires knowing what to include and why each piece matters. Here's a practical checklist of the seven things every freelance contract should cover, with sample language for each.

---

1. Parties and Contact Information

This sounds obvious, but contracts get voided or disputed because the right parties weren't properly identified. Name the full legal names of both parties — not just "Client" and "Freelancer." If you're a registered LLC or sole proprietor doing business under a different name, include that too.

Sample language:

This Agreement is entered into between Jane Doe, doing business as Doe Design Studio ("Contractor"), located at [address], and Acme Corp, a Delaware corporation ("Client"), located at [address].

Include email addresses and phone numbers here as well. If a dispute ever arises, you want a clear record of who was party to the agreement and how they can be reached.

---

2. Scope of Work and Deliverables

Vague scope is the root cause of most freelance disputes. "Website redesign" means something different to you than it does to your client. Be specific about what you're delivering, what format it's in, and what's explicitly excluded.

Sample language:

Contractor will design five (5) custom website page templates in Figma, including homepage, about page, services page, blog index, and contact page. Deliverables include source files and one round of revisions per template. Copywriting, development, and SEO are not included in this agreement.

If the client asks for something outside this scope later, you have a clear baseline to reference — and a basis for a change order.

---

3. Timeline and Milestones

A deadline without milestones is just a hope. Break the project into phases with specific dates attached to each. This protects both sides — you have a schedule to hold yourself to, and your client knows when to expect what.

Sample language:

Project timeline is as follows: kickoff call and brief review by [date]; initial concepts delivered by [date]; client feedback due within five (5) business days of each delivery; final files delivered by [date]. Timeline is contingent on client providing feedback within the specified windows. Delays caused by late client feedback will extend the project timeline accordingly.

That last sentence matters. Clients who sit on feedback for three weeks and then expect you to hit the original deadline are a common problem. Build in the protection upfront.

---

4. Payment Schedule and Late Fees

Don't work for free. Specify the total project fee, how it's broken up, and what happens if payment is late. A 50% deposit upfront is standard for project-based work — it filters out non-serious clients and covers your time if things go sideways.

Sample language:

Total project fee: $4,500. Payment schedule: 50% ($2,250) due upon signing; 50% ($2,250) due upon final delivery. Invoices are due within fourteen (14) days of receipt. Payments received after the due date will incur a late fee of 1.5% per month on the outstanding balance. Final files will not be transferred until payment is received in full.

That last sentence is your leverage. Don't hand over deliverables before you've been paid.

---

5. Intellectual Property Transfer

Who owns the work? By default in the US, the creator owns copyright — which means your client doesn't automatically own what you make for them unless the contract says otherwise. Decide upfront whether you're transferring full ownership, licensing the work, or retaining certain rights.

Sample language (full transfer):

Upon receipt of full payment, Contractor assigns to Client all intellectual property rights in the final deliverables, including copyright. Contractor retains the right to display the work in their portfolio unless otherwise agreed in writing.

Sample language (license only):

Contractor grants Client a non-exclusive, perpetual license to use the final deliverables for [specific purpose]. Contractor retains ownership of all underlying source files and original work.

If a client insists on owning source files and all underlying assets, that's a reasonable ask — but it typically warrants a higher fee.

---

6. Kill Fee and Cancellation Terms

Projects get cancelled. Clients run out of budget, change direction, or just disappear. A kill fee ensures you're compensated for work completed if the project ends early — and it discourages clients from cancelling on a whim.

Sample language:

Either party may terminate this agreement with fourteen (14) days written notice. In the event of termination by Client, Client agrees to pay for all work completed to date, plus a kill fee equal to 25% of the remaining unpaid balance. The initial deposit is non-refundable.

Adjust the percentage based on your situation. Some freelancers charge 50% of the remaining balance as a kill fee — especially for projects where they've turned down other work to take this one on.

---

7. Dispute Resolution and Governing Law

If something goes wrong, how do you resolve it? Specifying this upfront saves both parties from expensive, unpredictable litigation. Most freelancers opt for mediation or arbitration before going to court — it's faster and cheaper. You also need to specify which state's laws govern the contract.

Sample language:

This Agreement shall be governed by the laws of the State of [Your State]. In the event of a dispute, the parties agree to first attempt resolution through good-faith negotiation. If unresolved within thirty (30) days, disputes will be submitted to binding arbitration in [Your City, State] under the rules of the American Arbitration Association.

Choose the state where you're located. If you're based in Texas and your client is in New York, you don't want to be flying to New York to resolve a $3,000 dispute.

---

A Few Practical Notes Before You Send

Get the contract signed before you start any work — not after the kickoff call, not "once things get going." Before. A signed contract is your only real protection.

Use plain language. Contracts full of legalese are harder to enforce because courts sometimes interpret ambiguous terms against the drafter. Clear, specific language is better than trying to sound like an attorney.

Keep a copy. Both parties should have a signed version. If you're using e-signature tools like DocuSign or HelloSign, the platform stores copies automatically.

Review your contract annually. Your rates change, your services evolve, and your standard terms should keep up.

A well-written freelance contract isn't about distrust — it's about clarity. Clients who respect your work will respect a professional contract. The ones who push back on basic terms are usually the ones you'd regret working with anyway.

Have a contract to review? Try KlausClause.

This article is for informational purposes only and does not constitute legal advice.