The client wants daily updates. Is that reasonable?
Communication frequency mismatchAgree an update cadence based on uncertainty, decision needs, and cost. A concise exception update may satisfy the need without forcing the team into repeated manual reporting.
What to do now
- Ask what concern drives the request
- Define the useful update content
- Agree a proportionate cadence and channel
- Review the arrangement after conditions stabilize
When to escalate
Escalate when
The requested reporting consumes critical delivery capacity or conceals a trust issue.
Who decides
The stakeholder decision owner and project sponsor
Example
During cutover the client receives brief daily readiness updates, returning to weekly reporting afterward.
Mistake to avoid
Rejecting the request without understanding why confidence is low.
Prevent a repeat
Check stakeholder understanding at important decisions rather than counting messages sent.
Suggested ApprovedFlow setup
- Projects
- Documents
- Approvals
Keep stakeholder decisions and supporting records with the project and assign follow-up actions to named owners. See the platform
Related cases
- The team uses too many communication channels. How do we simplify?Fragmented project communication
- Different audiences need different project messages. How do we avoid inconsistency?Inconsistent communication views
- The client wants every request treated as a defect. How do we distinguish changes?Defect-versus-change ambiguity
- The resource plan is monthly, but tasks change daily. How should they connect?Planning-granularity mismatch