How to set client expectations in the first week
Six expectations to state in the first week of a client engagement, each with sample wording you can adapt, plus a short written summary to send after the kickoff.

Clients do not have the same picture of the work that you have. Silence about the details leaves them to fill in the gaps, and they fill them in their own favor. Stating six things out loud in the first week heads off many of the arguments that arrive in month three.
Why the first week
In week one, the client is attentive and goodwill is high. Nothing has gone wrong yet, so a boundary reads as professionalism. The same boundary stated after a dispute reads as defensiveness.
Do not turn this into a lecture. Cover each point in a sentence or two, then put them in a single written summary. Say them, write them, and ask for a reply that confirms.
Expectation 1: how we communicate
Name the channel, the usual response time and when you are not available.
Sample wording: "We will use email for decisions and a shared channel for quick questions. We reply within one working day. If something is urgent, say so in the subject line and call."
Most irritation comes from mismatched assumptions about speed. If the client expects an hour and you plan for a day, neither of you is wrong, but both of you are unhappy.
Expectation 2: what is in scope
State the deliverables and, just as clearly, what is not included.
Sample wording: "This covers a five-page website, written copy and one set of images. It does not cover ongoing content, paid advertising or photography. If you would like any of those, we can scope them separately."
Saying what is excluded is not negative. It gives both sides a clear edge to work from, and later requests are easy to describe.
Expectation 3: how feedback and revisions work
Say how many rounds are included, how feedback should be sent and how long you need to turn it around.
Sample wording: "Two rounds of revisions are included in the fee. Please send feedback in one consolidated message. Extra rounds are billed at our hourly rate."
An example of the cost: an extra round that takes 3 hours at $100 per hour is 3 x 100 = $300. Naming the rate up front means that number is never a surprise.
Expectation 4: what we need from you
Delivery depends on the client's responses as much as your work.
Sample wording: "To keep to the launch date we need your feedback within three working days of each delivery. If it takes longer, the date moves by the same number of days."
This sentence protects you from taking the blame for slippage you did not cause. Put it in writing and refer to it kindly when needed.
Expectation 5: how we will report progress
Say what updates they get, when and in what form.
Sample wording: "You will get a short written update every Friday: what was done, what is next and anything we need from you. We will meet every two weeks for 30 minutes."
Consistency matters more than length. A client who knows when the update arrives stops sending "just checking in" messages.
Expectation 6: how we work with tools, including AI
Clients increasingly ask, or wonder, how you handle their material. Raise it before they do.
Sample wording: "We use a small number of approved tools to work efficiently. We do not put your confidential information into tools that have not been checked, and everything we send you is reviewed by a person."
Be accurate here. Only say what is true of your practice. If you have not yet set rules for your team, the points in what an AI project assistant can answer (and what it can't) are a good place to start.
Put it in a one-page summary
After the kickoff call, send a short email that lists the six points. Keep it plain.
- Communication: channel and response time
- Scope: included and excluded
- Feedback: rounds and format
- Client responsibilities and turnaround times
- Reporting: cadence and format
- Tools and confidentiality
End with: "Please reply to confirm this matches your understanding, or tell us what to change." A reply is a record, and an easy reference later.
Delivering the message well
- Use "we" and "you", not "the client" and "the agency".
- Present it as how you make the work go smoothly, not as rules.
- Say each one once, then write it down. Repeating it in the call makes it sound like a warning.
- Listen for objections. A client who pushes back on feedback rounds is telling you something useful before you have spent a dollar.
Where this fits in the first month
The expectations summary belongs inside a larger routine. A full sequence of steps for day one, week one and month one is in the client onboarding checklist for agencies. Treat this post as the detail behind the "agree how we will work" item on that list.
When a client pushes back
Some clients will resist one of the six points. Treat it as a negotiation, not a failure. If they want faster responses than you offered, ask what is driving it and consider a priority channel at a fee. If they want unlimited revisions, offer a fixed number with a clear price for extras. If they dislike a written summary, keep it anyway, but shorten it.
What you should not do is agree to something you know you cannot deliver, just to get past the call. A promise you cannot keep is the fastest way to turn week-one goodwill into month-two resentment.
Next step
Draft your six-point summary this week and test it on a colleague. If any line takes more than two sentences to explain, shorten it. Then send it after your next kickoff call.
Ready to run it all in one place?
Projects, clients, time tracking and invoicing in one platform.