Many freelancers in the United States start work on the strength of an email and a handshake. It feels faster, friendlier, and less formal than sending a contract, especially with a new client you want to impress. Then a project changes shape halfway through, a payment arrives weeks late, or a client claims rights to work you never agreed to hand over, and the friendly email turns out to say nothing useful about any of it. A written contract does not make you difficult to work with. It makes you professional, and it protects both sides by writing down what was agreed before money and feelings get involved.
This guide covers what a freelance contract should include, in plain language, for US-based freelancers in any field: writers, designers, developers, consultants, photographers, and more. It is general information, not legal advice, and for high-value or unusual projects, a short review by a local attorney is money well spent. But for most everyday freelance work, a clear, complete contract you actually use beats a perfect contract you never send.
Why a Contract Matters Even With Good Clients
A contract is not a weapon for a dispute. It is a shared record of an agreement, and its main job is preventing disputes in the first place. When the scope, price, timeline, and payment terms are written down, both sides can check the document instead of relying on memory. Memory is unreliable, especially months later, and especially when a project has changed direction several times. A contract turns I thought you meant into let us check what we agreed.
Contracts also matter for taxes and business records. A written agreement, together with invoices and payment records, shows that you operated as an independent business, which is useful if your working arrangement is ever questioned. It also makes your own bookkeeping easier: each signed contract maps to an invoice, and each invoice maps to a payment, so nothing falls through the cracks at year end.
Finally, a contract signals professionalism. Clients who hire freelancers regularly expect one, and many larger clients require one before they can pay you at all. Sending a clear contract promptly, and being willing to discuss its terms, tells a client you take your work seriously. Freelancers who skip contracts are often the ones who spend the most time chasing late payments later.
Identify the Parties and the Project
Start with the basics, and get them exactly right. The contract should name both parties with their full legal names, not just first names or business nicknames, and include contact details and addresses. If you operate under a business name, use it consistently across your contract, invoices, and tax records. If the client is a company, name the company and the person authorized to approve the work, because the person you talk to every day may not be the person who can approve payment.
Next, describe the project in concrete terms. What exactly will you deliver? A website, a set of articles, a logo package, a month of consulting calls? List the deliverables, the format they will arrive in, and how many there are. Vague descriptions like marketing help or design work invite disagreement, because each side fills in the blanks differently. A deliverable list that both sides can point to is the foundation of everything else in the contract.
Include the timeline: when work starts, when drafts or milestones are due, and when the final delivery is expected. If the timeline depends on the client, say so. A common clause states that deadlines shift by the same number of days the client takes to provide feedback or materials. Without that, a client who takes three weeks to review a draft can still hold you to the original delivery date.
Define the Scope and Handle Changes
Scope creep is the most common source of freelance frustration: a project that starts as five pages becomes eight, a logo becomes a logo plus social templates plus a brochure, or a fixed-price website gains new features every week. A scope section prevents this by stating what is included, and, just as importantly, what is not. If you are writing website copy, say whether that includes product descriptions, blog posts, or only the main pages. If you are designing a logo, say how many concepts and revision rounds are included.
Then add a change process. State that additional work beyond the agreed scope will be quoted separately and requires written approval before you begin it. This single clause changes the dynamic of scope creep entirely. Instead of an awkward conversation about whether extra work is free, there is a simple process: the client asks, you quote, the client approves in writing, and then you proceed. Clients who genuinely want the extra work will approve it. Clients who were hoping it was included will decide it is not a priority after all.
Revision rounds deserve their own line. State how many rounds of revisions are included, what counts as a revision versus a new direction, and what happens after the included rounds are used. A project that allows unlimited revisions never ends, and it punishes the freelancer for the client’s indecision. A clear limit, with additional rounds billed at an agreed rate, keeps projects moving and keeps both sides honest about feedback.
Set Payment Terms That Protect You
Payment terms are where most freelance contracts earn their keep. State the total fee, or the rate and how it is calculated, and state when payment is due. Common structures include full payment on delivery, a deposit before work begins with the balance on delivery, or milestone payments for longer projects. For new clients, a deposit is standard practice, not rudeness: it confirms the client is serious and covers your early work if the project stalls.
State the payment method, the currency, and the due date in days from invoice, not from a vague point like completion. Net 30 means payment is due thirty days after the invoice date, and writing that out avoids arguments about when the clock started. Add a late fee clause if you want one, stated as a specific rate or amount, and state who pays any transfer or payment processing fees. If you work with clients who pay by check, note that work or delivery may pause until a payment clears.
Include a kill fee: what happens if the client cancels the project partway through. A typical arrangement is payment for all work completed to date, plus a percentage of the remaining fee, because cancelled work cannot always be replaced immediately. Without a kill fee, a cancelled project can leave you with weeks of work and nothing to show for it. Clients understand kill fees when they are explained as fairness, not punishment: you reserved time that could have gone to another client.
Keep payment records carefully. Every contract should map to numbered invoices, and every invoice to a payment. If a client pays you for services in the course of their business and the total reaches the reporting threshold, they may need to report it: businesses that pay $600 or more to a contractor in a calendar year generally must file Form 1099-NEC for that contractor. You can read a clear explanation of the rule here: Form 1099-NEC Guide. Your own tax records should include every invoice and payment regardless of whether you receive a form.
Cover Ownership and Usage Rights
Ownership is the clause freelancers most often regret skipping. In general, a freelancer owns the work they create until rights are transferred in writing, but clients often assume they own everything the moment they pay. Your contract should state exactly what the client receives: full ownership of the final deliverables on full payment, or a license to use them for specific purposes, and what you keep. For example, a designer might transfer ownership of the final logo while keeping the right to display it in a portfolio, and a writer might license articles for a website while retaining the right to republish them elsewhere after a set period.
State when ownership transfers. A common and sensible rule is that rights transfer when payment is received in full. This gives you leverage if payment is late, and it gives the client certainty once they have paid. Also state what the client may not do: resell your work as their own, alter it in ways that misrepresent it, or use it beyond the agreed scope without a new agreement. If the client wants broader rights, that is a negotiation about price, not a detail to concede silently.
Do not forget your own materials. Drafts, unused concepts, working files, and tools you built for your own use are not automatically part of the delivery. If the client wants source files, say whether that is included and at what price. Source files are valuable: they let the client make future changes without you, and charging for them, or keeping them as your own, is entirely reasonable.
Clarify That You Are an Independent Contractor
Your contract should state that you are an independent contractor, not an employee of the client. This matters for taxes, benefits, and liability. As an independent contractor, you are responsible for your own taxes, including self-employment tax, and you do not receive employee benefits from the client. The client does not withhold tax from your payments, and you manage your own schedule, tools, and methods of work.
Note, however, that a contract label alone does not decide the question. The IRS looks at the actual working relationship, weighing behavioral control over how the work is done, financial control over the economics of the arrangement, and the type of relationship the parties have. A worker who must follow the client’s hours, use the client’s equipment, and work only for that client may be treated as an employee even if the contract says contractor. You can read how the IRS weighs these factors here: IRS Common Law Employee Test. If your arrangement looks like employment in practice, talk to a professional rather than relying on a label.
Include a short section on liability and confidentiality. A limitation of liability clause caps what either side can claim if something goes wrong, usually at the amount paid for the project. A confidentiality clause covers non-public information you learn about the client’s business. Both are standard, and both protect you as much as the client. Avoid signing a contract that makes you liable for unlimited damages, or that claims ownership of work you create for other clients.
Taxes and Records for Freelancers
Freelance income is generally taxable, and because no tax is withheld from your payments, you are responsible for paying it yourself. If you expect to owe a certain amount in tax for the year after withholding and credits, the IRS generally expects quarterly estimated payments, which fall due in April, June, September, and January. The Taxpayer Advocate Service explains the current rules and due dates here: Making Estimated Tax Payments. Setting aside a portion of each payment when it arrives, rather than spending it all, is the habit that keeps tax season calm.
Keep your records in one place: signed contracts, invoices, payment confirmations, expense receipts, and any forms you receive. A simple folder per client, or a basic bookkeeping tool, is enough for most freelancers. Good records do three things: they make tax filing easier, they prove what was agreed if a payment dispute arises, and they show a pattern of independent business operation if your status is ever questioned.
Consider whether you need business insurance. Professional liability insurance, sometimes called errors and omissions insurance, covers claims that your work caused a client a loss. It is not required for every freelancer, but clients in some fields ask for it, and it is worth pricing once your income becomes regular. An insurance agent who works with small businesses can explain what a basic policy covers and what it costs for your field.
Use a Simple Process for Every Project
The best contract is one you actually send, every time. Build a template with the sections in this guide, and fill in the project-specific details for each client. Send it before work begins, and do not start until it is signed, or at least until the client has confirmed the key terms in writing and paid any deposit. Starting work on an unsigned contract because a deadline is tight is how freelancers end up working for free.
Be willing to discuss terms. A client who asks to change a clause is not necessarily being difficult; they may have their own standard terms, a legal department, or a genuine concern. Read their changes carefully, keep what is fair, and push back on what is not, such as unlimited liability, ownership of your unrelated work, or payment terms that stretch for months. Negotiation is normal, and a client who respects a freelancer who negotiates clearly is a client worth keeping.
Review your template once a year. As your rates, services, and experience grow, your contract should grow with them. A template written when you charged half your current rate may still contain a kill fee, a revision limit, or a liability cap that no longer fits the work you do. A yearly review takes an hour and keeps your most important business document current.
Frequently Asked Questions
Do I need a contract for a small project?
Yes. Small projects cause a surprising share of disputes, because small scope is where assumptions differ most. A short contract, even a page or two covering scope, price, payment terms, and ownership, is enough for most small jobs, and it takes far less time than resolving a disagreement later.
Can I use a contract template I found online?
A template is a good starting point, but read every clause and adapt it to your work, your state, and your clients. Templates written for another country or another field may contain terms that do not apply to you, or miss terms you need. For high-value projects, have a local attorney review your template once, then reuse it with confidence.
What if a client refuses to sign a contract?
That is useful information. A client who will not put an agreement in writing is telling you how they handle commitments. You can offer a simpler version, or a written confirmation of key terms by email, but be cautious about starting work with no written agreement at all, especially on a fixed-price project.
Does a contract make me an employee or a contractor?
The contract states the intended relationship, but the IRS looks at how the work actually happens: who controls the methods and schedule, who bears the financial risk, and what the overall relationship looks like. A contract that says independent contractor, combined with genuinely independent working practices, supports contractor status. A label alone does not decide it.