A good freelance contract does not need legal theatre. It just needs to remove ambiguity before the first design file is opened.
Most agency problems with freelancers are not talent problems. They are expectation problems: unclear rounds, unclear licensing, unclear deadlines, and unclear payment terms. A practical contract fixes that early.
Below is the structure I see work best with Australian agency teams. It borrows from both large network and smaller studio contracts I have worked under, then simplifies them into one practical template.
What to include in a freelance design contract
Engagement section
Services, start date, and whether each project uses a separate engagement request form.
Commercial section
Day rate or hourly rate, invoice cadence, payment terms (for example 14 days), and overtime.
Confidentiality + IP
Confidential handling rules, return of files, IP ownership, and any prior IP carve-out.
Operations section
Time tracking method, response windows, tools and equipment, and notice/termination rules.
Suggested clause order for agencies
Pick-and-mix template clauses (ready to adapt)
Plain English: this makes the work type and response expectation explicit so projects do not stall while people wait for confirmation.
Plain English: everyone knows what is included in a normal day, and any late additions are billed fairly instead of argued about later.
Plain English: this sets a predictable payment rhythm so there is no confusion about when invoices go out or when cash is due.
Plain English: this protects sensitive campaign and client information during the project and after it ends.
Plain English: the client gets ownership of what they paid for, while the freelancer keeps pre-existing tools, frameworks, or reusable assets.
Plain English: this confirms the freelancer is not an employee, handles their own tax setup, and can still work with other clients.
Agency Edition vs Designer Edition
If you are reading this from an agency side, focus on risk control, speed, and clean handover. If you are a freelance designer, focus on scope protection, payment clarity, and rights boundaries. The same template can serve both sides, but the emphasis should change.
Agency Edition Focus
Clear approvals, predictable payment cycle, confidentiality controls, and ownership terms that prevent delivery delays.
Designer Edition Focus
Defined scope, tracked overtime, approved expenses, and clause wording that prevents open-ended revisions or late-payment stress.
The six clauses agencies should never skip
| Clause | Why it matters | What happens without it |
|---|---|---|
| Engagement request mechanics | Lets teams scale work in/out without rewriting the whole agreement each time | Scope confusion across multiple projects |
| Invoice cadence + 14-day terms | Keeps cashflow predictable for both sides | Late payment disputes and admin drag |
| Pre-approved expense rule | Avoids surprise costs and reimbursement arguments | Disputed out-of-pocket claims |
| Confidentiality + return of property | Protects client information and working files | Data leakage risk and unclear handover |
| IP assignment with prior IP carve-out | Gives client ownership while protecting reusable pre-existing assets | Ownership ambiguity after delivery |
| Termination + mediation path | Provides clear exit process and dispute path | Escalation, delays, and avoidable legal friction |
Template language that keeps things clear
For agency teams, plain wording usually performs better than legal-heavy language. For example, writing "two feedback rounds included" is clearer than burying that in abstract legal terms.
The same applies to file delivery. State whether handover includes packaged source files, exported assets only, or both. It avoids the classic last-day confusion.
- Define one project owner who consolidates feedback and approvals.
- State where time is tracked (for example, PM tool plus time tracker export).
- Use clear payment dates (for example, "14 days from valid invoice").
- Add governing law and amendment-in-writing clauses to avoid version drift.
- Keep every clause plain enough that producers and creatives can both use it fast.
Download the Freelance Contract Template (PDF)
Enter your details below and I will send you straight to the template PDF.
Thanks — your download should begin automatically. If it does not, click here to open the PDF.
A contract should speed up collaboration, not slow it down. If both sides can read it once and know exactly how the project will run, the template is doing its job.
Note: this is an operational template based on real-world agreement structure, not legal advice. For final legal sign-off, run your version past a qualified Australian lawyer.