Scope creep almost always starts with one sentence
Think of the worst job you've taken — then go back and read the message where you agreed to it. Nine times out of ten you'll find a line like: “design the company website,” “handle social content for a month,” “edit three videos,” “get the system sorted.”
Those sentences feel clear. They say nothing about how many pages, who writes the captions, how many hours of raw footage, or what “sorted” means. Those gaps don't disappear — they get resolved later, mid-project, when you're in the weakest position: half the work delivered, the final payment outstanding, and every clarification carrying a relationship cost it wouldn't have carried on day one.
Most clients aren't trying to take advantage. They're interpreting the words in front of them, and the words allowed their interpretation. Which is why scope isn't defensive paperwork for the day things go wrong. It's the instrument that lets you price the job correctly on the day it starts.
Scope has three layers, not one
Most freelancers write only the first layer. The other two are where projects sprawl.
Layer 1 — deliverables. What the client receives: countable, with file formats, sizes, quantities, and an explicit list of what isn't included.
Layer 2 — process. What happens along the way: how many meetings and how long, how many review rounds, your response time in working days, and which channel is official. Leave it blank and the client will reasonably assume meetings are unlimited and a message at 10pm is normal.
Layer 3 — client inputs. What they must give you before you can work: copy, logos, system access, the name of whoever approves, and by when. In practice this is the most valuable layer, because most late freelance projects aren't late because the freelancer was slow. They're late waiting on the client — and then somehow it's the freelancer's delay.
Write deliverables you can count and sign off
A simple test: if someone unfamiliar with the project can't count the items from your description, it isn't written yet.
Instead of “design the company website,” write: “design five pages (home, about, services, work, contact), delivered as Figma files including a mobile version of each page. Copywriting, photography and deployment are not included.”
The exclusions carry as much weight as the inclusions — often more, because they're where silent expectations live. Three to five lines of “not included” removes the hardest conversation of the project before the project begins.
Then add acceptance criteria: when is a stage actually finished? Something like “a delivery is accepted when the client confirms in writing, or seven working days after delivery if no revision request is received.” That single clause resolves the classic situation where a job has been sitting in “waiting for the client to look at it” for three months and you still can't bill it.
Revision rounds: cap them, and price the next one in advance
Capping revisions isn't precious — it's just knowing your costs. State how many rounds the price includes, how a round is counted (one consolidated set of feedback, not a trickle of individual messages), and what the next one costs.
Publishing the price of the extra round matters more than the cap itself. Once the client knows it up front, asking for more becomes a business decision on their side rather than a favour requested from you — and you never have to open a money conversation mid-project, which is exactly the conversation most freelancers avoid until they've worked for free.
Out-of-scope work deserves the same mechanism: “additional work will be quoted in writing and begins on written approval.” That gives you a third answer beyond yes-for-free and no.
Deadlines run both ways
Most agreements pin down the freelancer's dates and leave the client's completely open, even though half of all delays originate there.
The fix is to tie your dates to receipt rather than to the calendar: “first draft within 10 working days of receiving complete copy and system access.” Add that any delay in client materials moves the delivery date by the same number of days.
For longer engagements, include a stall clause: if the project is inactive on the client's side for more than 30 days, work completed becomes payable, and restarting is subject to your schedule at that time. This prevents the pattern where a half-finished project — and half-finished payment — sits frozen for a quarter.
Payment terms: deposit, stages, and a real date
A structure that fits most freelance work: 30–50% deposit before starting, mid-stage payments tied to verifiable deliveries, balance on completion. One principle governs it — never let the value of unpaid delivered work exceed what you can afford to lose.
Details that are easy to skip and expensive to skip:
- Put a calendar date on the invoice, not a floating “net 30.” Many companies count from their own billing cycle, not from the day you sent it.
- Ask about the billing cycle on day one. Plenty of Thai companies accept billing only on the 25th, or once a month. Miss it by a day and the money moves a month.
- State a late fee at a reasonable rate. You may never charge it; it still changes where you sit in the accounts payable queue.
- Say who pays transfer fees, especially for overseas clients where intermediary bank charges can run into the thousands of baht.
Put the tax terms in writing before the transfer, not after
Three items explain why the amount landing in your account rarely matches the invoice — and why so many freelancers chase payments that were never short.
Withholding tax. Service and hire-of-work payments from Thai companies are withheld at 3%. Your quotation should say the price is before withholding tax and that the client will issue the withholding tax certificate (50 Tavi) each time. That certificate is your tax credit at filing time; collect it at payment, or spend next March chasing dozens of them.
If the client pays through the bank e-Withholding Tax system, the rate drops to 1% under the incentive extended to 31 December 2027, and the record is visible in the Revenue Department's system. It's worth asking corporate clients whether they use it — the difference in cash you hold during the year is real.
VAT. Above ฿1.8 million of annual revenue you must register, and every quote needs to state clearly whether the price includes or excludes 7% VAT. Ambiguity here has cost freelancers 7% of entire projects.
Copyright: Thai law doesn't default to the creator
This is the single most common misunderstanding. Under Section 10 of the Copyright Act B.E. 2537, work created under a commission belongs to the person who commissioned it, unless agreed otherwise — the reverse of Section 9, which covers employees and leaves copyright with the creator.
So by default your client already owns it. If you want something different — a licence limited to specific uses, rights limited to Thailand, or retention of your source files and reusable components — it has to be written down. And tie the transfer to payment: “copyright transfers upon receipt of payment in full” is worth more than a page of legal prose.
Always ask for portfolio rights too. Once copyright sits with the client, showing the work requires permission; specify when you may publish it, for example after public launch. Moral rights under Section 18, including attribution, remain yours regardless of transfer.
Cancellation, and the compensation that should follow
Projects get cancelled. What's abnormal is not having written down what happens when they do. Two short clauses cover it: the deposit is non-refundable, and cancellation after work begins is payable pro rata for work completed to the notice date, plus any stage already due.
For work that reserves your calendar — shoots, events, a booked-out week — a tiered cancellation fee (25% inside 14 days, 50% inside 7) is standard practice across industries, not an aggressive ask. You turned down other work to hold that slot.
An agreement doesn't have to be long to work
A lot of freelancers skip contracts because they picture ten lawyer-drafted pages. In reality a one-page agreement covering seven headings — scope, exclusions, revisions, schedule and client inputs, payment, copyright, cancellation — prevents well over ninety percent of what actually goes wrong.
And legally, a clear agreement by email or chat can bind; you don't need a wet signature. For small jobs the smoothest route is to put the entire scope into the quotation and ask the client to reply confirming approval of that quotation number. That's a usable record, with no extra step for either side.
Check before you send the quote
- Are the deliverables countable, with file formats stated?
- Is there a list of at least three exclusions?
- Are revision rounds capped, with the next round priced?
- Are the client's inputs and their due dates specified?
- Are your dates tied to receipt of materials rather than the calendar?
- Are acceptance criteria and the silence rule written down?
- Are the deposit, stages and due dates real calendar dates?
- Are 3% withholding, the 50 Tavi certificate and VAT addressed?
- Are copyright, portfolio rights and transfer-on-payment covered?
- Are cancellation terms and the non-refundable deposit stated?
A well-written scope doesn't make you look difficult. It makes you look like someone who has done this before. Practically, it's the difference between a project that ends with the money collected and one that ends with three more months of conversations about money.
If you'd like the scope, terms and payment stages to live in the same place from quotation through to receipt, MANA keeps all three alongside the project and the income — so what you agreed and what you actually collected are the same set of numbers.