Freelance Contract Template: What to Include (Free Outline)

A freelance contract needs ten things: the parties, the scope, the timeline, the payment terms, the revision limit, who owns the work, confidentiality, how either side can end it, a cap on your liability, and two signatures. Everything else is optional. A handshake deal works great — until it doesn't, and the document that decides who is right is the one you wrote before the work started. Here is what goes in each section, the language you can copy, and the clauses to strike out when a client sends you their contract instead.

Why You Need a Freelance Contract

A contract isn't about distrust. It's about clarity. Without one, you're relying on memory and assumptions about scope, payment, timelines, and ownership. When something goes wrong (and eventually it will), a contract is the document that protects both sides.

Common scenarios a contract prevents:

• "I thought the price included unlimited revisions"
• "We assumed you'd also handle the social media graphics"
• "We'll pay you when our client pays us"
• "We own everything you created, including your original concepts"

There is a second reason that has nothing to do with disputes. A written agreement that shows you control how the work gets done, supply your own tools, and serve multiple clients is part of what establishes you as an independent contractor rather than an employee — a distinction covered in detail in our guide to freelancer vs independent contractor status. The contract is evidence, not just insurance.

The 10 Essential Sections of a Freelance Contract

1. Parties Involved

List the full legal names and contact information for both you and the client. If you're working with a company, include the company name and the primary point of contact. Name the entity that is paying you, not just the person who hired you — "Acme Marketing LLC" and "Dana Wu, Marketing Director" are two different things, and only the first one can be pursued for an unpaid invoice.

2. Scope of Work

This is the most important section. Be specific about what you will deliver. List each deliverable explicitly. Vague scopes like "design a website" invite scope creep. Instead write:

• Design homepage layout (desktop and mobile)
• Design 3 interior page templates
• 2 rounds of revisions per page
• Final delivery as Figma files and exported assets

Add an explicit not included list underneath. It feels blunt and it is the single highest-value paragraph in the document: "Not included: copywriting, photography, CMS development, ongoing maintenance." Everything you leave unmentioned is something a client can reasonably believe they bought. If you price fixed-fee work, the mechanics of holding a scope line are covered in our hourly vs project rate guide.

3. Timeline and Milestones

Define when work starts, key milestones, and the final deadline. Include dependencies — for example, "design phase begins within 5 business days of receiving brand guidelines from client."

Deadlines that depend on the client need to say what happens when the client is late. Without that, every day they sit on feedback comes out of your schedule while your delivery date stays fixed. A clause as short as "each business day of delay in client feedback extends all subsequent dates by one business day" converts their delay into a schedule change instead of your overtime.

4. Payment Terms

Be crystal clear about:

• Total project fee or hourly rate
• Payment schedule: 50% upfront + 50% on completion, or milestone-based payments
• Due dates: Net 15 or Net 30 from invoice date
• Accepted payment methods: Bank transfer, credit card, etc.
• Late payment penalties: e.g., 1.5% per month on overdue balances

Two details decide whether this section actually works. The first is what the due date is measured from: "Net 30" alone is ambiguous, and "Net 30 from receipt" or "Net 30 from approval" can add weeks. Our guide to Net 30 and other payment terms covers how EOM and MFI variants can nearly double the real wait. The second is that a late fee only exists if it was agreed before the work started — a penalty introduced in a reminder email after the due date is a negotiating position, not a debt. See how much late fee to charge for the standard rates and the state caps that limit them.

If you take a deposit, say what it is credited against, because "deposit" and "retainer" are routinely confused and the difference decides whether the money is refundable. Deposit structures are covered in when to send an invoice.

5. Revisions and Change Requests

Specify how many revision rounds are included. After that, additional changes are billed at your hourly rate. For significant scope changes, require a written change order with a revised quote.

Define what one round is, or the count means nothing: a round is one consolidated set of feedback from the client, delivered at once. Three people sending three separate emails over a week is three rounds unless you say otherwise.

6. Intellectual Property and Ownership

Spell out who owns the work product. The standard approach: you retain ownership until final payment is received, then full rights transfer to the client. Some freelancers retain the right to display work in their portfolio.

