The Update Your Client Forwards to Their Boss
A client update they can forward should make sense to a reader who missed every call and has little knowledge of the daily work.
Give that reader the outcome, current deadline, cost or scope change, decision, and next action without making your client add an explanation.
Writing a client update they can forward
Your direct client knows the people, files, and recent discussion. Their boss may know only the project name and approved budget.
Write one short line of context when it changes how the update is understood. Name the deliverable and its purpose rather than referring to "phase two" or "the latest version."
Do not repeat the full brief every week. Include enough context to explain the current fact. A sentence such as "The new booking page replaces the phone request process" may be all a second reader needs.
Lead with the current position
A forwarded update should reveal quickly whether the work is on track. State the relevant date, scope, or cost rather than using a general status label.
For example, you might write: "The approved homepage is ready for development, and the 30 September delivery date remains unchanged." The date is a hypothetical example, not a customer result.
If the project is not on track, say what moved and what you recommend. Do not place the change at the end after several paragraphs of completed tasks.
Name outcomes instead of effort
A senior reader rarely needs a list of meetings, hours, or internal tasks. They need to know what became possible, approved, delivered, or less risky.
Translate activity into its consequence. "We completed accessibility testing" becomes useful when you add what the test found and whether the finding affects launch.
Keep technical terms only when the reader needs them for a decision. Plain words reduce the chance that your client has to translate your update before forwarding it.
Make decisions explicit
Record what was decided, who made the decision when relevant, and what it changes. Separate a proposal from an approval.
"We discussed moving launch" is not a decision. "On 11 September, the client approved moving launch to 25 September with no change to scope" is clear. The dates are examples.
If formal approval is still needed, state that plainly and identify the approver. A forwarded message can then reach the right person without a second summary.
Put costs and deadlines in plain view
Do not hide a changed cost or deadline inside background detail. Give the previous position, the new position, and the reason.
Distinguish estimates from approved amounts. Distinguish a target date from a committed deadline. The labels prevent a secondhand reader from treating a working number as a promise.
When no cost or deadline changed, a short statement can reassure the reader. Use it only when you have checked both facts.
Give requests an owner and date
Your direct client may forward an update because they need help from their boss. Make the requested action easy to find.
Name the choice or item, the person responsible, the date needed, and the consequence of delay. Avoid "please advise" and "thoughts welcome," which require another conversation to discover the actual request.
If no action is needed, say so. A senior reader can then read for information without wondering whether a task was buried in the message.
Write a useful subject line
The subject should identify the project, reporting date, and material change when there is one. A subject such as "Harbor site update, 13 September, approval needed" is easier to forward than "Quick update." The project and date are examples.
Keep urgent wording for facts that need prompt action. If every weekly email says urgent, the word stops helping.
The body should still contain the full request. Subject lines are often shortened, edited, or separated from attachments when messages are forwarded.
Keep links and attachments understandable
Name what each link contains and whether the reader needs to open it. "Review the final homepage copy" is better than "see here."
Check that intended recipients can access the file. A link to your internal project tool may fail for the second reader or ask them to create an account.
Do not put the only important fact inside an attachment. The update should state the decision, amount, or deadline, while the attachment supplies detail.
Avoid private or casual detail
Write as though the client may forward the message, because they often need to report upward or across their company. Remove jokes about stakeholders, internal complaints, and personal detail that does not affect delivery.
Do not make the update bland or dishonest. State problems clearly, but describe facts and actions rather than assigning blame.
Use a separate, suitable channel for sensitive legal, personal, or security information. Forwardable does not mean suitable for unrestricted circulation.
Use a repeatable structure
Start with the current position. Follow with completed outcomes, next work, client requests, and changes to cost, scope, dates, decisions, or risk.
Keep the update under 200 words when possible. A senior reader should be able to understand it quickly, while your direct client should be able to forward it without rewriting.
Read the draft once as the secondhand reader. Remove unexplained names, internal labels, relative dates, and references to conversations they did not attend.
The weekly client update template provides the base structure. Add only the context needed for the update to survive outside the original inbox.
Friday can give your client a clean email to forward and a stable page to share when their boss wants the earlier history.
A client update they can forward saves the client from rewriting your work for each new reader.