How to Write a Contract: Step-by-Step Guide for Freelancers

How to Write a Contract

A well-written contract is the single most effective tool for protecting your business, setting clear expectations, and ensuring you get paid. For freelancers and small business owners, contracts prevent misunderstandings about scope, deliverables, timelines, and payment terms -- and give you legal recourse if a client fails to pay or disputes your work. This guide walks through every essential clause in a freelance contract and how to write each one clearly and effectively.

Why Every Project Needs a Contract

Clients you trust most are often the ones who create the most payment problems. Verbal agreements, email threads, and casual understandings do not constitute enforceable contracts in most jurisdictions. A signed contract:

• Defines exactly what work is included and excluded
• Establishes payment terms and what happens when they are not met
• Clarifies who owns the intellectual property
• Limits your liability for client-side failures
• Provides legal grounds for collecting payment through a dispute or court process if necessary

Even for small projects, a simple contract protects both parties and professionalizes the relationship.

Section 1: Parties and Effective Date

Begin with a clear identification of the parties:

"This Agreement is entered into as of [date] between [Your Full Business Name] ('Contractor') with a principal place of business at [your address], and [Client Full Legal Name] ('Client') with a principal place of business at [client address]."

Use your business's legal name (or your personal name if operating as a sole proprietor). For corporate clients, use their full legal entity name as it appears in their registration documents.

Section 2: Scope of Work

This is the most important section of any contract. Define exactly what you will deliver:

• List deliverables explicitly ("5 designed social media graphics per week" -- not "social media graphics")
• Specify file formats, quality standards, and delivery method
• Define what is NOT included (explicitly excluding scope prevents "can you just..." requests)
• Set revision rounds included in the price (e.g., "2 rounds of revisions; additional revisions billed at $X/hour")

Be specific. Vague scope descriptions are the leading cause of contract disputes.

Section 3: Project Timeline

"The Contractor will deliver initial concepts by [date]. Final deliverables are due by [date], contingent on Client providing feedback within [X] business days of each submission."

Include:

• Project start date
• Key milestone dates
• Final delivery date
• Consequence of client-side delays ("Timeline extends day-for-day if Client feedback is delayed beyond X business days")

Section 4: Fees and Payment Terms

Specify the total fee, payment schedule, and what happens if payment is late:

"Client agrees to pay Contractor a total project fee of $[X]. Payment schedule: 50% deposit ($[X]) due upon signing; remaining balance ($[X]) due upon final delivery.

Late payments accrue interest at [1.5%] per month after the due date. Contractor reserves the right to pause work and withhold final deliverables until all outstanding balances are paid."

Include your payment methods and where to send payment. See the freelancer payment terms guide for detailed guidance on structuring payment terms.

Section 5: Intellectual Property Rights

Who owns the work you create? This is often the most contested clause:

Option A (Work-for-hire / full transfer): "Upon receipt of full payment, Contractor assigns all intellectual property rights in the deliverables to Client."

Option B (License only): "Contractor grants Client a perpetual, non-exclusive license to use the deliverables for [specified purposes]. Contractor retains ownership of all underlying intellectual property."

Option C (Portfolio rights retained): "Client receives full ownership upon payment. Contractor retains the right to display the work in their portfolio."

Most freelancers use Option A (full transfer upon payment) with portfolio rights retained. Whatever you choose, be explicit.

Section 6: Confidentiality

If you will have access to sensitive client information:

"Contractor agrees to keep confidential all non-public information shared by Client and to use such information only for the purposes of performing the services."

Section 7: Limitation of Liability

Cap your financial exposure:

"In no event shall Contractor's total liability to Client exceed the fees paid by Client under this Agreement."

This clause prevents a client from suing you for consequential damages (lost profits, business disruptions) far exceeding what they paid you.

Section 8: Termination Clause

"Either party may terminate this Agreement with [14 days] written notice. Upon termination, Client shall pay for all work completed through the termination date at the pro-rated rate."

Specify what happens to work in progress: do you deliver what is done? Does the client get their deposit back? Address these scenarios clearly.

Section 9: Governing Law and Dispute Resolution

