TL;DR: The first week of a new Upwork contract sets how the rest of it goes. Within a day of accepting, send a kickoff message that restates the first deliverable, the date and how you will communicate. Confirm the contract is set up the way you agreed: a funded milestone on fixed-price work, or the right rate and weekly limit on hourly work. Collect access and files early, ask your open questions in one batch, and agree on how often you will update the client. Then deliver something small and visible early, keep every message and file on Upwork, and log any scope change the moment it happens. Most contracts that end badly show the warning signs in week one, and most of those signs are fixable while they are small.
Getting hired feels like the finish line. It is closer to the starting line. The first few days decide whether a client becomes a five-star review, a repeat buyer, or a dispute.
A quick note: Upwork changes contract screens, milestone flows and payment protection rules from time to time. Check the current help pages and your own contract page before relying on any specific detail here.
Before you start work: check the contract itself
The offer you accepted is the contract. Before you write a line of code or a word of copy, open the contract page and confirm it matches what you discussed in chat. Got an Upwork offer? What to check before you accept covers this in detail, but the short version for day one is:
- Fixed-price: is the first milestone funded? A funded milestone means the client's money is held in escrow for that piece of work. An unfunded milestone protects nobody. Upwork milestones explained covers how funding and release work.
- Hourly: are the rate and the weekly limit what you agreed? The weekly limit caps how many hours you can bill in a week. If you expect to work 20 hours and the limit is 10, fix it now, not after you have done unpaid time.
- Scope: does the contract description, or the milestone description, say what you will deliver? If it is vague, your kickoff message is where you make it specific.
If something is off, raise it politely before you begin. "Before I start, I noticed the first milestone is not funded yet. Could you fund it when you get a moment?" is a normal, professional message.
Send a kickoff message within a day
The kickoff message turns a loose conversation into a shared plan, and creates a written record on Upwork both sides can point back to.
A good kickoff message covers five things:
- Thanks, briefly. One line. Do not gush.
- The first deliverable and its date. "First up: the homepage redesign in Figma, which I will share by Thursday."
- What you need from them. Logins, files, brand assets, a contact person, answers to specific questions.
- How you will communicate. Where updates will go (Upwork messages), how often, and when you are usually online.
- What happens after the first deliverable. A one-line view of the next step, so the client can see the path.
Here is an example you can adapt:
Thanks for the offer, happy to get started. Here is the plan for the first week:
First deliverable: a working draft of the product import script, tested on your sample CSV, by Friday.
What I need from you: read access to the staging store and the sample CSV. One question: should duplicates overwrite existing products or be skipped?
I will post a short update here every Tuesday and Friday, and I usually reply within a few hours between 9am and 6pm UTC.
Once the draft is approved, I will move on to the error reporting piece we discussed.
Many clients have been burned by freelancers who went quiet after accepting. A clear plan on day one answers the question they are silently asking: did I hire the right person?
Collect access and ask questions in one batch
Missing access is a common reason a new contract stalls in week one. You wait for a login, two days pass, and your first deliverable is late for reasons that were not your fault but still look like it. Ask for everything in the kickoff message, and group your questions: one message with five clear questions gets answered, five separate ones feel like noise.
A few practical rules:
- Ask for the minimum access the work needs. If read access is enough, ask for read access.
- Never ask for or accept credentials that do not make sense for the job. A data entry contract does not need the client's bank login. How to spot Upwork job scams covers the patterns where a "client" asks for things that put you or them at risk.
- Write down assumptions. If a question is still open when you need to start, say what you are assuming and proceed. "I have not heard back on duplicates, so I will skip them for now and can change that in five minutes." That keeps work moving without making silent choices.
Agree on an update rhythm
Clients do not need constant messages. They need predictable ones. A simple update has three parts: what is done, what is next, and anything you are blocked on. Three or four lines is enough, with a screenshot or draft link when you can, because showing beats describing.
How often depends on the contract:
- Short fixed-price jobs: an update at the start, one in the middle, and the delivery.
- Longer fixed-price jobs: one update per milestone stage, plus a mid-milestone check-in if the milestone runs more than a week.
- Hourly contracts: at least weekly, timed before the weekly billing cycle closes so the client sees what the hours bought.
On hourly work, the update matters more because the client is paying for time rather than a result. Upwork Work Diary: what it actually tracks explains how tracked time and memos appear on the client's side. Write memos a client could read without context, because they might.
Deliver something small and early
The fastest way to build trust on a new contract is to show progress before anyone asks for it. It does not need to be finished. A rough draft, a working prototype of one screen, a first section of a document, or a short outline is enough.
Early delivery proves you are working, and it surfaces misunderstandings while they are cheap: if you misread the brief, you find out on day two instead of day ten. How the client responds to a rough draft also tells you a lot about how the rest of the contract will go. Label early work clearly as a draft.
Keep everything on Upwork
Some clients will suggest moving to email, Slack or WhatsApp in the first week. Shared tools for the work itself are common. Moving the relationship and payment off Upwork is a different matter. Keep the terms, scope, deliverables and any changes written in Upwork messages: if there is ever a dispute, that thread is your evidence. Can you work with an Upwork client outside Upwork? explains where the line sits and why taking a client off the platform early can cost you more than the fee you save.
After any call, post a two-line summary in the Upwork thread so the record stays complete.
Watch for scope changes from day one
Scope creep rarely starts as a big request. It starts in week one with "while you are in there, could you also..." Each addition feels too minor to discuss. Together they turn a fair contract into an underpaid one.
Handle it early and lightly: acknowledge the request, say whether it is in scope, and offer a path such as a new milestone or more hours.
Upwork scope creep: how to handle it has scripts for this. The key point for week one is that how you handle the first extra request teaches the client how the rest of the contract will work.
Read the week-one warning signs
Some contracts go wrong no matter how well you start. The first week usually tells you which ones. Watch for:
- The milestone is still unfunded after you have asked politely and started.
- The scope keeps shifting before you have delivered anything.
- Requests to pay or communicate off the platform in ways that bypass the contract.
- Silence after you send questions you cannot proceed without.
- Rewriting the brief every time you share a draft.
One sign alone is often just a busy client. Several together are a reason to slow down and keep your work tied to funded milestones. How to end a contract on Upwork covers how to close one cleanly if it comes to that, and what to do when an Upwork client doesn't pay covers the options if money becomes the problem.
Many of these clients can be spotted before you apply. How to spot good Upwork clients walks through the signals to check.
Why week one matters beyond this contract
A strong first week compounds. Clients who feel looked after early are more likely to leave strong feedback, which feeds your Job Success Score, and more likely to hire you again, which is work that costs no Connects. How to find long-term clients on Upwork covers how repeat clients form, and how to ask for feedback on Upwork has the wording for when the contract wraps up.
Start with clients worth keeping
The best first week starts before the contract does. A client with a verified payment method, real spend, a history of hiring and fair reviews is far more likely to fund milestones, answer questions and respect scope. Finding them is the hard part, because Upwork's search cannot filter on client spend, hire rate or proposal count, and good jobs fill fast.
Upwork Scout watches Upwork continuously and filters new jobs by your niche, budget, payment verification, client spend, hire history and proposal count, then alerts you while the post is still fresh. You spend less time screening and more time on contracts that are worth a strong first week. The free tier lets you set up your filters and start getting alerts today.
The bottom line
Check the contract matches what you agreed. Send a kickoff message within a day that names the first deliverable, the date, what you need and how you will communicate. Collect access in one batch, agree on an update rhythm, and show something early. Keep the record on Upwork and treat the first scope change as practice for the rest. A week of small, deliberate habits is what turns a single hire into a client who comes back.