This guide covers how to manage client expectations at each stage of a project: kickoff, the weeks of work, the moment something slips, and handover. Each section includes example wording you can copy and adapt.
What does managing client expectations mean?
Managing client expectations means making sure the client's picture of the project matches yours. That covers the result, the dates, the cost, the client's own tasks, and how and when you will talk.
Setting expectations happens before work starts. Managing them happens during the project. Resetting them happens when a fact changes. You need all three.
Expectations usually go wrong in a few places:
- A call where something was agreed but never written down.
- A request that sounds small but sits outside the scope.
- A client task, such as page text or feedback, with no date attached.
- A long gap between updates, where the client makes their own guesses.
- The end of the project, where nobody said what support looks like.
How do you set expectations with a client at the start of a project?
How to manage client expectations starts at kickoff. Write down what you will deliver, what is not included, the key dates, what you need from the client and by when, and how you will communicate. Send this in writing after the kickoff call, even if you covered it all out loud, and ask the client to confirm it.
People remember calls differently, so the written version is the one that counts.
Example: kickoff summary email
Hi Dana,
Thanks for the call today. Here is what we agreed for the website refresh, so we both have it in one place.
What I will deliver: a new design and build for the home page, about page and contact page, plus a booking form connected to your calendar.
What is not included: new photography, writing page text, and changes to your online shop.
Key dates: design draft on 6 June, build ready for review on 27 June, launch on 4 July.
What I need from you: final page text by 30 May and your feedback on the design draft by 11 June. If these move, the launch date moves by the same amount, and I will tell you the new date in writing.
How we will stay in touch: I will send a short update every Friday with what got done, what comes next and anything I need from you. For quick questions, email me and I will reply within one working day.
Revisions: the design includes two rounds of changes. Extra rounds are billed at my hourly rate, and I will always check with you first.
Please reply to confirm this matches your understanding, or tell me what to change.
Sam
This email names what is not included, which is where many disagreements start. It ties the client's tasks to the dates. And it asks for a reply, so silence does not count as agreement.
If you send a welcome email before kickoff, the client onboarding email template covers what to put in it.
Ask what a good result looks like to them
Before you write the summary, ask the client how they will judge the project when it's done. You might hear "more bookings", "something my board will approve" or "live before our event". These goals shape what the client expects, even when they never write them down.
You could ask: "When this is finished, what will tell you it went well?" Then reflect the answer in the summary, or say plainly if it depends on things you can't control.
Say no to the unrealistic parts early
If a date, budget or result is not realistic, say so at kickoff. It is much easier to change a plan before anyone has committed to it.
Example: pushing back on a date at kickoff
I can see why you want this live by 20 June. With the three pages and the booking form, the earliest date I can commit to is 4 July. If 20 June is fixed, I could launch the home page and booking form first and add the other two pages the week after. Which would suit you better?
Give a reason, offer an option and ask the client to choose. The decision stays with them, and they know exactly what each choice means.
How to manage client expectations during the project
During the project, send a regular update on a fixed day, even in slow weeks. Each update should say what got done, what comes next, and what you need from the client and by when. When the client knows when the next update will arrive, they stop guessing.
If a client often asks "how's it going?", your updates are probably too far apart or hard to find. If your client has to ask explains how to fix the schedule without blame.
Example: weekly update
Hi Dana,
Done this week: the home page and about page designs are finished. Both are in the attached PDF.
Next week: I will start the build and connect the booking form to your calendar.
What I need from you: your feedback on both designs by Tuesday 11 June. Comments on the PDF are fine.
Launch is still planned for 4 July.
Sam
That last line matters. It repeats the main expectation every week, so the client never has to wonder whether the date still stands. The guide to writing a weekly client update covers this format in more detail.
Handle extra requests in writing
A small request agreed on a call can become part of the project in the client's mind. When a request falls outside the agreed scope, reply in writing with what it would change and let the client decide.
Example: reply to an extra request
Adding a newsletter signup to the contact page is a good idea. It wasn't part of the original plan, so here are the options:
- Add it now. It takes about half a day, costs $300, and moves launch from 4 July to 7 July.
- Launch as planned and add it the week after.
Let me know which you prefer and I will update the plan.
Doing it for free to avoid the conversation sets a new expectation that more free work will follow.
How do you reset expectations when things slip?
When something slips, tell the client as soon as you know the likely effect. Say what happened, what it changes, what you are doing next, and when you will update them again. Don't wait until you have every answer, and don't hide the change at the end of a long message.
The client may need to tell their own manager or move their own plans. The sooner they know, the more options they have.
Example: a date slips because of your side
Hi Dana,
The build will not be ready for review on 27 June as planned. The calendar connection for the booking form needs more testing than I expected, and I don't want to hand you a form that double-books appointments. The new review date is 2 July, and launch moves from 4 July to 9 July.
I will confirm progress by Friday 28 June, even if nothing has changed.
Sam
Example: a date slips because a client task is late
This one is harder, because it can sound like blame. Stick to the facts and the effect.
Hi Dana,
I haven't received the final page text yet, which was due on 30 May. I can keep working on the design with placeholder text until 5 June. After that, each day of delay moves the launch date by a day.
If the text will take longer, let me know and we can agree a new date together.
Sam
For more on wording difficult news, see how to tell a client bad news.
What if the client's expectations were never realistic?
Sometimes you find out partway through that the client expected something you never agreed to. Go back to the written agreement, not to who said what on a call. Say what was agreed, acknowledge what they hoped for, and offer a way forward.
Example: correcting an expectation mid-project
I can see why you expected the shop pages to be redesigned too. Our plan from 24 May covered the home, about and contact pages. I'm happy to quote for the shop pages as a second phase. Would you like me to send that this week?
How do you set expectations at handover?
At handover, tell the client what they are getting, what happens if something breaks, what support is included and until when, and when the project ends. Projects often end badly not because of the work, but because nobody said what happens after launch. A client who expects free changes forever will feel let down when your next invoice arrives, even if your contract was clear.
Example: handover email
Hi Dana,
The new site is live. Here is what you have and what happens next.
What you're getting: the three pages, the booking form, and a short guide to editing your page text (attached).
Fixes: if something I built doesn't work as agreed, I will fix it free of charge until 9 August.
Changes and new work: anything new, such as extra pages or design changes, is quoted separately.
How to reach me: email me as usual. I reply within one working day.
Once I receive the final payment, I will send you all the design files and account logins.
Thank you for working with me on this.
Sam
List anything still open
Before you send the handover email, list anything still open: a payment, a decision, a file the client needs to keep, a login they need to change. Put each one in the email with a date. A project with open items doesn't feel finished to the client, even if the work is done.
FAQ
What are the main steps to managing client expectations?
Agree the scope, dates and client tasks in writing at kickoff. Keep those expectations visible with a regular update. Reset them in writing as soon as a fact changes. Close the project with a handover email that says what support is included.
How do you manage client expectations as a freelancer?
How to manage client expectations as a freelancer is the same as for a larger team, with less paperwork. A kickoff summary email, a short weekly update and a handover email cover most of it. Put your response times and working hours in the kickoff email so the client knows when to expect a reply.
Is it better to under-promise and over-deliver?
Promise what you can realistically deliver. If you always pad your dates, the client learns that your dates don't mean much. Give a real date and keep it, or reset it early and in writing.
Conclusion
How to manage client expectations comes down to writing things down and repeating them. Agree the plan at kickoff, confirm it in every update, reset it as soon as it changes, and say clearly what happens at handover. Most clients accept a change when they hear about it early and in plain words.
Friday helps with the middle part. You write one short update each week per project, covering what got done, what comes next, and what you need from the client and by when. The client gets it by email, and every update stays on a private page for the project, so the agreed dates are always easy to find. You can try Friday free for 30 days, no card needed.