Delivering work and handling revisions
How to submit a milestone so it gets approved rather than queried, what auto-approval protects you from, how to handle revision requests including ones that are really extra scope, and what to do when a client goes silent.
Delivery is where a contract is won or lost. The work itself matters, obviously, but how you submit it changes how it is received more than most freelancers expect.
Submitting a milestone
Mark the milestone as submitted and attach the deliverable. Then write the message that goes with it, which is the part people rush.
A good submission message covers:
What you delivered, against what the milestone asked for. Go through the requirements and confirm each. A client who can tick items off approves quickly; one who has to work out whether everything is there does not.
Anything you did differently, and why. Never hide a deviation and hope it is not noticed. Explaining a judgement call reads as expertise; being caught in one reads as carelessness.
Anything you need from them for the next stage.
How to check it. A link, credentials, where to look. Make approving easy.
Two minutes on this message routinely turns a three-day approval into a same-day one.
What happens next
The client approves, requests a revision, or does nothing.
If they approve, the money is released to your wallet, where it goes through clearance before you can withdraw it. See How and when you get paid.
If they do nothing, the milestone auto-approves after a set period and releases normally. This exists to protect you: without it, a client who goes quiet leaves you with delivered work and no way to be paid. The countdown is on the contract.
Auto-approval is a backstop, not a strategy. A client who is chased politely and approves is better for you than one who lets a clock run out, because the second is unlikely to hire you again.
Revision requests
Expect them. A revision request is not a failure and is not an insult; it is the normal shape of collaborative work.
Read it fully before responding. The instinct is to defend. Resist it for ten minutes.
Separate what is in scope from what is not. This is the crucial distinction, and it decides whether you make money on the contract.
Do the in-scope corrections properly and without friction. Do not do them grudgingly or partially. A client who has to ask twice for the same thing writes a different review from one who asks once.
Resubmit with a note listing what you changed and where.
When a revision is really extra scope
This is the situation freelancers handle worst.
A client asks for something that was not in the agreed scope. It is not unreasonable of them — they usually do not realise. But doing it free trains them to keep asking, and doing it silently means the pattern continues to the end of the contract.
Handle it directly and without drama:
"Happy to do that. It is outside what this milestone covers, so I would suggest adding it as a small additional milestone. Roughly [X] and [Y] days. Shall I set that up?"
That sentence is polite, it does not accuse anyone, and it puts the decision back where it belongs. Most clients say yes without a second thought, because they were not trying to get free work — they simply did not know it was extra.
Where scope is genuinely ambiguous, decide whether it is cheaper to absorb it than to argue. Sometimes it is. Make that a decision rather than a default, and if you absorb it, say that you are — otherwise it sets the expectation anyway.
When a client goes silent
Message once, politely, after a couple of days. Assume good faith; people get ill and go on holiday.
Check the auto-approval clock. If it is running, you may not need to do anything.
If a milestone is delivered and the clock is not running for some reason, or the contract has stalled entirely, contact support. Do not simply abandon it — an abandoned contract damages your completion rate, which is heavily weighted in your rank.
If they reappear with complaints after a long silence, respond to the substance calmly and keep it on the platform. The record of you delivering on time and following up is the record that matters if it becomes a dispute.
When you cannot deliver on time
Say so early. A client told on day three that a two-week job will take three weeks is usually fine. The same client told on day fourteen is not.
Late is survivable. Late and silent is not, and it is the difference between a four-star review mentioning a delay and a dispute.
If you genuinely cannot complete the work at all, say so as early as you can and offer to release the escrow back. It costs you the contract and it protects your record far better than disappearing does.
Things that go wrong repeatedly
Delivering to the wrong place. Send work through the platform. Files in a private channel do not exist as far as any dispute is concerned.
Delivering something adjacent to what was asked. If you think the request is wrong, say so before building the alternative, not by delivering it.
Treating the last milestone as optional. Final milestones — documentation, handover, deployment — are where reputations are made. The client remembers the end.
A template for a submission message
Adapt rather than copy, but the structure is what matters.
Start with a one-line summary of what is attached. Then a short list confirming each item in the milestone description and where to find it. Then anything you did differently and why. Then anything you need from them next. Then how to check it — a link, a login, where to look.
Five short blocks, two minutes to write, and it consistently turns a slow approval into a fast one.
Managing several contracts at once
Once you have three or four running, delivery becomes a scheduling problem rather than a work problem.
Know which clocks are running. Every submitted milestone has an approval countdown, and every contract has deadlines. Check them together rather than per contract.
Batch your submissions where you can, so review and reply happen in one sitting rather than scattered.
Flag slippage early and everywhere. If one project overruns, the others usually feel it. Telling three clients on Monday is much better than telling one on Friday and two the following week.
Do not take on more than you can deliver. The most damaging thing to a freelance record is not a difficult client, it is over-commitment, and it shows up as missed deadlines across every contract at once.
When work is rejected outright
Occasionally a client says the work is not acceptable at all rather than requesting a revision.
Ask what specifically fails against the agreed scope. If the answer is concrete, fix it. If the answer is that they wanted something different from what was agreed, that is a scope conversation and it may be additional work rather than a defect.
Do not offer a refund reflexively to end an uncomfortable conversation. If you delivered what was agreed, you are entitled to be paid for it, and the dispute process exists precisely so that this does not come down to who is more willing to be difficult.
Handling a difficult client well
Most clients are reasonable. Occasionally one is not, and how you handle it decides whether it costs you a contract or a reputation.
Stay factual. Respond to what was said, not to the tone. A calm, specific reply is both more effective and better evidence if it becomes a dispute.
Keep it on the platform. Everything you would rely on later has to be visible.
Do not do unpaid extra work to make the problem go away. It rarely works and it establishes the pattern for the rest of the contract.
Know when to stop. If a client is abusive, report it. If the engagement is unrecoverable, end it properly rather than enduring it — but end it formally, with a handover, rather than disappearing.
Finishing well
The last milestone is the one clients remember, and it is the one freelancers most often rush.
Deliver the unglamorous parts properly: documentation, handover notes, credentials, a short summary of what was done and anything the client should know. It takes an hour and it is what turns a satisfied client into a repeat client.
Then ask for a review while the work is fresh. Most clients intend to and forget.
Repeat hires are the strongest signal on your profile, and they come almost entirely from how the last week of a contract went rather than the first.
Common questions
What if the client asks for more revisions than agreed? Those are additional work. Offer to add them as a small milestone.
Can I withdraw a submission? Resubmit with the corrected work and explain in the message.
What if the client never approves? Auto-approval releases the money after a set period.
Should I deliver outside the platform if the files are large? Share access to appropriate storage, but record on the contract exactly what was delivered and when.
Related
Did this answer your question?
Did this not answer it?
Open a ticket and a person will read it. You do not need an account.