Freelancer Contracts: The Essential Clauses That Protect Your Pay, Scope and IP

This is general information, not legal, tax, financial, medical or security advice. Rules and prices change, so confirm details with the official sources linked below or a qualified professional.

Every freelance contract should answer seven questions in writing: who the parties are, what you'll deliver (and won't), how "done" is accepted, how changes are handled, what you're paid and when, who owns the work, and how either side can exit. Clear clauses on scope, payment, IP-on-payment and termination prevent most disputes, and give you leverage when a client pays late.

This is general information, not legal/tax/financial advice. Contract law differs by country and state; have a lawyer review important agreements.

Key takeaways

• A written contract isn't optional for serious work. In New York it's legally required for covered freelance work of $800 or more.
• Scope + exclusions + change process prevent "just one more thing" creep.
• Payment terms should state the currency, due dates, method, who pays transfer fees, and late-payment consequences.
• IP should transfer on full payment, with your pre-existing tools licensed, not handed over.
• Termination, kill fee and liability cap clauses protect you when things go wrong.

The essential clauses

1. Parties

Use legal names, entity types and mailing addresses for you and the client. Name the actual paying entity, not just a brand name.

2. Scope of work and deliverables

Describe the deliverables in specific terms: features, pages, integrations, environments, documentation. Vague scope is the root of most freelance disputes.

3. Exclusions

List what's not included: content writing, third-party licence costs, ongoing maintenance, hosting, data migration, support after launch. Exclusions are as valuable as inclusions.

4. Timeline and dependencies

Give milestone dates, plus the client dependencies that affect them, such as access, content, feedback turnaround and approvals. Say that delays caused by missing dependencies shift the timeline.

5. Acceptance criteria and process

Define how each deliverable is reviewed, how long the client has to review it (for example, five business days), and what happens if they don't respond, such as deemed acceptance.

6. Change requests

Every change gets a written estimate (time and cost) and written approval before work starts. This one clause protects fixed-price projects more than any other.

7. Fees and payment terms

State:

• The fee model (hourly, fixed, retainer) and rates
• Deposit and milestone amounts
• Invoice timing and due dates
• Currency
• Accepted payment methods
• Who pays transfer and conversion charges

New York's law, for example, requires covered contracts to include the rate and method of compensation and the date payment is due (or how it will be determined). That's a good standard to follow anywhere.

8. Late payment

Specify what happens if an invoice is late: a reminder schedule, a late fee or interest (where lawful), and your right to pause work after a set number of days. See how to handle late-paying clients.

9. Intellectual property

A balanced approach:

• Deliverables become the client's property on full payment.
• Pre-existing materials (your libraries, templates, tools) stay yours, and the client gets a perpetual licence to use them as part of the deliverables.
• Third-party and open-source components are subject to their own licences, which you'll disclose.
• Portfolio rights: you may show the work publicly unless the client opts out in writing.

10. Confidentiality

Both sides protect each other's confidential information. Define what counts, how long the obligation lasts, and the usual exceptions (public information, information already known, legally required disclosure).

11. Data protection and security

If you'll touch personal data or production systems, state who is responsible for what: access controls, credentials, backups and breach notification. Clients in some markets will require their own data processing terms.

12. Warranties and liability

• A short warranty period for fixing defects in delivered work.
• A cap on liability, often limited to fees paid under the contract, with exclusions for indirect or consequential losses where the law allows.
• No guarantee of specific business results unless you've deliberately agreed to one.

13. Termination and kill fee

• Either party can end the contract with written notice (for example, 14 days).
• The client pays for all work done to the termination date, plus any kill fee agreed for early cancellation.
• Deliverables and IP for paid work transfer on payment.

14. Governing law and disputes

Name the governing law and the dispute process: negotiation first, then mediation or arbitration, then courts. For international work, choose something both sides can practically use.

What New York's law requires (a useful benchmark)