"This Agreement shall be governed by the laws of the State of [your state]. Any disputes arising from this Agreement shall be resolved through binding arbitration in [your city], or in the alternative, in the courts of [your county]."

Choosing your home jurisdiction for disputes is standard and favorable to you as the contractor.

Using Eonebill for Contracts and Invoices

Create and send contracts alongside professional invoices through Eonebill -- then convert accepted contracts directly into project invoices. See also the freelance proposal guide for writing winning proposals before the contract stage, and how to write an invoice email for professional billing communication.

Contract Red Flags: Terms to Push Back On

When clients send their own contracts for you to sign, watch for clauses that are one-sided or dangerous for freelancers:

Unlimited revision clauses: "Revisions as needed until client satisfaction" is open-ended and unlimited. Push back for a specific number of revision rounds with additional revisions billed at your hourly rate.

IP assignment before payment: Some client contracts require you to transfer all intellectual property rights at the time of delivery -- not upon receipt of payment. This means you could deliver work, receive no payment, and have no legal claim to your own work product. Negotiate to tie IP transfer to receipt of full payment.

Non-compete clauses: A broad non-compete that prevents you from working in your industry or with similar clients is often unenforceable but still creates legal uncertainty. Push back on overly broad non-competes, especially those with long duration (more than 6 months) or wide geographic scope.

Unlimited liability clauses: Contracts that make you responsible for any and all damages the client may suffer -- including consequential damages, lost profits, and reputational harm -- create exposure far beyond your project fee. Insist on a liability cap equal to the fees paid under the contract.

Automatic renewal clauses: Some retainer agreements auto-renew unless explicitly canceled 30-60 days before the renewal date. These are easy to miss. Note auto-renewal terms in your calendar when signing.

Unilateral payment terms changes: Clauses that allow the client to change payment schedules, reduce fees, or withhold payment at their discretion should be removed entirely.

When to Use a Letter of Agreement vs a Formal Contract

For smaller or shorter-term projects, a letter of agreement (LOA) -- a shorter, less formal document -- provides adequate protection without the complexity of a full contract:

An LOA typically covers: the project scope (1-2 paragraphs), the fee and payment schedule, the timeline, IP ownership (one sentence), and signature lines. For projects under $2,000 or with known, trusted clients, an LOA is often sufficient.

A full contract with all the clauses described in this guide is appropriate for: new clients, projects over $2,000, complex or multi-phase projects, work that creates significant intellectual property, and any situation where the stakes of a dispute are high.

For contract templates, proposal tools, and professional invoicing, use Eonebill. See the freelance proposal guide for the pre-contract stage, and freelancer payment terms for structuring your payment clauses.

Contract Red Flags to Avoid

Learning to write good contracts also means learning to spot bad ones when clients send their own. Watch for:

Unlimited revision clauses: Language like "revisions until the client is satisfied" or "revisions as needed" with no cap exposes you to infinite unpaid work. Counter with a specific number of revision rounds and a clear definition of what constitutes a "revision" versus new scope.

Payment on client approval: If your payment is conditioned on "client's satisfaction" or "approval," the client can withhold payment indefinitely by simply not approving. Change this to payment on delivery of specified deliverables, regardless of subjective satisfaction.

IP assignment before full payment: Some contracts assign intellectual property rights to the client immediately, even before you have been paid. Counter with: "IP transfers to Client upon receipt of full payment."

Jurisdiction in a distant state: A contract that specifies disputes will be resolved in a court 2,000 miles away is impractical for you. Negotiate for your own jurisdiction or for remote/online arbitration.

Broad indemnification clauses: Some client contracts ask you to indemnify them for anything that goes wrong, including their own negligence. Narrow indemnification to cover only your own actions and omissions.

When to Get a Lawyer's Review

For contracts under $5,000 with established clients, a well-drafted standard contract you wrote is usually sufficient. For contracts above $10,000, projects with significant IP creation, retainer agreements, or any contract with a large company's legal team behind it -- have an attorney review before you sign. The $200-$500 review fee is insurance against a contract that costs you thousands in disputes. Use Eonebill's invoicing tools to connect your contract terms directly to your invoice payment terms, ensuring consistency between what you agreed to and what you bill.