What Should Be in a Freelance Contract?

Disclaimer: This article is for educational purposes only and does not constitute legal advice. Every freelance situation is different. If you are dealing with high-value engagements, complex IP arrangements, or cross-border work, consult a qualified legal professional in your jurisdiction.

You landed the client. You agreed on the rate. Work begins next week. Now comes the part most freelancers either rush through or skip entirely: the contract.

This is a mistake. Not because contracts are bureaucratic formalities, but because a contract is the only document that makes your agreement real. Emails get misread. Verbal understandings get misremembered. A signed contract stays the same.

According to a 2025 Contractor Management Report published by Remote, 85% of freelancers have had invoices paid late at least some of the time, and 21% are paid late more often than on time. Most of those situations trace back to one source: ambiguity about what was agreed. A clear contract closes that ambiguity before it becomes a dispute.

This guide covers every clause a freelance contract should include, why each one matters, and what happens when it is missing.

Why Contracts Protect Both Parties, Not Just the Freelancer

There is a common assumption that asking for a contract signals distrust. It does not.

A contract is not a trap. It is a record of what both parties agreed to before work began. The client benefits from clarity on exactly what they are getting, when they will get it, and what the process looks like if something changes. You benefit from the same. Disputes almost never arise from bad intentions. They arise from different interpretations of an incomplete agreement.

A good contract reflects a fair deal. Its purpose is to record that deal so neither party has to rely on memory or hope.

The Core Clauses: What Every Freelance Contract Needs

Clause 1: Parties

What it is: The identification of both parties involved in the agreement. This means full legal names, business names where applicable, and registered addresses.

Why it matters: This clause establishes who the contract is actually between. Without it, there is no legal basis to determine whether the agreement applies to the specific individuals or entities in a dispute.

What happens without it: A client might claim the agreement was made with a different contact at their company, or dispute whether it applies to their legal entity at all.

What it should include: Your full legal name and business name if you operate under one. The client’s full legal name, whether individual or company. Registered addresses for both. If the client is a company, include the registered company name, not just the name of your contact there.

Clause 2: Scope of Services

What it is: A precise description of what work you will deliver.

Why it matters: This is the single most important clause in any freelance contract. Most freelance disputes do not begin with bad faith. They begin when the freelancer delivers what they understood was agreed, and the client expected something different. Neither party is lying. The contract just failed to specify.

What happens without it: The client expects X. You deliver Y. Both of you believe you are right. Without a written reference point, there is no way to resolve this cleanly, and the working relationship rarely survives it.

What it should include: Specific deliverables listed individually, not described in categories. What is explicitly not included. Any dependencies on client input, such as brand assets, copy, or approvals. Acceptance criteria where applicable.

The specificity principle matters here more than anywhere else. “Website design” is not a scope. “Design of homepage, about page, services page, and contact page in Figma, delivered as production-ready files and exported assets, responsive for desktop and mobile, excludes copywriting, photography, and development” is a scope. The difference between those two descriptions is the difference between a smooth project and a dispute.

When a client requests additional work that falls outside the written scope, you can respond professionally: “This falls outside what we agreed in the contract. I am happy to take it on as an additional project at my standard rate.” That conversation is only possible if you have a scope clause to point to.

Clause 3: Payment Terms

What it is: The complete payment arrangement, including the amount, schedule, method, and consequences for non-payment.

Why it matters: Payment disputes are the most common legal issue freelancers face. Clear payment terms prevent most of them. Vague language creates room for delay. Specific language closes it.

What happens without it: “I thought we agreed net 60” against “I thought it was due on delivery” is an argument with no written resolution.

What it should include: The total fee or rate. The payment schedule, including deposit amount and timing, milestone payments if applicable, and final payment timing. The payment method. How you will send invoices. The due date after invoicing (net 14, net 30). Late payment consequences, including any interest rate you will apply and your right to suspend work on unpaid accounts.

For recurring client relationships, ruul.io/subscriptions covers how to handle retainer and subscription billing so your payment cycle is automated rather than chased.

Clause 4: Revision Policy

What it is: A definition of how many rounds of revisions are included and what constitutes a revision versus a new request.

Why it matters: Without this clause, a client can request unlimited revisions while claiming everything is within the original scope. You either absorb the cost or damage the relationship by charging for something the client genuinely believes they already paid for.

What happens without it: Endless revision cycles with no clear end point. The freelancer works more hours than were priced. The client wonders why the freelancer seems reluctant to improve the work.

What it should include: The number of included revision rounds. A definition of what counts as a revision, meaning refinement within an agreed direction, versus a change, meaning a new direction or additional deliverables. How revision requests should be submitted (in writing, consolidated). The rate for additional revisions beyond what is included.

Clause 5: Intellectual Property Ownership

What it is: A statement of who owns the work product once it is created and delivered.