Ownership-on-payment is the clause that gives an unpaid invoice actual leverage — it is what lets you hold source files, exports, and production access without breaching the agreement. Carve out the things you reuse on every job: your own tools, libraries, templates, and methods should stay yours, licensed to the client for use in the deliverable rather than transferred outright.

7. Confidentiality

If you'll access sensitive business information, include a basic NDA clause. Keep it reasonable — you shouldn't be bound by confidentiality forever, and it shouldn't prevent you from doing similar work for other clients. Two limits make it fair: a term (two to three years is normal) and the standard exclusions for information that is already public or that you knew before the engagement.

8. Termination Clause

Define how either party can end the contract and what happens when they do:

• How much notice is required (typically 14-30 days)
• Client pays for all work completed up to the termination date
• Any kill fee for early termination (typically 25-50% of remaining project value)

Work through the arithmetic once so the clause is not abstract. On a $6,000 project cancelled at the halfway mark with $3,000 already invoiced and a 30% kill fee, the client owes $3,000 for completed work plus 30% of the remaining $3,000 — $900 — for a total of $3,900. The kill fee exists because you turned down other work to hold the schedule, which is the same logic that makes a capacity retainer's notice period payable in full.

9. Liability and Indemnification

Limit your liability to the total project fee. You shouldn't be on the hook for indirect damages, lost revenue, or problems caused by the client's misuse of your deliverables.

Note what this cap does and does not do. It limits what the client can recover from you under this contract. It is not a shield against a third party, and it is not a substitute for professional liability (errors and omissions) insurance — and neither is forming an LLC, for the reasons set out in our sole proprietor vs LLC comparison.

10. Signatures and Date

Both parties sign and date the contract. Electronic signatures are legally binding in most jurisdictions. Use tools like DocuSign or even a simple email confirmation referencing the attached contract.

Who Is Actually Signing — the Detail That Undoes an LLC

If you have formed an LLC, the signature block is where the entity either becomes the contracting party or doesn't. Signing your own name on the line makes you the party to the agreement, and a client suing on that contract sues you personally — the entity you paid to form never entered the deal. This is one of the three common ways the liability shield leaks, alongside personal guarantees and mixing business and personal money.

The fix costs nothing. Name the entity, then sign as its representative:

The same applies everywhere else your name appears: the "Parties" section should name the LLC, your invoices should bill under the LLC name, and your W-9 should carry the LLC's EIN. A contract in your personal name paired with an invoice from the company is the mismatch that makes the whole arrangement look decorative.

If the Contract Is a Retainer, Name the Model in One Sentence

"Retainer" describes two completely different deals, and nearly every retainer dispute is one side thinking they bought the first while the other sold the second.

• A capacity retainer buys reserved availability. The client pays for you to hold time open and turn away conflicting work, so unused hours expire by default and the notice period is invoiced in full.
• A prepaid retainer funds a balance you draw against at an agreed rate. You have not earned that money on the day it arrives, so unused balance stays the client's, carries forward, and is generally refundable on termination.

The contract has to say which one it is, in plain words, before it says anything about rollover or overages — those rules only make sense once the model is named. Our retainer invoicing guide works through both models with rollover policies, overage rates, and proration arithmetic.

Copy-Paste Clauses for the Three Sections That Cause Disputes

Adapt the bracketed values and drop these straight into your agreement.

Payment and late fees

Ownership on payment

Termination

These are practical starting points written for ordinary freelance projects, not legal advice. Anything unusual — high contract value, regulated work, cross-border clients, or a client's own paperwork you don't understand — is worth an hour of a lawyer's time.

Freelance Contract Red Flags

Watch out for these when a client sends their contract:

• "Work for hire" language — means you have zero rights to anything you create, including reuse of your own methods and tools
• Non-compete clauses — a client shouldn't restrict you from working with others in your industry
• Unlimited revisions — always cap revision rounds
• Payment on "acceptance" without defining what acceptance means — this creates an indefinite approval loop
• No termination clause — you need an exit strategy
• "Pay when paid" — makes your payment conditional on the client's own client paying them, which puts you on a timeline nobody in the contract controls
• Uncapped indemnification — an obligation to cover the client's legal costs with no ceiling can exceed the project fee many times over

Most of these are negotiable, and asking is normal rather than difficult. Three replacements do most of the work:

• Acceptance: "Deliverables are deemed accepted if Client does not provide written objection within 7 business days of delivery." That single sentence closes the indefinite approval loop.
• Pay when paid: "Payment is due within 30 days of invoice regardless of Client's arrangements with third parties."
• Indemnity: add "Contractor's total liability under this agreement shall not exceed the total fees paid" and limit any indemnity to claims arising from your own negligence.

Free Contract Template Outline

Here's a simple structure you can adapt for most freelance projects:

1. Parties: [Your Name/Business] and [Client Name/Business]
2. Project: [Brief description]
3. Deliverables: [Specific list] — and what is not included
4. Timeline: [Start date] to [End date], with client-delay adjustment
5. Fee: $[Amount] — [Payment schedule], due [Net 15] from invoice date
6. Late fee: [1.5]% per month on overdue balances
7. Revisions: [Number] rounds included; additional at $[Rate]/hour
8. Ownership: Transfers to client upon final payment; pre-existing materials licensed, not transferred
9. Confidentiality: [2] years, standard exclusions
10. Liability: capped at total fees paid
11. Termination: [Notice period] with payment for completed work plus [30]% of remaining value
12. Signatures: [Both parties sign and date — entity name first if you have one]

The Full Freelance Contract Template, Written Out

An outline tells you what goes where. It is not a document you can send. Below is the same agreement written out in full, in the same order, with every value you need to supply marked in brackets. Copy it into a document, replace each bracket, delete any clause that does not apply to the job, and read it once from the client's side before you send it.

It carries three sections the ten above do not: acceptance, independent-contractor status, and a governing-law line. Each is one sentence, and each closes an argument that otherwise has nowhere to go.

The five brackets people leave in

A half-filled template is the version that causes the dispute it was supposed to prevent. These five are the ones that go missing:

• [state] in Section 11. With no governing law named, a disagreement with an out-of-state client begins with an argument about where it gets heard, before anyone discusses the money.
• The "Not included" line in Section 1. Left blank, it reads as though nothing is excluded — which is worse than having no such line at all.
• $[rate] in Section 4. A revision limit with no hourly rate behind it has no consequence, so the limit is decorative.
• The dates in Section 2. "TBD" start dates make the client-delay extension unmeasurable, because there is no original date to extend from.
• The entity names in the preamble and Section 12. They have to match each other, the name on your invoices, and the name on your W-9.

What to send with it

Three things travel together on the day the contract is signed. The signed copy goes to both parties, not just to the client's inbox. If the client is a US business, they will need a completed Form W-9 from you before they can pay you and before they can issue a 1099 at year end — and the name on it should be the same party you named in Section 12, not your personal name under an entity's contract. Then the deposit invoice, the same day, carrying the same due date and the same late fee that Section 3 just agreed to; our guide to when to send an invoice covers how to structure the deposit itself.

One caution about Section 8: it states the relationship, it does not decide it. Classification turns on how the work actually runs — who controls the methods, who supplies the tools, whether you serve other clients — and a label in a contract does not override the facts. The IRS's self-employed individuals tax center is the place to start if a client's arrangement begins to look more like employment than a project.

As with the clauses above, this is a practical starting point for ordinary freelance projects in the United States, not legal advice, and state law varies. High contract value, regulated work, cross-border clients, or a client's own paperwork you don't fully understand are all worth an hour of a lawyer's time before you sign.

From Contract to Invoice

A contract only helps you get paid if the invoice matches it. When the agreement says Net 15 with a 1.5% monthly late fee, the invoice should carry that same due date and that same fee — not different numbers, and not silence. The fastest way to lose the benefit of a payment clause is to negotiate it carefully and then send an invoice that never mentions it.

In InvoiceBloom you set the due date and the late fee amount directly on the invoice, break the fee out into line items that mirror your deliverables, and put your payment methods, your agreed payment terms, and any deposit arithmetic into the payment instructions field so accounts payable can reconcile the invoice against the contract without emailing you. Keeping an eye on the due dates is still yours to do — an invoice moves to the overdue tab when you put it there, not when the date passes — and noticing one has slipped is usually the first sign that a payment clause is about to matter. What happens next is covered in our guide to handling late-paying clients.

