Before You Record a Hire: Scope, Milestones, Payment, Ownership
The riskiest moment in a freelance project is the one right after "sounds good, let's do it." Both people are keen to start, the details feel settled, and nobody wants to slow things down with paperwork. Then week three arrives and it turns out you agreed on different things.
So before you record a hire, stop for twenty minutes and go through this list together. It's written for clients, but freelancers can use it just as well.
1. Scope: write down the edges
A scope is only useful if it says what's out as clearly as what's in.
One-sentence outcome both sides agree on.
Bulleted list of included work.
Bulleted list of excluded work (the things that "might come up").
What the client provides: access, content, assets, decisions, and by when.
How change requests are handled: new quote, new milestone, or hourly.
Number of revision rounds, if it's design or writing work.
Tip: read the excluded list out loud. If either person hesitates on an item, discuss it now.
2. Milestones: dates you can check
Milestones turn a long project into short, checkable pieces.
Each milestone has a deliverable you can see or test.
Each milestone has a delivery date.
Each milestone has an amount attached, if paying in stages.
The first milestone is small, so both sides can test the working relationship.
Review time is agreed (for example, the client replies within three working days).
If you can't describe a milestone's deliverable in one line, it's too big. Split it.
3. Payment method and terms
Many freelancers are paid directly, by bank transfer, Wise, Payoneer, PayPal or something else the two sides agree on. That's fine, but it means the terms need to be explicit.
Currency.
Payment method and who covers transfer fees.
When each payment is due (on approval, on a date, net 7, net 14).
What happens if a payment is late.
Whether there's an upfront deposit.
Invoice details: legal names, addresses, tax IDs if needed.
Don't assume the platform you met on is handling any of this. Some marketplaces process payments; others don't. On workli.tech, for example, the platform does not hold funds or act as escrow, and clients pay freelancers directly, so the payment terms in your agreement are the payment terms, full stop.
4. Ownership and access
This section prevents most of the painful end-of-project arguments.
Who owns the final work, and when ownership transfers (often on final payment).
Whether the freelancer can show the work in a portfolio.
Whether an NDA applies, and what it covers.
Which accounts are created in whose name (domains, hosting, repos, app stores).
How credentials will be shared and later rotated.
Third-party assets: fonts, stock images, libraries, and their licences.
Rule of thumb: production accounts should belong to the client from day one. The freelancer gets access, not ownership.
5. Working rhythm and the written record
Short list, but it matters:
Main channel for messages.
Expected response time on each side.
Check-in rhythm (weekly call, written update, or both).
Time zones and overlap hours.
Who on the client side can approve work.
Record it.
Once everything above is agreed, put it somewhere both people can see later. A shared document works. A contract recorded on the platform you hired through also works, and it has the advantage of creating a dated record tied to both accounts. Whatever you use, make sure:
Both sides have the final version.
Milestone dates match what you discussed.
Nobody is relying on a detail that only exists in a call.
A quick sanity pass.
Before anyone starts, each side answers three questions:
- What will I receive or deliver first, and when?
- When and how does money move?
- If we stop halfway, what does each of us keep?
If both people give the same answers, you're ready. If not, you've just found the misunderstanding cheaply.
None of this takes long once you've done it a couple of times. Keep the list as a template, copy it for every new hire, and fill it in during the last call before work starts. The twenty minutes you spend here are the cheapest insurance a freelance project gets.


Comments 0
Replies to this note, oldest first.
No replies yet. Found it useful? Say so below.