Clients rarely get upset because something went wrong. They get upset because something went differently than what they expected — and no one told them in advance. Setting expectations well is one of the highest-leverage communication skills in client-facing work, and it's learnable.

Be specific, not reassuring

"We'll get this done soon" feels comforting to say, but it sets no real expectation. A client hears "soon" and fills in their own definition — which is rarely the same as yours.

Instead: "You'll have the first draft by Thursday at 5pm" gives the client something concrete to hold you to, and gives you something concrete to hold yourself to.

Say what's included — and what isn't

Scope creep usually isn't malicious. It happens because "included" was never clearly defined, so the client reasonably assumes more falls under the original agreement than it does.

  • Put scope in writing, even for informal engagements
  • Name a few things explicitly out of scope, not just what's in
  • Revisit scope out loud whenever a new request comes in

Flag risk early, not after it happens

If a timeline is at risk, the version of you that says so on day 3 looks far more credible than the version that stays quiet until day 10. Early warning, even about bad news, builds trust. Silence until the deadline is missed destroys it.

Confirm understanding, don't just deliver information

After a scope or timeline conversation, a short written summary — even two lines in an email — closes the loop and prevents the classic "that's not what I thought we agreed" moment weeks later.

Clients don't expect perfection. They expect to know, clearly and early, what to expect.

Set expectations this way consistently, and something shifts: clients start trusting your word without needing to double-check it. That trust is what makes every future conversation — including the hard ones — considerably easier.