You set client expectations by agreeing, in writing and before work begins, what you will deliver, by when, at what cost, what you need from the client and how you will both handle changes. Most project friction comes from things nobody said out loud, so the job is to say them early, record them, and revisit them at fixed points.
This guide is for agency owners, account managers and project managers. It walks through what to agree, how to word it, how to keep the client informed and what to do when scope moves.
TL;DR
- Agree scope, deliverables, timeline, cost and success measures in writing before any work starts.
- Put the client's own responsibilities (access, assets, approvals, named contacts) in the plan, with dates attached.
- Agree a communication rhythm up front: who, what, how often, through which channel.
- Decide how changes are requested, priced and approved before the first change request arrives.
- Treat onboarding as the first test of your expectations: chase missing inputs promptly and confirm everything in a handover summary.
Table of Contents
- What client expectations are and why they matter early
- The six things to agree before work starts
- Scope, deliverables and cost
- Agree what success looks like
- Put the client's responsibilities in the plan
- Agree a communication plan
- Decide how changes will be handled
- Close the loop with a handover summary
- Our perspective: onboarding is where expectations are won or lost
- Make onboarding do the work for you
- FAQ
- Sources
What client expectations are and why they matter early
Client expectations are the beliefs a client holds about what they are buying, how involved they need to be, how quickly things will happen, what it will cost and what a good result looks like. Some are written in your proposal. Many are never written anywhere. They come from past agencies, a competitor's case study or a sales call from three weeks ago.
The unwritten ones cause the damage. Gary Williams of Questas Consulting argues that most project problems come from mismatched expectations rather than poor service, and that good expectation-setting is about making the unspoken things spoken. The same piece lists the usual symptoms of vague starts: scope creep, response times that cannot be sustained, frustration over unexpected costs or delays, and teams unsure who owns what.
There is evidence that clients feel this too. A 2024 report from the Chartered Management and Consulting Europe body found that 73% of respondents named agreeing client expectations as the most important factor in delivering value, ahead of effective communication (38%) and open, trusting relationships (33%). That research looked at consultants, but an agency sells a similar thing: expert time and judgement against an outcome the client can only partly see.
For agencies that run campaigns, the stakes are commercial. Cision UK warns that without early expectation management, clients may feel shortchanged and question the value of the work, which can damage trust and even cost you the account. Its answer is a transparent kick-off conversation that covers goals, timelines and realistic outcomes based on past results and benchmarks.
The six things to agree before work starts
A useful test: if the client left tomorrow and a colleague took over, could they read your agreement and know what was promised? If not, something is still unspoken. Use this table as a starting list.
| What to agree | The question it answers | Where to record it |
|---|---|---|
| Scope and exclusions | What is included, and what is not? | Proposal or statement of work |
| Deliverables and milestones | What will the client receive, and when? | Statement of work, project plan |
| Cost and billing | What does it cost, what triggers an invoice, what counts as extra? | Proposal, contract |
| Client responsibilities | What do you need from them, and by when? | Onboarding checklist, project plan |
| Success measures | How will we both know it worked? | Brief, kick-off notes |
| Communication and change process | Who hears what, how often, and how do changes get approved? | Communication plan, contract |
The next sections take these in turn.
Scope, deliverables and cost
Start with the document that carries the commercial agreement. Professional bodies in the UK are consistent about this. The ICAEW-affiliated IFA says an engagement letter is a key document in the relationship, confirming the work, each side's obligations and the fees. ACCA says it should be provided before any work is undertaken and helps protect the firm if a misunderstanding later turns into a complaint. ICAS adds that an engagement letter should cover scope and timing, each party's responsibilities, fee basis and additional charges, and should be revisited whenever scope changes. RICS makes the same point in its guidance on setting up an initial agreement with clients: written terms help both sides understand the scope, its limits and the framework for delivery.
Marketing agencies are not bound by those accountancy and surveying rules, but the principle carries over directly. A statement of work should, according to Sprintlaw UK, define the services, deliverables, milestones, deadlines, dependencies, pricing, invoicing triggers, out-of-scope work and the acceptance process.
Two habits make this concrete:
- Write exclusions as carefully as inclusions. "Social media management" means little. "Three posts a week across two channels, one round of amends per post, no paid media management" can be checked.
- Say what counts as extra work, and how it is priced. A client who knows the day rate for out-of-scope requests rarely treats them as free.
The UK government's older but still widely used project guidance lists what a project initiation document should define: scope, constraints, risks, roles, deliverables, milestones, dependencies, costs, governance and reporting. You do not need that much paperwork for a retainer, but it is a good checklist for what a one-page brief could cover.
Agree what success looks like
"Better results" is the most dangerous phrase in agency work, because every client defines it differently. The Association for Project Management suggests asking stakeholders what success means to them, agreeing measurable and acceptance criteria, and negotiating differences against the wider outcome. It also says benefits and deliverables should be measurable and communicable from the start, with a clear view of how completion will be known.
In practice, ask three questions in the kick-off:
- What would make you say this was a good job in three months?
- Which number or outcome will you report upwards to your own boss?
- What would disappoint you, even if we hit the brief?
The third question is the one that surfaces hidden expectations. Write the answers down and send them back. Where a target depends on factors you do not control, such as search rankings or ad auction prices, state the range you can honestly stand behind and what it depends on. Cision's advice to anchor outcomes in past campaign results and industry benchmarks is a sound way to do that without over-promising.
Put the client's responsibilities in the plan
Clients tend to hear a timeline as your promise alone. In reality, most delays start with something the client has not supplied: logins, brand assets, approvals, a decision. Sprintlaw UK's advice is that a delivery date should state the client inputs and dependencies needed to keep the project moving, such as access, assets, named contacts, feedback and approvals.
So make the dependency visible:
- List every input you need, in one place, with an owner and a due date.
- State the effect of lateness plainly: "If brand assets arrive after the agreed date, the launch date moves by the same number of days."
- Name one decision-maker on the client side, and one day-to-day contact.
The Cabinet Office's Consultancy Playbook, written for government buyers of consultancy, says mobilisation should establish ways of working, clarify client and supplier roles and identify dependencies involving data and people. The same idea scales down neatly to a ten-person agency.
This is where an onboarding checklist earns its keep. Our marketing agency client onboarding checklist covers the information and files most agencies need in the first days, so the list of client responsibilities is never invented from scratch. If you also want to understand how work should pass between your own team members once the client has signed, this overview of agency workflow stages, roles and handovers is a good companion.
Chase missing inputs early and consistently
Expectations are tested in the first week. If the client promised assets by Friday and nobody mentions it on Monday, you have taught them that deadlines are soft. Send a short, friendly reminder that names the item, the date and what it unblocks. Then a second one. The point is not nagging, it is consistency: the client should see that the agreed plan is being followed by both sides.
How you collect those inputs matters too. Scattered email attachments and half-completed forms create their own confusion, which is why we cover secure client file sharing for UK agencies and how agencies run digital onboarding well in separate guides.
Agree a communication plan
A client who does not know when they will next hear from you assumes the worst. A communication plan removes the guesswork. Microsoft's project guidance recommends creating a plan that identifies stakeholders, the information they need, channels and frequency, tailored to preferences and revisited as conditions change. It gives examples such as weekly status reports for project teams and weekly summaries of schedule and cost for sponsors or customers.
APM says expectation-setting should start by identifying stakeholders early and understanding their interests and communication preferences. Its communication planning guide adds that a plan should cover scope, objectives, stakeholders, messages, channels, evaluation, sign-off protocols and review frequency, and that you should ask stakeholders whether the updates are valuable and adapt accordingly.
For an agency, a workable version fits on half a page:
- Weekly update: work completed, work in progress, next steps, anything needed from the client.
- Monthly or milestone review: progress against the success measures agreed at kick-off.
- Response times: for example, "we reply to emails within one working day". Only promise what the team can sustain.
- One channel for decisions: whatever the chat tool, decisions are confirmed by email or in the project record.
- Escalation route: who the client contacts if something is going wrong.
TeamGantt recommends a regular status report covering work completed, current and upcoming work, action items, timeline, budget and risks, and notes that telling clients bad news early prevents surprises. That habit does more for trust than any amount of polish. A client told on Tuesday that a deadline is at risk is annoyed; a client told on the deadline day is a client at risk.
If you want clients to see progress without asking, a shared view helps. Our guide on what to track in a client onboarding dashboard shows what that view can include.
Decide how changes will be handled
Change is normal. What hurts is change that happens informally. RICS describes change control as the process for altering timescale, cost or scope, and says each change should be assessed for cost, time, risk and objectives before it is accepted or rejected. It also notes the contract normally identifies who is authorised to make changes, and that once agreed they may become binding.
Atlassian suggests a simple sequence for scope creep: capture the request and its rationale, assess schedule and budget impact, decide trade-offs, record approval and update the baseline. For an agency, that becomes a short routine:
- Log the request in writing, with who asked and why.
- Estimate the time and cost, and say what moves if it goes ahead.
- Offer options: add it with a revised price, swap it for something in scope, or park it for the next phase.
- Get a written yes from the named decision-maker.
- Update the plan and send the client the revised version.
The tone matters as much as the process. "Yes, and here is what it takes" keeps the relationship warm. A flat "that's out of scope" does not, even when it is correct.
The Cabinet Office playbook also recommends regular client and supplier touchpoints to review progress, challenges and feedback, which helps manage cost, delay and scope creep. A short monthly check-in where you ask "is this still what you expected?" catches drift before it becomes a dispute.
Close the loop with a handover summary
APM describes handover as a process rather than a date, planned from the start. The first handover in any agency relationship is from sales to delivery, and it is where expectations most often leak. The client told the salesperson one thing, the account team heard another.
A good internal handover pack records what was sold, what was agreed, what the client has supplied, what is still missing and what the client said success looks like. Our guide to project handover documentation sets out what to include. Then send the client a short kick-off recap of the same points and ask them to confirm it. That confirmation is your shared record of expectations.
Our perspective: onboarding is where expectations are won or lost
We see the same pattern in agencies of every size. The proposal is clear, the contract is signed, and then the first fortnight disappears into chasing logins, brand files and answers to questions the client did not know were coming. By the time the kick-off happens, the client has already formed an impression of how the agency works, and it was formed by email reminders.
That is why we built Clientovo as a managed onboarding service rather than another form builder. A form can collect answers, but it cannot notice that a client has gone quiet or that a file is the wrong one. Our team follows up on missing inputs, organises what arrives and runs a team review, so the agency receives a structured handover with a summary and reviewed client files. Our approach is designed to help projects start faster and with more clarity.
The agency keeps control of the relationship. Clients still hear from the agency's brand, on the agency's terms, while the repetitive admin is handled for them. We think that is the most practical way to turn "set clear expectations" from a good intention into something that happens on every new client, including the busy weeks.
the author
Make onboarding do the work for you
If the steps above feel right but you do not have the time to run them for every new client, that is the gap Clientovo fills. We automate the collection of information and files, follow up on anything missing, organise materials, and deliver a structured handover pack through your agency portal, with a team review before it reaches you. You can see how managed onboarding works step by step.
Pricing is published on our site: £14 one-off per onboarding on pay as you go, or £34 per month on the monthly plan. The first client onboarding can be run on a free trial. If you are weighing a managed service against do-it-yourself forms, our comparison of client onboarding forms versus a managed service sets out the differences, and you can contact us with questions.
FAQ
How do you set expectations with a new client?
Hold a kick-off conversation and follow it with a written recap. Cover scope and exclusions, deliverables and dates, cost, what you need from the client, how success will be measured and how changes will be handled. Ask the client to confirm the recap, so everyone is working from the same record.
What are the main things clients expect from an agency?
Clients usually expect clear communication, work delivered to the agreed timeline and budget, honesty when something goes wrong, and visible progress towards the outcome they care about. The exact list differs by client, which is why you should ask what a good result looks like for them rather than assuming.
What should you do when a client's expectations are unrealistic?
Raise it early and calmly, using evidence. Point to comparable past results or benchmarks, explain what the outcome depends on, and offer a realistic target with the steps to reach it. Record the revised agreement in writing. Leaving an unrealistic target unchallenged only moves the difficult conversation to a worse moment.
How often should you update clients?
Agree it at the start and keep to it. Many teams send a short weekly update and hold a monthly or milestone review, but the right rhythm depends on the client and the work. Microsoft's guidance recommends tailoring frequency to what stakeholders need and revisiting the plan as the project changes.
Can onboarding help manage expectations?
Yes. Onboarding is the first time the client experiences your process, so a structured one shows how you work and what you need from them. Collecting inputs promptly, chasing gaps and confirming a handover summary all set the tone for the rest of the relationship.
Sources
- Managing Client Expectations, Questas Consulting
- CMCE Consultant Value report, August 2024
- How to Manage PR Client Expectations, Cision UK
- Engagement and disengagement letters, IFA
- The importance of letters of engagement, ACCA
- Engagement Letters Helpsheet, ICAS
- Setting up your initial agreement with clients, RICS
- Statement of Work Sample, Sprintlaw UK
- Guidelines for Managing Projects, UK government
- Understand What Success Is, APM
- How to Successfully Handover Projects, APM
- The Consultancy Playbook, Cabinet Office
- Best practices for project communication, Microsoft Support
- Communicate, APM stakeholder engagement
- Communication planning, APM
- Client Management for Project Managers, TeamGantt
- Change control and management, RICS
- Scope Creep in Project Management, Atlassian