Delivering and earning reviews

Running a project so the client feels informed, handling revisions and handover properly, and earning the reviews that bring the next client.

What: The start of a project where you confirm scope, deadlines, the client's inputs, how and when you will communicate, and who approves the work.
Why: Most later problems are misunderstandings that a ten-minute kickoff would have caught.

What: A short, regular message: what is done, what is next, any blocker or question, and when the next update will come.
Why: Clients worry when they hear nothing. Predictable updates build trust faster than fast work does.

Code

Done: booking form and email alerts
Next: payment page, ready Thursday
Need from you: the clinic logo in SVG
Next update: Thursday evening

Also called time zone

What: The hours when both you and the client are working. Agree a reply window and a regular call slot inside it.
Why: A freelancer in Lagos or Manila and a client in California may share only an hour or two, so plan questions to avoid losing whole days.

What: Collecting all feedback for a round in one list, confirming which items are in scope, fixing them, and summarising what changed on redelivery.
Why: Organised rounds stay inside your revision limit and show the client you listened.

Watch out

Fixing each comment as it arrives in chat, which turns two rounds into twenty.

What: Delivering through the order page. The buyer has three days to accept, ask for a revision or extend review, after which the order completes automatically.
Why: Only completed orders count for your level and start the clearance clock, so deliver on the platform with a short summary of what is included.

Watch out

Sending files by email or a link outside the order, which leaves nothing on record if the buyer disputes delivery.

What: The final package: files, repository access, logins transferred to the client, a short guide to running or editing the work, and what support is included afterwards.
Why: A clean handover ends the project well and prevents months of "how do I change this" messages.

Watch out

Keeping hosting, domains or accounts in your own name so the client depends on you without realising it.

What: After a good delivery, asking the client to leave feedback, and on direct work asking whether you can quote them as a testimonial.
Why: Early reviews are your most valuable asset, and many happy clients simply forget to leave one.

Watch out

Offering discounts or extras in exchange for five stars, which breaks platform rules.

Also called Success Score

What: A 1 to 10 score for each seller built from how orders go and how clients respond, compared with sellers at similar prices.
Why: It is one of the six metrics for every level, and a very low score marks the account as low performance and cuts visibility.

What: A formal disagreement about payment or delivery. Upwork and Fiverr have processes that use the contract, messages and delivery records on the platform.
Why: Your written scope, messages and on-platform delivery are the evidence. Without them, a dispute is your word against the client's.

Go deeper