New York State's Freelance Isn't Free Act, in General Business Law Article 44-A (effective August 28, 2024):

• Applies to freelance workers (individuals, or organizations of one person) retained as independent contractors for $800 or more, alone or aggregated with the same hiring party over the previous 120 days. Lawyers, licensed medical professionals, construction contractors and certain sales representatives are excluded.
• Written contract must include: both parties' names and mailing addresses; an itemisation of services, their value, and the rate and method of compensation; the payment date or how it will be set; and the date by which you must submit a list of services to meet the client's payment processing deadlines.
• Record keeping: the hiring party must keep the contract for at least six years.
• Payment: by the contract date, or within 30 days after completing the work if no date is specified. Once work has started, the client can't make timely payment conditional on you accepting less money.
• Model contract: the NY Department of Labor publishes a free Freelance Worker Agreement.

Even if your clients aren't in New York, this checklist is a solid minimum standard.

How to put a contract in place (step by step)

1. Start from a template, such as the NY DOL model agreement or your own reviewed template.
2. Write the scope with the client, not for them. Agree deliverables and exclusions in a call, then document them.
3. Attach a statement of work for each project under a master agreement, if you work with a client repeatedly.
4. Send for e-signature and keep the signed PDF.
5. Match your invoices to the contract terms (invoicing best practices).
6. Use change orders for every scope change, even small ones.

Extra clauses for international clients

Cross-border work adds a few points worth writing down:

• Currency and exchange rate. Invoice in one currency, and say that the client pays the invoiced amount in that currency.
• Transfer charges. State that the client bears sending and intermediary bank charges, or that you'll invoice them separately.
• Tax forms and withholding. US clients may ask for IRS Form W-8BEN (individuals) or W-8BEN-E (entities). The IRS says to provide W-8BEN when the payer requests it. Say that the fee is due in full, and that each party handles its own taxes.
• Working hours and response times. Agree overlap hours and expected response times across time zones.
• Language of the contract. If you have translated versions, say which one governs.
• Independent contractor status. Confirm that you aren't an employee, that you control how and when you work, and that you can work for other clients.
• Sanctions and compliance. Large clients may require you to confirm you aren't on sanctions lists and will follow their supplier code.

Clause comparison: weak vs. strong

The percentages above are examples, not recommendations. Set your own.

From experience: On Shopify Plus and custom web projects, the clause I rely on most is the change-request process. It turns "can you also..." from a debate into a quote, and clients appreciate knowing the cost before deciding.

Revisit your template every year, after any dispute, and whenever you enter a new client market.

Checklist

• [ ] Legal names and addresses of both parties
• [ ] Deliverables, exclusions and dependencies listed
• [ ] Acceptance process and review window defined
• [ ] Change-request process in writing
• [ ] Fees, currency, due dates, payment method, transfer fees
• [ ] Late-payment terms and right to pause work
• [ ] IP transfers on full payment; pre-existing tools licensed
• [ ] Confidentiality and data-security responsibilities
• [ ] Liability cap and warranty period
• [ ] Termination notice and kill fee
• [ ] Governing law and dispute process
• [ ] Signed copy stored

Next steps

• Prepare for slow payers with how to handle late-paying clients.
• Set the numbers that go into the contract with how to price freelance development work.
• Make invoices mirror your contract with invoicing best practices.
• Need a second opinion on a technical scope before signing? See technical due diligence.

Sources

• New York State Department of Labor, Freelance Isn't Free Act: https://dol.ny.gov/freelance-isnt-free-act
• New York General Business Law §1410 (Definitions): https://www.nysenate.gov/legislation/laws/GBS/1410
• New York General Business Law §1411 (Contracted compensation payments): https://www.nysenate.gov/legislation/laws/GBS/1411
• New York General Business Law §1412 (Written contracts): https://www.nysenate.gov/legislation/laws/GBS/1412
• NY DOL Model Freelance Worker Agreement: https://dol.ny.gov/freelance-worker-agreement

Keep reading