Published October 12, 2026
Published October 12, 2026
Separate communication work from promise authority
An assistant can gather status, draft a clear update, send approved information, and maintain the record. That does not automatically authorize new scope, price, delivery dates, or interpretations of a dispute. Define this boundary before the first update so a helpful reply does not become an accidental commitment.
List the kinds of statements the assistant may send independently: confirmed completion, previously approved dates, meeting logistics, and requests for missing input. Everything else should route to a named decision owner.
Create one source of status
Choose the project record that governs the update. The assistant should not reconcile five private messages every time. Require workstream owners to record outcome, next milestone, blocker, and requested client action by a cutoff.
Mark the time of the snapshot. Status can change after a draft is prepared, so the send checklist should confirm material fields again when the message leaves.
Write for the client’s next decision
Lead with what changed and what the client needs to know or do. Internal activity is background unless it explains an outcome. A good update distinguishes completed work, work in progress, risks, and decisions without turning uncertainty into reassurance.
Use dates and owners for next steps. “We are working on it” is not operationally useful. “The implementation lead will confirm the migration window by Thursday” gives the client a testable expectation.
Build an approval path by risk
Routine updates can use a pre-approved structure and spot checks. Messages involving delay, cost, scope, performance concerns, or contractual language need owner review. The assistant should tag the reason for approval so the reviewer knows where judgment is required.
Set a review deadline and a safe fallback. If approval is late, the assistant may send a holding note that acknowledges the pending decision without inventing an answer.
Keep tone consistent without hiding problems
Provide examples of direct, calm language for good news, ordinary friction, and material risk. Avoid scripts that force every situation into optimism. Clients usually value a bounded problem, an owner, and a next checkpoint more than vague confidence.
Remove internal blame and speculation. State observed facts, the operational effect, and the action underway. If the cause is not verified, say so.
Record what the client received
Save the sent message or link it to the project record, including attachments and approvals. A later reviewer should be able to reconstruct what was promised without searching personal inboxes.
Log client decisions that arrive in reply. The update workflow is incomplete if the outgoing message is preserved but the client’s approval never reaches the delivery team.
Inspect the workflow monthly
Sample updates for timeliness, accuracy, missing decisions, and commitment language. Review corrections and client confusion as process evidence. A recurring correction may point to a weak source record, not careless writing.
The assistant’s role is to make communication reliable and visible. Accountability remains with the people authorized to set scope and outcomes, while the client receives a consistent view of progress and decisions.
This guide was published on October 12, 2026. For adjacent workflows, explore the Delegation Assistant blog or review the deeper evidence in Research.