contracts

The Key Clauses in a Freelance Contract, Explained

Adira EditorialLegal AI desk5 min read

What are the key clauses in a freelance contract? A freelance contract is the agreement between a client and an independent freelancer, such as a writer, designer, developer or consultant, who delivers a defined piece of work for a fee without becoming an employee. Its key clauses are the scope of work, fees and payment, independent-contractor status, intellectual property and ownership, revisions and approvals, a kill fee or cancellation term, confidentiality, warranties, limitation of liability, and termination. The purpose of the document is to make sure both sides agree on what is being delivered, what it costs, who owns it, and what happens if the work stops. Below, each clause is explained in plain English. This is an explanation of common clauses, not legal advice. Contractor status and IP rules vary by jurisdiction, so have a qualified lawyer review a high-value engagement. ## Scope of work The scope clause says exactly what the freelancer will deliver: the specific outputs, the format, and the milestones. This is where most freelance disputes are won or lost. A tight scope with an explicit out-of-scope line protects the freelancer from endless additions and protects the client from vague delivery. If the work has phases, list them and tie payment to each. ## Fees and payment This clause sets how much, on what basis, and when. The basis may be a fixed project fee, an hourly or daily rate, or a retainer. It should cover a deposit or upfront payment, invoicing points, the payment due date, late-payment interest, and how taxes such as GST or VAT are handled. For freelancers, an upfront deposit and clear due dates are the main protection against slow or non-payment. ## Independent-contractor status This clause confirms the freelancer is an independent contractor, not an employee, responsible for their own taxes and free to work for others. The label alone is not decisive. Tax and labour authorities look at how the relationship actually works, including control and exclusivity, and the classification test varies by jurisdiction. Keep the clause, but make sure the real arrangement matches it. ## Intellectual property and ownership This is the clause freelancers most often get wrong. By default, ownership of created work does not always pass to the client automatically, and in some places the creator keeps copyright unless it is assigned in writing. A clear IP clause states that ownership of the deliverables transfers to the client on full payment, and lets the freelancer keep pre-existing tools and templates. Freelancers should also consider keeping the right to show the work in a portfolio. ## Revisions and approvals A good freelance contract says how many rounds of revisions are included and what counts as a new, chargeable request. Without this, "just one more change" becomes unpaid work with no end. State the number of rounds, the approval process, and the rate for extra work beyond them. ## Kill fee and cancellation A kill fee is the amount the client pays if it cancels the project partway through. It protects the freelancer who has turned down other work and started the job. The clause should set the fee or the basis for it, such as payment for work done plus a percentage of the remaining fee, and say when it applies. ## Confidentiality Freelancers often see client information: plans, data, unreleased products. The confidentiality clause requires them to keep it secret, use it only for the job, and return or delete it on request, with normal exceptions for public information or disclosure required by law. In many engagements this duty is one-way, from freelancer to client, but it can be mutual. ## Warranties and liability The warranties clause is the freelancer's promise to perform with reasonable skill and care and to deliver work that does not knowingly infringe anyone else's rights. The limitation-of-liability clause caps how much the freelancer can be made to pay if something goes wrong, often at the fees paid, and excludes indirect loss. A fair cap matches the size of the project; an uncapped liability is a serious risk for an individual freelancer. ## Termination The termination clause says how either side can end the engagement, usually on notice, and immediately for a serious breach. It should say that the client pays for work done up to termination, and it works alongside any kill fee. Make the notice period workable for both sides. ## How a freelance contract differs from an employment contract A freelancer is not an employee, and the contract should keep that line clear. An employee gets a salary, benefits and statutory protections, and the employer directs how the work is done and owns most of what is created automatically. A freelancer sets their own methods, works for several clients, carries their own tax and insurance, and keeps ownership of their work unless they assign it. This difference is why the independent-contractor status clause and the IP assignment clause matter so much: without the first, a client may wrongly be treated as an employer with back-tax and benefit exposure; without the second, the client may not own what it paid for. If a client controls a freelancer like staff, with fixed hours and exclusivity, a tax or labour authority may reclassify the relationship, so the written terms and the real working pattern need to match. ## A note on jurisdiction How a freelancer is classified for tax and employment, whether copyright passes automatically or needs written assignment, and how far a liability cap holds all differ by country. This explainer is India-first but written to apply across the UK, Ireland, Singapore, Australia and the US, where the structure is similar but the detail varies by jurisdiction. This is not legal advice. ## Where a contract workspace helps Understanding these clauses lets a freelancer or a client read and negotiate a contract with confidence. The ongoing work is everything after: making sure each new project contract has a clear scope and IP assignment, tracking deposits and payment dates, and keeping versions straight as terms are negotiated by email. Drafting a freelance contract, reviewing its scope, IP assignment and liability, and tracking deposits and payment dates across many small jobs can live in one AI contract workspace tuned to how you take on work. Adira keeps them together in one workspace. The explainer above is enough to read a freelance contract on its own.

Frequently asked questions

Who owns the work a freelancer delivers?
Only if the contract says so. Ownership of created work does not always pass to the client automatically, and in some places the freelancer keeps copyright unless it is assigned in writing. A clear IP clause transfers ownership of the deliverables to the client on full payment, which is usually what both sides intend.
What is a kill fee in a freelance contract?
A kill fee is the amount a client pays if it cancels the project partway through. It protects a freelancer who turned down other work and already started. A fair clause sets the fee or its basis, such as payment for work done plus a share of the remaining fee, and states when it applies.
How many revisions should a freelance contract include?
State a specific number, such as two or three rounds, and define what counts as a new, chargeable request beyond them. Without a revisions clause, repeated changes become unpaid work with no clear end. Setting the rounds and the rate for extra work protects both sides.
Was this useful?

See how Adira drafts in your voice and reads contracts from your side.

Explore the showroom

Working through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.

Try Weave — free