contracts

A Freelancer Guide to Client Contracts That Get You Paid

Adira EditorialLegal AI desk5 min read

Why freelancers need a contract If you freelance, your contract is the single biggest thing standing between you and unpaid work. Most freelancer payment problems are not fraud; they are scope creep, vague payment terms, and no written record of what was agreed. A clear client contract fixes the scope, the price, the payment schedule and what happens when things change, so you get paid for what you actually do. A contract also makes you look professional, sets expectations, and gives you something to point to when a client pushes for "just one more revision" or pays 60 days late. You do not need a long legal document. You need the right clauses, clearly written. This article is general guidance, not legal advice. ## The clauses that actually get you paid These are the clauses worth fighting for, in rough order of how often they save freelancers: 1. Scope of work. Describe exactly what you will deliver, in what format, and how many rounds of revisions are included. The sentence that protects you most is: "Work beyond this scope is charged separately at [rate]." Scope creep is the number one cause of unpaid or underpaid work.

  1. Payment terms. State the fee, the currency, the schedule, and the due date. "Net 15 from invoice date" beats "on completion". Be specific.
  2. Deposit or advance. Ask for an upfront payment (for example 30 to 50 percent) before you start. A client who will not pay a deposit is the client most likely not to pay the balance.
  3. Milestone payments. For larger projects, bill in stages tied to deliverables, so you are never carrying the whole project unpaid.
  4. Late payment fee and interest. State a late fee or interest after the due date. It encourages prompt payment and compensates you if it is late.
  5. Intellectual property on payment. Make clear that IP and usage rights transfer to the client only on full payment. Until then, the work is yours. This single clause gives you real leverage.
  6. Kill fee / cancellation. If the client cancels, state what you are owed for work done and as a cancellation fee.
  7. Expenses. Say whether costs (stock assets, travel, tools) are billed on top.
  8. Termination. How either side can end the engagement, and what is owed on exit.
  9. Governing law and disputes. Which law applies and how disputes are handled. ## A short freelance contract block A lean starting point for a simple project. Adapt and have it reviewed for anything substantial. ``` FREELANCE SERVICES AGREEMENT Between: [FREELANCER], [address] and [CLIENT], [address] Date: [DATE] 1. SERVICES The Freelancer will provide: [describe deliverables, format, and number of revision rounds]. Work beyond this scope is charged at [rate]. 2. FEES AND PAYMENT Total fee: [AMOUNT] [currency]. Deposit of [X]% ([amount]) is payable before work begins. Balance payable [schedule / on milestones]. Invoices are due within [N] days. 3. LATE PAYMENT Amounts unpaid after the due date carry a late fee / interest of [rate]. 4. INTELLECTUAL PROPERTY All IP and usage rights in the deliverables transfer to the Client only upon receipt of full payment. Until then they remain with the Freelancer. The Freelancer may show the work in their portfolio unless agreed otherwise. 5. CANCELLATION If the Client cancels, the Freelancer is paid for all work done plus a cancellation fee of [amount / %]. 6. CONFIDENTIALITY Each party keeps the other's confidential information private. 7. INDEPENDENT CONTRACTOR The Freelancer is an independent contractor, responsible for their own taxes, and is not an employee of the Client. 8. GOVERNING LAW This Agreement is governed by the laws of [jurisdiction]; disputes go to [courts / arbitration / mediation first]. Signed, Freelancer: __________ Signed, Client: __________
- **No deposit.** Starting work with nothing upfront is the most common reason freelancers go unpaid.
- **Transferring IP before payment.** If the client owns the work before paying, you lose your main leverage.
- **Vague payment terms.** "On completion" invites endless delay. Use dated terms and milestones.
- **No late fee.** Without a cost to paying late, many clients will.
- **Working with no contract for "small" jobs.** Small jobs go wrong too, and are the hardest to chase without a written agreement. ## Getting paid: the practical and legal side A contract gets you most of the way; good habits do the rest. Invoice promptly and clearly, with your terms on the invoice. Send a polite reminder the day payment is due, then a firmer one after the deadline. If it is still unpaid, a formal demand letter referencing the contract and the amount often works. On the legal side, the rules vary by jurisdiction. In India, your agreement is a contract under the Indian Contract Act, 1872, and if a client pays by cheque that bounces, the cheque-bounce procedure under section 138 of the Negotiable Instruments Act, 1881 may apply. Many small freelancers and businesses can register as micro or small enterprises, which in some cases brings statutory protections on delayed payments; check the current rules and whether you qualify. Because payment-enforcement rules differ by jurisdiction, confirm the position where you and your client are based. Last verified October 2026. <!-- [VERIFY: MSME delayed-payment specifics vary and should be confirmed against current rules before reliance] --> ## Where a contract workspace helps As a freelancer you reuse the same contract again and again, tweaking scope, fees and dates for each client, and then you have to remember who owes what and when each payment is due. That juggling, across email, invoices and documents, is exactly where things slip and payments get missed. That is the idea behind a single AI contract workspace: drafting from your own template tuned to how you work, reviewing a client's contract for one-sided terms before you sign, editing clauses in plain language, and keeping the signed agreement and its key dates in one place. Tools such as [Adira](https://adiralaw.com) are built around that idea of drafting, understanding and tracking contracts in one workspace. The clauses above are what get you paid; a workspace just makes reusing and tracking them less of a chore.

Frequently asked questions

What should a freelance contract include to make sure I get paid?
A clear scope with revision limits, specific payment terms with due dates, an upfront deposit, milestone payments on larger jobs, a late-payment fee, and a clause transferring intellectual property to the client only on full payment. The IP-on-payment clause and the deposit are the two that give a freelancer the most leverage.
Should a freelancer always take a deposit?
In most cases, yes. Asking for an advance of around 30 to 50 percent before starting work filters out clients who may not pay and means you are never carrying the whole project unpaid. A client who refuses any deposit is often the one most likely to delay the final payment.
What can a freelancer do if a client does not pay?
Invoice clearly with your terms, send reminders on and after the due date, then a formal demand letter referencing the contract and the amount owed. If the client paid by a cheque that bounced, the section 138 procedure under the Negotiable Instruments Act may apply in India. Enforcement rules vary by jurisdiction, so check the position where you and the client are based.
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