The Bottom Line

A good contract takes 30 minutes to write and can save you thousands of dollars and months of headaches. Keep it clear, fair, and specific: name the parties precisely, list what you are not doing as well as what you are, tie ownership to final payment, cap your liability, and sign as your business if you have one. Then send an invoice that says exactly what the contract says.

Frequently Asked Questions

Is a contract sent by email legally binding without a signature?

In most jurisdictions, yes — electronic signatures and clear email agreement are generally enforceable for ordinary freelance work, and a reply saying "approved, please proceed" attached to a specific document is far better than nothing. What matters is that both sides can be shown to have agreed to the same terms, which is why the email needs to reference the actual attachment or quote the terms in full rather than saying "sounds good" under a long thread. A proper e-signature tool is worth using because it timestamps the agreement and gives both parties an identical copy, removing the argument about which version was agreed. Keep the signed copy somewhere you can find it two years later, not only in your sent folder.

Do I need a contract for a small project?

Yes, but it can be short. For a $500 job, a one-page agreement or even a detailed email covering the deliverables, the price, the due date, the revision limit, and who owns the work at the end does the job — the goal is a written record of what both sides agreed, not a document that looks impressive. The projects that generate disputes are frequently the small ones, because they are the ones people skip the paperwork on and start from memory. A useful rule: if you would be annoyed to lose the money, write it down.

What if the client refuses to sign a contract?

Treat it as information rather than an obstacle. Most refusals are really objections to length or legal tone, and offering a one-page version usually resolves it — ask which parts they object to, because a client who will not put the price and the deliverables in writing is telling you what the invoice conversation is going to look like. If they still refuse, protect yourself another way: take a larger deposit upfront, work in smaller paid stages so your exposure is capped at one stage, and confirm every agreement in an email that restates the terms. A client who will not sign but will pay half upfront is a manageable risk; one who will do neither is not.

Who owns the work if the contract doesn't say?

It is genuinely unclear, which is the problem. In the United States, work created by an independent contractor generally belongs to the contractor by default unless there is a written agreement transferring it or it falls into one of the narrow statutory "work made for hire" categories — but clients routinely assume that paying for something means owning it outright, and the assumption is common enough to survive well into a dispute. Silence therefore produces the worst outcome: two parties who both believe they own the same asset, and no document to settle it. Write the ownership term down even when it feels obvious, and tie the transfer to final payment so the clause protects your invoice as well as your rights.

Should I sign a contract in my own name or my business's name?

If you have formed an LLC or corporation, sign in the entity's name and identify yourself as its representative — name the entity on the signature line, then "By:", your name, and your title. Signing in your own name makes you personally the party to the agreement, which means the entity you formed is not the one on the hook, and it is one of the most common reasons a liability shield turns out to be worth less than expected. Sole proprietors sign in their own name, optionally adding a registered DBA. Keep it consistent across the contract, the invoice, and your W-9, because a mismatch between the name on the agreement and the name being paid causes both legal ambiguity and year-end tax paperwork that does not reconcile.

Can I use the contract template above as-is?

For an ordinary freelance project with a US client, yes — that is what it is for — but only once every bracket is filled and any clause that does not fit the job is deleted. The version that causes trouble is the one sent with placeholders still in it, or with a section left in that describes work nobody is doing. Read it once from the client's side before sending, because a clause that would make you hesitate to sign will make them hesitate too, and that negotiation is far cheaper before signature than after. It is a practical starting point rather than legal advice, and anything unusual — a large contract value, regulated work, a client outside the United States — is worth a lawyer's hour, because state law varies and the review costs little next to the contract it protects.

Do I need a separate statement of work for each project?

For a single project, one agreement covering everything is simpler and easier for a client to sign. For repeat work with the same client, split it in two: a master agreement carrying the terms you negotiate once — payment, ownership, confidentiality, liability, termination — and a short statement of work per project naming the deliverables, the dates and the fee, stating that it is governed by the master agreement. The advantage is that the second project takes a one-page document instead of a fresh negotiation, and the terms you already won do not get reopened every time. Number and date each statement of work and reference the master agreement by its date in the first line, so a year later it is obvious which terms applied to which job.