Why it matters: Without this clause, IP ownership defaults to jurisdiction-specific laws that often surprise both parties. In most jurisdictions, the creator retains copyright by default even when paid to create something. The client may believe they own work they have purchased. Legally, they may not.

What happens without it: A client who built marketing materials based on your design discovers they cannot legally enforce their rights over that work. Or you try to include the work in your portfolio and receive a cease-and-desist.

There are three ways to structure IP in a freelance contract:

Full assignment to client: All intellectual property transfers to the client upon full payment. This is the most common arrangement for commercial work where the client needs to own the output outright.

License to client: You retain ownership but grant the client specified rights to use the work. Common in photography, illustration, and music licensing. You can restrict usage to specific purposes, geographies, or time periods.

Freelancer retains underlying IP: You transfer ownership of the specific deliverables while retaining your pre-existing tools, code libraries, frameworks, or methodologies. The client receives what they paid for. Your underlying assets remain yours. This is standard in software development.

What it should include: A clear statement of which model applies. When transfer occurs. What rights are licensed if the work is licensed rather than assigned. Explicit permission for you to include the work in your portfolio. A statement that IP transfer is conditioned on receipt of full payment.

That last point is critical. If a client receives your work and then refuses to pay, a contract that conditions IP transfer on full payment means they are using your property without a license. That gives you practical and legal leverage that an unconditional transfer does not.

Clause 6: Independent Contractor Status

What it is: A statement that you are an independent contractor, not an employee.

Why it matters: Worker misclassification carries significant tax and legal consequences for both parties. If the working relationship is treated as employment, the client may become liable for employment taxes and benefits. You may lose protections that come with self-employed status. A clear independent contractor clause reduces this risk.

What happens without it: Increased misclassification risk, particularly when the contract’s other terms resemble employment. Courts and tax authorities look at the totality of the relationship, not just the label.

What it should include: A statement that you are an independent contractor. A statement that you are responsible for your own taxes. Confirmation that you have the right to work with other clients simultaneously. Confirmation that the client controls the outcome of your work, not the means and methods by which you produce it.

Note: a non-compete clause directly undermines this clause. Restricting where a contractor can work signals economic dependence, which is one of the central criteria tax authorities use when evaluating misclassification. If a client asks for a non-compete in a freelance contract, this is a flag worth raising.

Clause 7: Confidentiality

What it is: Mutual obligations on both parties to keep specified information private.

Why it matters: Freelancers routinely access sensitive client information: business strategy, financial data, unreleased products, customer databases. Clients need confidence that this information stays protected. You may also share your own methods, processes, or pricing structures during the engagement.

What happens without it: If either party discloses information that was understood to be confidential, there is no legal basis to enforce consequences without a prior written agreement.

What it should include: A definition of what counts as confidential information. Obligations on both parties to protect it. Exclusions for information that is already publicly known, independently developed, or required by law to disclose. The duration of the obligation, how long after the engagement ends the confidentiality requirement lasts. Two to five years is common.

Clause 8: Termination

What it is: The conditions under which either party can end the contract before completion.

Why it matters: Engagements end early. Budgets get cut. Directions change. Client relationships break down. Without termination provisions, ending the relationship is legally ambiguous and practically disputed.

What happens without it: Can the client simply stop responding? Can you walk away mid-project if you are not being paid? Neither scenario has a clean answer without a termination clause. You are left negotiating the exit at the worst possible time, when the relationship is already strained.

What it should include: A notice period for termination, typically 14 to 30 days written notice. A statement that the client will pay for all work completed to the termination date. A kill fee provision: if the client terminates after a defined project stage, they owe a kill fee as a percentage of the remaining contract value, compensating you for the work you turned down to take this project. Obligations on both parties upon exit, such as return of materials and delivery of completed work to date.

Clause 9: Limitation of Liability

What it is: A cap on the amount either party can claim from the other in the event of losses.

Why it matters: Without a liability cap, a freelancer whose website contained an error could theoretically be held responsible for a client’s lost revenue. The potential exposure is unlimited and entirely disproportionate to the project fee.

What happens without it: You are exposed to claims that far exceed what you were paid. A client’s business loss, caused by any number of factors, could be attributed to your work without an upper limit on what they can seek.

What it should include: A cap on total liability, typically set at the total contract value or a defined multiple of it. An exclusion of consequential and indirect damages. A statement that neither party is liable for losses beyond what was reasonably foreseeable.

Limitation of liability clauses are standard in professional services contracts. Well-prepared clients will recognize them, and most will sign without dispute.

Clause 10: Governing Law and Dispute Resolution

What it is: A specification of which country or jurisdiction’s law governs the contract and how disputes will be resolved.

Why it matters: In international work, this determines which legal system applies if something goes wrong. That is a meaningful practical difference, affecting both where a dispute would be heard and which laws would apply.

