What Clients Actually Want to Know
What clients actually want to know is simple: are we on track, what comes next and when, and should I worry?
Answer those questions directly. Do not make the client interpret a task list and guess how you feel about it.
What clients actually want to know
"On track" needs a reference point. State which date, cost, scope, or expected result remains on track.
A green label alone says little. The project could be on schedule while spending more than planned, or within budget while missing a required feature. Name the part you mean.
If the plan changed, give the current position rather than comparing everything with an obsolete plan. Record when and why the baseline changed, especially when the client approved it.
What finished?
Clients use completed outcomes to judge movement. Tell them what is now delivered, approved, fixed, decided, or learned.
Avoid reporting effort as if it were a result. "We held three workshops" leaves the useful question unanswered. "The workshops produced an approved list of five requirements" explains what changed. The quantities here are examples, not a claim about customer results.
Some weeks produce evidence rather than a finished deliverable. A test that rules out a weak option is progress when you explain the decision it supports.
What happens next, and when?
Name the next visible result and its expected date. The client should know what they will receive before the next update.
Keep the promise narrow enough to be credible. A long list of possible work gives the appearance of a plan without setting a clear expectation.
When another event controls the date, name the condition. Say that you will send the draft two working days after approval, for example, rather than choosing a date that assumes immediate approval. The timing is an example and should match your actual project.
Do you need anything from me?
Put client requests under their own heading. State the action, owner, deadline, and consequence.
"Please send the signed copy by Thursday so printing can start on Friday" is clear. "Let me know your thoughts" does not explain which thoughts, who should reply, or when you need them.
Say when nothing is needed. Clients often scan updates for hidden homework, and an explicit answer lets them stop looking.
Should I worry?
Clients do not need false reassurance. They need your judgment about material risk and your plan for handling it.
Explain what may happen, how likely or uncertain it is in terms you can support, and what you are doing next. Avoid made-up percentages. If you cannot estimate likelihood, say what fact you are waiting for.
Separate a problem from its possible effect. A supplier being one day late may have no effect because the schedule has room. A missing approval may stop all work tomorrow. The consequence helps the client judge attention.
Has anything changed?
Report changes in scope, cost, timing, decisions, and assumptions. A client should not discover a changed plan by comparing this week's details with an old attachment.
Explain the reason without writing a defense. Then state the new date, amount, or boundary. If approval is required, ask for it rather than presenting the change as settled.
When nothing changed, say so briefly. The statement confirms that you checked rather than forgot.
What do you recommend?
Clients hire you for judgment as well as labor. When a decision is needed, give your recommendation and the reason.
Present alternatives only when the client can usefully choose between them. Do not send every internal option to prove that you considered it. Narrow the choice and explain differences in cost, timing, risk, or result.
Make clear whether you are asking for approval or merely informing them. Ambiguity here turns a read receipt or casual reply into a later argument about consent.
What does not answer the questions
Hours, meetings, tool names, technical jargon, and long task lists often describe your week without describing the project.
Some of that detail may belong in an invoice, audit file, or linked document. Keep it separate from the short status note. The client can open supporting material when they need depth.
Do not cite vague research about what all clients prefer. Different clients have different reporting duties and levels of expertise. Agree any special needs at the start, then keep answering the practical questions consistently.
Write for the client's next action
After reading, the client should know whether to approve something, send something, prepare for a date, or simply remain informed.
Use concrete nouns and dates. Replace "things are moving well" with the outcome and current deadline. Replace "some concerns remain" with the concern, possible effect, and next check.
Keep the note short enough to read in one sitting. If the summary cannot explain the project without a meeting, revise it before adding more detail.
The weekly update guide turns these questions into four repeatable sections. Use the questions as an editing test before you send.
Friday provides a simple place to answer them each week and keep the answers available in order.
What clients actually want to know should decide what stays in every update and what you remove.