Expectation Management Protocol.

Keep the client expectations aligned with reality throughout the engagement, not just at kickoff.

One principle: no surprises

A client told early about a delay is managed. A client who discovers it at the deadline is betrayed.

The protocol

Confirm understanding at each milestone, do not assume it holds. Flag any change to timeline or scope as soon as it arises, drawing on the change log. Never let the gap between what the client expects and what they will get widen silently.

Expectation checkpoints

Milestone / trigger

What to confirm or flag

How communicated

Confirmed?

Every scope decision recorded in the Change Control Log should be communicated here as it happens, so scope and expectations never drift apart.

Your answers stay in your browser on this page and are never sent anywhere. Use Save or print to keep your copy.

Back to the guide, or start over.