Freelancing: Upwork

Sefism.Freelancing: Upwork

Tauseef Fayyaz

Chapter 06

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.

Kickoff

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.

Status update

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

Time zone overlap

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.

Handling revisions

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.

Submitting work on Upwork

What: Using Submit Work for Payment on a funded fixed-price milestone. The client then has 14 days to approve or ask for changes, after which the funds are released automatically.
Why: It is what makes fixed-price payment protection apply. Delivering only through messages does not start the review period.

Hourly payment protection

What: Upwork's protection for hourly contracts when you log time with the desktop app tracker, with memos, within the weekly limit, as a verified freelancer working for a client with a verified billing method.
Why: Manual time and idle segments are not protected, so tracked time with clear memos is what gets you paid if a client disputes hours.

Handover

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.

Asking for a review

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.

Job Success Score

Also called JSS

What: Upwork's measure of client satisfaction, based on feedback, how contracts ended and long-term relationships over 6, 12 and 24 months. 90 percent or more is excellent.
Why: It is shown on your profile and needed for Top Rated. Below 79 percent Upwork says new work gets hard to win.

Watch out

Leaving a failing contract open instead of ending it honestly; how contracts end is part of the score.

Dispute

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