What happens without it: In cross-border engagements, both parties may assume their own jurisdiction applies. If a dispute reaches a legal process, this ambiguity can delay and complicate everything.

What it should include: The governing law, typically your own country or jurisdiction, which is most practical for you if enforcement is ever needed. The dispute resolution path: negotiation first, then mediation, then arbitration or litigation. The jurisdiction for any court proceedings if litigation becomes necessary.

Additional Clauses Worth Considering

Force majeure covers events outside either party’s control, such as natural disasters, pandemics, or government-mandated shutdowns, that prevent either party from performing. For longer engagements, this clause protects both sides from penalties for delays caused by circumstances neither of you can affect. It has become increasingly standard since 2020.

Non-solicitation prevents the client from hiring your subcontractors or team members directly, bypassing you. Include this if you work with subcontractors whose client relationships you need to protect.

Exclusivity clauses occasionally appear when a client wants you to avoid working for their direct competitors during an engagement. If you agree to any exclusivity, protect yourself by ensuring the restriction is time-limited, narrowly defined, and compensated. Broad exclusivity clauses that limit your ability to work in your field entirely are worth pushing back on.

Profession-Specific Clause Considerations

The ten core clauses apply to every freelance contract. Certain professions require additional specificity in particular areas.

Developers should address source code ownership explicitly: who owns the codebase and repositories, not just the delivered functionality. If you are incorporating open source components or pre-existing libraries, state this clearly and identify the applicable license terms. Post-delivery support and maintenance should be scoped separately if offered, with its own rate and timeline, rather than left as an implied extension of the original engagement.

Designers should specify exactly which file formats will be delivered, distinguishing source files from export files, and whether the client receives both. Font and stock asset licensing deserves its own clause: who is responsible for licensing third-party assets incorporated into the deliverables. Brand usage guidelines, if relevant, should define how the design can and cannot be used.

Writers doing editorial work should address kill fees if a publication cancels an assignment before publication, and specify which rights are being licensed: first rights, reprint rights, digital rights. Fact-checking responsibility matters for published claims; clarify which party is accountable for accuracy.

Consultants should define the deliverable format precisely: whether the engagement produces a report, a presentation, a set of recommendations, or a combination. A clause clarifying that the consultant advises and the outcome depends on the client’s implementation protects you from liability for results you cannot control. Given the sensitivity of strategic information, the confidentiality clause deserves particular depth in consulting engagements.

What to Do When the Client Sends You a Contract

Most experienced freelancers eventually encounter this scenario: the client sends their own contract and expects you to sign it.

The same ten clauses apply in reverse. Review the scope clause for accuracy. Check that payment terms are complete, with a due date, a payment method, and late payment consequences. Look at the IP clause closely; broad assignment clauses that transfer all rights including preliminary work and pre-existing tools are not a fair arrangement and are negotiable. Check for any non-compete language. Look at the liability section for uncapped exposure.

Common unfavorable terms to watch for: unlimited IP transfer that includes work created before the engagement began. Non-compete clauses that are broader than the specific client relationship. Payment terms longer than net 30 without a compelling reason. Liability provisions with no cap, or indemnification clauses that shift all legal risk onto you regardless of fault.

Contracts sent by clients are starting positions. “This is our standard contract” is a negotiating stance, not an immovable fact. You can mark it up, propose changes, and negotiate. Experienced clients do this all the time; being asked to negotiate terms does not reduce your standing in their eyes. It often raises it.

Checklist: Does Your Contract Cover Everything?

Use this before signing or sending any freelance agreement.

• Parties fully identified: full legal names, business names, and registered addresses for both sides
• Scope defined with explicit inclusions and exclusions
• Payment terms complete: amount, schedule, due dates, method, and late payment consequences
• Revision policy in place: number of rounds included, definition of revision versus change request, and rate for additional revisions
• IP ownership explicitly stated and conditioned on receipt of full payment
• Independent contractor status confirmed
• Confidentiality obligations defined with a duration
• Termination provisions including kill fee
• Limitation of liability included
• Governing law and dispute resolution specified

From Contract to Payment

A contract establishes your right to be paid. Getting paid on time is a separate challenge that requires more than a signed document.

A strong contract sets the terms. Reliable payment infrastructure makes sure those terms translate into actual income. Ruul handles invoicing, client payment collection, and payout within one business day after a client pays, without requiring you to set up a company or navigate payment rails yourself. If you are working with clients in different countries or getting paid in multiple currencies, ruul.io/get-paid covers how global payouts work across 140+ currencies, and ruul.io/crypto-payout covers USDC withdrawal for those who prefer it. For record-keeping and tax documentation, ruul.io/stay-organized-tax-ready centralizes your transaction history so invoicing records are exportable when you need them.

The contract protects the agreement. The rest is about making sure what you agreed actually lands in your account.