Contracts essentials: protecting both sides

0:00 Contracts essentials

Here's a story that repeats itself thousands of times a year. A freelancer delivers a logo. The client says it isn't quite what they wanted, refuses to pay the final invoice, and starts using the logo anyway. Who owns it? Who's right? Without a contract, it's one person's memory against another's. In this lecture, you'll learn the clauses that prevent most freelance disputes: scope, acceptance, payment, late payment, intellectual property, AI use, termination and governing law. This is general information, not legal advice, so have a lawyer check your template once, then reuse it.

0:41 Why it matters

Why does this matter? Because most freelance disputes, late payment, endless revisions, arguments about ownership, aren't really about bad people. They're about unclear expectations. A contract turns assumptions into a shared, written understanding before anyone's emotional or out of pocket. It's not a sign of distrust. Good clients expect it, and serious clients insist on it. Here's the key idea. A contract doesn't make a relationship formal. It makes it safe.

1:12 The rulebook analogy

Here's an analogy. Think of the rules of a football match. Players don't read them before every game, but they're there, and everyone knows the referee will apply them. What counts as a goal. How long the match lasts. What happens after a foul. Your contract is the rulebook for your project. What counts as done. How many revisions. When payment is due and what happens if it's late. Who owns what, and when. You rarely need to quote it. But its existence changes how everyone behaves.

1:50 Key clauses

Now the key clauses. Parties, with full legal names. Scope, referring to the proposal or statement of work, with exclusions and a change order process. Timeline and client dependencies. Acceptance: how deliverables are approved, and deemed acceptance after a set number of days. Revisions, defined. Fees, currency, deposit and milestones. Who pays transfer fees. Late payment terms. Intellectual property. AI use. Portfolio rights. Confidentiality and data protection. Warranties and a limit on liability, often capped at the fees paid. Termination and a kill fee. Contractor status. And governing law and dispute resolution. The full checklist is in the lesson.

2:33 Payment protection

Let's focus on payment protection. Take a deposit before work starts, commonly thirty to fifty percent for projects. Use milestone payments for longer work. Bill retainers in advance. Transfer final files and rights only on full payment. Include a right to pause work if invoices are overdue. And late payment terms, where lawful. In the UK, for example, businesses can claim statutory interest on late business-to-business payments at eight percent above the Bank of England base rate, plus fixed compensation of forty, seventy or a hundred pounds per invoice depending on its size. Other countries have different rules, so check locally or ask a lawyer.

3:19 IP and AI use

Now intellectual property, the most misunderstood clause. In many countries, the creator owns the copyright unless it's assigned in writing. Clients often assume they own everything automatically. A common, fair approach: copyright in the final deliverables transfers to the client on full payment. You keep your pre-existing materials, tools, templates and know-how, and license them for use in the deliverables. Third-party assets, like fonts, stock images, music and code libraries, are licensed on their own terms. And now AI use. State what's allowed, keep client confidential data out of tools that train on inputs, commit to human review, and give IP warranties you can honestly support.

4:05 Worked example 1: Grace in Brighton (illustrative)

A simple worked example, illustrative. Remember our logo dispute. This time the freelancer, Grace in Brighton, has a contract. It states two revision rounds, approval at each stage by email, and IP transfer on full payment. The client says, it isn't what we wanted, after approving each stage. Grace calmly replies, referencing the approvals and the contract. She offers an additional revision round as a paid change order, and notes that rights transfer on payment, so the logo can't be used until then. The client pays the invoice, and orders the extra round separately. No shouting, no lawyers. Just the rulebook.

4:49 International contracts

Now international contracts, which many of you will sign. Specify the currency, and who pays transfer and receiving fees. Specify governing law and how disputes are resolved: your jurisdiction, the client's, or neutral mediation or arbitration. For bilingual contracts, say which language prevails. And be realistic about enforcement. Chasing a small debt across borders through courts is rarely worth it. That's why, internationally, the practical protections matter most: deposits, milestones, retainers in advance, pausing work and rights on payment. For large contracts, get advice from a lawyer in the relevant jurisdiction.

5:29 Worked example 2: Omar and a Saudi client (illustrative)

Now the realistic scenario, illustrative. Omar, a developer in Karachi, lands a large project for a Saudi logistics company. The client sends their own contract, in Arabic and English. Omar uses the clause checklist. He finds three problems: unlimited liability, IP transferring on signature rather than payment, and payment within ninety days of final acceptance. He negotiates politely: liability capped at fees paid, IP on payment, and a thirty percent deposit with monthly milestones. He also asks that the English version prevail, as that's the language he reads fluently, and he has a lawyer review the final draft. The client agrees to most changes, and the project starts on a safe footing.

6:18 Watch me: checklist review

Watch me check a contract with the checklist. I open the client's draft beside the checklist from the lesson. Parties: correct legal names? Yes. Scope: does it reference the SOW and exclusions? Yes. Acceptance: missing, so I add deemed acceptance after five working days. Revisions: defined. Fees and currency: fine, but no mention of transfer fees, so I add that each party pays its own bank charges. Late payment: I add a right to pause work after fourteen days overdue. IP: on full payment, good. AI use: missing, so I add our standard clause. Liability: capped. Termination: kill fee added. Governing law: agreed. Six minutes, four fixes.

7:05 Common mistakes

Let's list the common mistakes. Working without a contract because they're a friend, or it's urgent. Transferring IP before payment. No kill fee or termination clause. No acceptance clause. Ignoring governing law in international work. Signing a client's template without reading the liability and payment clauses. Silence on AI use, which leads to awkward questions later. And never getting a lawyer to review your template even once. One review, reused for years, is excellent value.

7:38 Recap and try this now

Let's recap. A contract is the rulebook that makes the relationship safe. Cover scope, acceptance, revisions, fees, currency and transfer fees, late payment where lawful, IP on full payment, AI use, confidentiality, liability, termination and governing law. Internationally, rely on practical protections: deposits, milestones, advance billing and rights on payment. Your try this now: compare your current contract, or a client's template, against the clause checklist, list what's missing, and book a one-off review of your template with a qualified lawyer. Next, we'll onboard clients so projects start well.