Freelancer Contracts 101: What to Put in Writing Before You Start

Why a Handshake Deal Is a Financial Risk

Freelancing runs on trust, but trust is not a payment method. When there is no written agreement, a dispute over money or ownership comes down to one person’s word against another’s. If a client decides not to pay, or decides your work belongs to them now, you have no document to point to.

A contract does not need to be complicated to be effective. It needs to cover a short list of specific points, in writing, before any work begins. This article walks through what those points are and how to phrase them so they hold up.

The Core Elements Every Freelance Agreement Needs

Scope of work

Vague scope is the single biggest cause of freelance disputes. “Design a logo” invites endless revisions. “Design one primary logo concept, two rounds of revisions, delivered as vector files” gives both sides a finish line.

Write the scope as a list, not a paragraph. Include:

• What deliverables you are producing, in specific formats
• How many revision rounds are included
• What counts as “out of scope” and triggers additional fees
• The deadline, or a process for how deadlines can change

Payment terms

Payment terms fail when they are implied instead of stated. Your contract should spell out:

• The total fee or rate, and how it is calculated (flat, hourly, milestone-based)
• A deposit requirement before work starts, commonly 25 to 50 percent
• The invoice schedule (on completion, monthly, per milestone)
• The exact number of days the client has to pay after an invoice is sent
• What happens if payment is late

Late payment consequences

A payment term without a consequence is a suggestion. Add language that makes late payment cost the client something, such as:

• A late fee, stated as a flat amount or a percentage per month
• The right to pause work until the invoice is paid
• A statement that final files or deliverables are withheld until payment clears

That last point deserves its own explanation, because it is one of the most useful and most overlooked tools freelancers have.

Withholding Deliverables Until You’re Paid

Unless your contract says otherwise, you generally are not obligated to hand over final files, source documents, or completed work before payment is made. This is sometimes called a “kill fee” or “withholding” clause, and it should state plainly that ownership and final files transfer to the client only after full payment is received.

This single clause does more to prevent nonpayment than any amount of chasing invoices after the fact. It shifts the leverage back to you, because the client cannot use the work until they pay for it.

What to do when a client goes quiet

If an invoice goes unpaid past the due date, a simple sequence works better than escalating emotion:

1. Send a polite reminder on the due date itself, referencing the invoice number and original terms.
2. Send a second notice a week later that references the late fee specified in your contract.
3. Send a formal notice stating that work will pause, or that a collections process will begin, by a specific date.
4. If the amount is significant, consider small claims court, which in most places does not require a lawyer and has a filing cost far lower than the amount owed.

Who Owns the Work: Intellectual Property Basics

Many freelancers assume that once they hand over a finished file, the client automatically owns everything, or the opposite, that they automatically keep the rights. Neither assumption is safe. Ownership depends entirely on what the contract says.

Work for hire vs. licensing

There are two common structures:

• Work for hire: the client owns the finished work outright, as if they had made it themselves. This is common for logos, written copy, and commissioned designs.
• License: you retain ownership and grant the client permission to use the work in specific ways. This is common for stock-style assets, code libraries, or work you want to reuse or display in a portfolio.

If your contract is silent on this point, the default rules vary by jurisdiction and by the type of work, which means you cannot count on a favorable outcome. State it directly instead of leaving it to chance.

Portfolio rights

Even under a work-for-hire arrangement, you can negotiate the right to display the work in your portfolio or reference it as past experience. Add a short clause granting you this right, since many standard contracts leave it out by default.

Pre-existing materials

If you are using your own tools, templates, code snippets, or frameworks that you built before this project and plan to reuse on future projects, say so in writing. Otherwise a broad ownership clause could be read to include those pre-existing materials, which limits what you can use on your next job.

Other Clauses Worth Including

Kill fee for cancelled projects

If a client cancels partway through, a kill fee clause guarantees you get paid for work already completed, typically calculated as a percentage of the total fee based on how much progress had been made.

Limitation of liability

This clause caps how much you could owe a client if something goes wrong, usually limited to the amount they paid you. Without it, you could theoretically be exposed to open-ended damages far beyond your fee.

Termination terms

State how either party can end the agreement early, how much notice is required, and what happens to payment for work already done.

Governing law

Name the state or jurisdiction whose laws apply and where any dispute would be filed. This matters more than it seems, especially when working with clients in other states or countries.

Putting It Into Practice

You do not need a different contract for every client. Build one solid template that covers scope, payment, late fees, withholding rights, IP ownership, portfolio rights, kill fee, liability limits, and governing law. Then adjust the specific numbers and deliverables for each new project.

Send the contract before any work starts, not after the first invoice goes unpaid. A signature at the outset, even a simple e-signature on a PDF, is worth far more than a strongly worded email after the fact.

The goal is not to prepare for every client to become a problem. It is to make sure that if one does, you already have the paperwork that settles the question quickly, in your favor, without a drawn-out fight.

For the complete, structured playbook on this topic, see The Freelancer Legal Kit: Agreements, IP Protection, and Getting Paid in our library. New here? Start with our free guide.