Table of Contents
Most freelancers use contracts the way most people use medicine leaflets: relieved they exist, never actually read. But every clause in a service contract is a pre-answered argument — and knowing what each one does lets you negotiate intelligently, spot missing protections, and recognize when a client's template quietly disadvantages you. Here's the plain-language tour. (Foundation reading: how to write a contract.)
Scope of Work — the load-bearing wall
Defines what you'll deliver, in what form, and — the half everyone skips — what you won't. Every scope-creep battle is won or lost here, months before it happens. Trap to avoid: activity language ("design services for the brand") instead of deliverable language ("one logo, two revision rounds, files in AI/PNG/SVG"). Activities are infinite; deliverables end.
Payment Terms — the reason the document exists
Amount, schedule (advance, milestones, final), due dates, late-fee interest, and currency/taxes (GST treatment stated). Trap: "payment on satisfaction" or "on approval" clauses — they hand the client a perpetual free option. Payment triggers should be events you control (delivery of X) or dates, never feelings.
Timeline & Client Obligations — the two-way street
Your deadlines, and theirs: feedback windows, asset delivery, approvals. Without client-obligation language, their three ghost weeks become your "missed deadline." Standard fix: "timelines extend day-for-day with delays in client inputs" (the ghost-then-urgent defence).
Revisions — the infinity-stopper
How many rounds, what counts as a revision vs. new scope, and the rate beyond the cap. The single highest-ROI clause per word in creative work.
Intellectual Property — who owns what, when
The default surprises people: in India (and most jurisdictions), the creator often retains copyright absent written transfer. Your clause should state what transfers (final deliverables), when ("upon receipt of full payment" — five words that convert your invoice into leverage), what you retain (working files, unused concepts, portfolio rights), and any third-party materials (fonts, stock, music licenses) passed through under their own terms. Trap: "all work product, including preliminary materials, work-for-hire, assigned in perpetuity" — client templates love this; carve out your process assets and portfolio rights.
Confidentiality — reasonable, bounded
You'll see their unreleased products and internal chaos; they may see your rates and methods. Fine — but bound it: what's confidential (marked/reasonably obvious), for how long (2–3 years, not "perpetual"), with standard carve-outs (already-known, independently developed, legally compelled).
Indemnity & Liability — the clause to actually read in client paper
Liability cap: your exposure limited to fees paid — without it, a ₹40,000 project theoretically carries unlimited downside. Indemnity: who pays if a third party sues (e.g., over content the client supplied — their indemnity; over work you plagiarized — yours; keep it symmetric and fault-based). Trap: one-way indemnities and uncapped "consequential damages" in corporate templates — these are negotiable more often than freelancers assume; ask.
Termination — the exits, priced
Either party's right to end with notice (15–30 days), what's owed on exit (work done + non-cancellable commitments), and kill-fee mechanics for event businesses. A contract without exits traps you as much as them.
Force Majeure, Disputes, and the Boring End Matter
Force majeure: performance excused for genuinely uncontrollable events — reschedule mechanics beat refund mechanics. Dispute resolution: governing law and city of jurisdiction (pick yours); mediation-first language keeps small disputes cheap. Entire-agreement clause: the document supersedes every WhatsApp promise — which is why everything promised goes in the document.
Reading Client Paper: The 10-Minute Checklist
When the corporate MSA lands, check five things: payment trigger (event/date, not satisfaction), IP scope (deliverables, not your toolkit), liability (capped? mutual?), non-compete breadth (a client can protect their clients, not your whole industry), and termination (can they exit owing nothing for finished work?). Push back politely on the worst two; you'll win more often than you expect — templates are opening offers, not laws.
Build your own baseline once — contract templates adapted to your service, e-signable in minutes, attached to every booking — and the clause knowledge above becomes something you exercise twice a year in negotiations, instead of learning once in a dispute.