Most guides on how to deal with difficult clients start with the conversation. The conversation matters, but most problems with clients start earlier, when the scope was vague or the client could not see progress. This guide covers the common causes, how to manage client expectations from the first day, how to handle scope creep with a simple change rule, word-for-word scripts for six hard moments, and a weekly routine on a shared kanban board.
Why clients become difficult
A client who seems difficult usually has a reason that you can find and fix. These are the causes that come up most often:
- Unclear scope. “A new homepage” means a template change to you and a full redesign to the client.
- No visible progress. A week without updates looks like a week without work.
- New requests with no trade-off. Each small addition is accepted, and the deadline slips without anyone deciding it should.
- Lost decisions. An approval given on a call is disputed a month later because nobody wrote it down.
- Hidden waiting time. The project is stuck waiting for the client’s content, but the client sees only that you are late.
Research from the Project Management Institute (PMI) shows how common the first and third causes are. PMI’s 2018 Pulse of the Profession survey found that 52 percent of projects completed in the previous 12 months had scope creep or uncontrolled changes to scope, up from 43 percent five years earlier. A 2013 PMI report on communications estimated that ineffective communications cause 56 percent of the budget at risk on a project.
Managing client expectations before work starts
The best time to prevent a dispute is before the first invoice. Agree these five points in writing, in the proposal or contract, and repeat them at the kickoff call:
- What is included. List each deliverable with a short acceptance test, such as “Contact page works on mobile and sends to the info@ address.”
- What is not included. Name the likely extras: copywriting, stock photos, extra revision rounds, new pages.
- How changes work. A new request is estimated first and starts only after the client approves the cost and the new date.
- How you update the client. For example, a written update every Friday and a board the client can check at any time.
- Who approves. One named person on the client side signs off each deliverable.
With a “not included” list, the client can see before signing that an item they assumed was part of the work is not.
Scope creep: turn requests into decisions
PMI’s PM Network separates two things that clients often treat as one. In a 2012 article on preventing scope creep, consultant Trevor K. Nelson describes scope creep as work done outside the agreed scope without approval and without an agreement for more payment. A scope change is a change that the project manager or sponsor has acknowledged. He names the controls that prevent creep: a clear scope statement, a contract, and a change control process.
A change control process for a small agency or a freelancer can be four steps:
- Write the request down as its own item, separate from the agreed work.
- Estimate the effort, the cost and the effect on the delivery date.
- Send the client the options: add it with the new cost and date, swap it for something of similar size, or move it to a later phase.
- Start work only after the client picks an option in writing.
The process does not mean saying no. Most requests are reasonable, and many are paid work.
How to deal with difficult clients: six scripts
Each script below names the fact, refers to what was agreed, and offers a next step. Adjust the words to your own voice.
A new request that is out of scope
“Thanks, that’s a good idea. It wasn’t part of the scope we agreed on 3 March, so I’ve added it to the board as a separate request. It’s about two days of work, which adds $1,200 and moves launch to the 24th. Would you like to add it now, swap it for the blog page, or keep it for phase two?”
The client is late with content or feedback
“We’re ready for the product photos, and the homepage is waiting on them. I’ve marked the card ‘Waiting on client’ on the board so it’s easy to find. If they arrive by Wednesday, we can keep the launch date. After that, each day of delay moves launch by a day.”
“This isn’t what I asked for”
“Let’s check it against the brief together. The card for this page says a three-column layout with the pricing table first, and you approved the mockup on the 12th. Which parts don’t match what you expected? If it’s a new direction, I’ll estimate it as a change.”
An angry email
Reply after you have read the whole message twice, and keep the reply short:
“I understand you’re frustrated about the delay, and I want to fix it. Here is where things stand: two pages are done, one is waiting on your copy, and one is in progress. Can we take 15 minutes tomorrow to agree on the plan for the last two?”
A demand for a faster deadline
“We can deliver by the 10th if we drop the gallery and the second contact form from this phase, or we can keep everything and deliver on the 17th. Which matters more to you?”
A late payment
“Invoice 1042 for the design phase was due on the 1st. I’ve paused new work on the build phase until it’s settled, as set out in our agreement. Everything is saved, and we can restart the day payment arrives.”
When a disagreement turns into a dispute
When a disagreement becomes a dispute, use the method that the Harvard Program on Negotiation teaches. Its summary of Getting to Yes lists the first three principles of principled negotiation: separate the people from the problem, focus on interests rather than positions, and work together on options that satisfy both sides.
For a client project, that means four steps:
- Separate the person from the problem. Talk about the card, the date and the brief, not about the client’s attitude.
- Ask about the interest behind the position. “We need it by Friday” often means “my boss is presenting on Monday.” A demo build by Friday may meet that need.
- Offer two or three options, each with a cost and a date.
- Write down the result where both of you can see it.
If the same problems repeat after you have raised them directly, you may decide to end the work. Typical reasons are unpaid invoices, ignored scope agreements and disrespect toward your team. Follow the notice and handover terms in your contract, and deliver what has been paid for.
A board routine for client communication
A shared board turns the habits above into a routine. In KanbanWP, the Client template creates five stages and three labels:
- Stages: Backlog, In Progress, In Review, Approved and Done.
- Labels: Feedback, Revision and Approved.
Add two labels of your own from the Labels button: “Waiting on client” and “Change request”. Then use the board this way:
- One card per deliverable, with the acceptance test in the description and a due date. Add a checklist for the parts of the deliverable.
- New requests go into Backlog with the Change request label. A card moves to In Progress only after the client approves the cost and the date.
- Waiting time is shown with the Waiting on client label, so the reason for a delay is on the card.
- Decisions are written as comments on the card, with the date: “Agreed on call 14 May: logo stays, footer links change.”
- Private notes, such as pricing thoughts, go into comments marked Internal. Admins and members see those comments, and clients do not. See task comments.
Show the board to the client on a page of your site with the client portal. Add clients with the Client role. Clients can read the board and every comment that is not internal, and they can comment, but they cannot edit tasks. A client can then confirm a decision on the card where it was made.
A worked example
A small agency is building a five-page site. On Monday the client emails three new ideas. The project lead creates three cards in Backlog, labels each one Change request, and writes an estimate in each description. On Tuesday the client approves one, which moves to In Progress with a new due date, and declines two, which are archived with a comment saying why.
On Thursday the About page is ready for approval, so it moves to In Review. The photos for the Services page are late, so that card gets the Waiting on client label. Friday’s written update copies the facts from the board: two cards approved, one in review, and one waiting on photos since Wednesday.
The weekly review
Set aside 15 minutes each week:
- Filter the board by Due: Overdue, then by the Waiting on client label, and act on each card. See filtering tasks.
- Check that every card in Backlog with the Change request label has an estimate and a decision date.
- Send the written update, with links to cards in In Review.
- Save the filters you use every week as a saved view.
A checklist for starting a client project
- Scope with deliverables and acceptance tests, signed
- “Not included” list in the proposal
- Change rule agreed: estimate first, approval in writing
- Update schedule and one named approver
- Board created from the Client template, with Waiting on client and Change request labels
- Client added as a Viewer, and the portal page sent
- First review date set
To set up the board, follow your first board. For the ground rules a team should agree before work starts, read what isn’t on the board.
Frequently asked questions
How do you deal with difficult clients?
Find the cause first, which is usually unclear scope, missing updates or a lost decision. Then point to what was agreed in writing, offer options with a cost and a date, and keep every decision in one shared place.
How do you manage client expectations?
Write down what is included and what is not before work starts, agree how often you will send updates and who approves work, and show progress where the client can check it without asking.
What is scope creep?
Scope creep is work added outside the agreed scope without approval and without an agreement on extra payment. A scope change is the same request after it has been agreed through a change process.
When should you stop working with a difficult client?
Consider ending the work when the client repeatedly ignores the written agreement, refuses to pay for agreed changes, or treats your team with disrespect after you have raised it directly. Finish or hand over the current deliverable as your contract requires.