Scoping, Contracts, and Boundaries

Most freelance projects don't go bad because of the work. They go bad because nobody agreed on what the work actually was. This article is about pinning that down before you start, protecting it on paper, and holding your boundaries once the project is running.

Ask a lot of questions

Before you quote anything, you need to know exactly what you're being asked to make. Ask until it's clear, and get the answers in writing. At minimum:

• Resolution
• Frame rate
• Colour space
• File formats
• Every version, adapt, and deliverable they'll need
• The deadline, and the real one behind it

Artists lose money on the versions and adapts nobody mentioned upfront. "Can we also get a square cut and a 15-second version?" is a whole extra job if it wasn't in the original scope. Surface all of it before you price.

What a good brief looks like

A good brief is short, specific, and honest about constraints. It has:

• Context: what this is for and why it exists
• Scope: exactly what you're delivering, and what you're not
• Constraints: the technical specs above, plus any creative guardrails
• Timeline: clear dates, including when you need feedback from them

If the brief is vague, that's not a green light for you to guess. It's a conversation to have before anything is agreed.

And if there genuinely are no creative guidelines, get it in writing that your judgement is what's being trusted. One line in the confirmation email does it: "No fixed brief, the artist's creative direction is approved." Without that, a client mood-swing three weeks in becomes your fault, when there was never a spec to violate in the first place.

Cap your revisions

Agree on a fixed number of feedback rounds and a fixed timeline, and write it down. Two or three rounds is normal. Anything past that is extra work at extra cost.

This protects both sides. It stops a project from dragging on forever, and it makes feedback more deliberate because rounds are finite. Projects also stall on the client side, not yours. Slow approvals, people going quiet, decision-makers disappearing. Those delays are their cost, not yours. Time is money, for you and for them.

Put it on paper

For every project, even small ones, get the terms in writing. A proper contract is best. When a contract isn't happening, at the very least get an email that confirms the scope, timeline, payment terms, and rights. I almost always get at least the email. A signed contract is better, but the email is the floor.

What your contract or confirmation must cover:

• Scope and deliverables: exactly what you're making, spec'd out
• Timeline and revision rounds: how many, by when
• Payment terms: total, advance, milestones (see the pricing article)
• Advance: 30–50% upfront, always, no exceptions
• Kill fee / termination clause: if they cancel halfway, you're paid for your time
• Late-payment penalty: a daily charge on overdue invoices
• Storage / holding fee: a daily charge if the client goes silent mid-project while you're holding their files or sitting on reserved time
• Portfolio rights: in writing, that you can post the work on social media and in your portfolio
• Jurisdiction: which city's courts the contract falls under. Name yours. It matters the day you have to chase a payment

That last one matters more than people think. If it's not written down that you can show the work, you might not be able to, and your portfolio is how you get the next job.

Track scope creep

Projects grow. A tweak here, an extra element there, a "small" addition that's actually half a day of work. Left unchecked, you end up doing 130% of the job for 100% of the money.

The habit is simple: the moment new work gets added, call it out. Note it, tell the client it's additional, and price it before you do it. Keep all these change requests in an email thread so there's a written record. You're not being difficult. You're getting paid for the work you do, which is the entire deal.

Boundaries

Set them early, state them plainly.

• Working hours. Tell clients your availability up front. Don't work weekends by default. The time that's yours stays yours.
• Availability expectations. You're not on call. Messages at odd hours don't get instant replies.

Same logic as the mindset piece: clients take their cue from you. Treat your time as unlimited and so will they. Hold the line calmly and the respect follows.

Opportunity cost

Every project you take is a project you can't take. If you're already booked, a new job means saying no to it, or doing worse work on both.

So a cheap, draining project isn't just cheap. It's blocking the better one that might come next week. Factor that in. Account for the hidden time too: the meetings, the render waits, the feedback delays. A "small" project that eats your calendar isn't small.

This is the abundance mindset from the first article, applied to your schedule. Guard your time like it's your most limited resource, because it is.

A project checklist

Once a project is a go, run it through this so nothing slips:

1. Contract (or confirmation email) signed
2. Welcome doc: how you work, timelines, what you need from them
3. Advance invoice sent and paid before work starts
4. Access request: resources, references, brand docs, logins
5. Kick-off call to align on everything above
6. Feedback request at each agreed milestone, in writing

---

You've scoped it, papered it, and set your boundaries. The last piece is the pipeline: finding good clients, and spotting the bad ones before they cost you.

Next up: Getting Clients & Spotting Bad Ones.

Freelancing in 3D in India? Share templates, briefs, and war stories with the community at 3dartists.in.