Prepare a Status Update

Turn scattered work into one clear update that its audience can understand and act on.

Lead with what changed and what it means rather than producing a diary of activity.

1. Understand the update

Infer where possible:

• subject;
• reporting period;
• audience;
• purpose;
• destination.

Ask only when a missing detail would materially change the content.

Use an accepted previous update when it reveals the expected:

• voice;
• structure;
• depth;
• recurring commitments.

Otherwise begin with a concise draft and calibrate through feedback.

Do not force:

• traffic-light status;
• fixed templates;
• long documents

when a shorter message is more useful.

2. Reconstruct the current picture

Use approved sources that represent the work, such as:

• project systems;
• task systems;
• goals;
• metrics;
• team messages;
• meetings;
• decision documents;
• calendars;
• dashboards;
• files;
• browser tabs;
• connected apps.

Suggest a new connection only when it materially improves accuracy or coverage.

Respect the source of truth for each record.

Prefer current direct evidence.

Expose important conflicts rather than selecting whichever version is easiest to report.

When useful, compare the current state with the last accepted update.

Exclude from broadly shared drafts:

• private notes;
• personnel matters;
• sensitive hypotheses;
• unrelated work.

If coverage is incomplete, state what could not be verified.

3. Identify what the audience needs

Prioritize information that changes understanding or action:

• progress toward the intended outcome;
• meaningful changes since the previous update;
• risks;
• blockers;
• dependencies;
• timing changes;
• decisions made;
• decisions still needed;
• specific asks;
• owners;
• dates;
• next steps.

Adapt emphasis to the audience.

Leadership

Prioritize headline, consequence, decision, and ask.

Delivery Team

Prioritize ownership, dependencies, execution changes, and priorities.

Cross-functional Partners

Prioritize what affects them and by when.

Use status colors only when the organization has an accepted meaning for them or the user explicitly wants them.

Keep distinct:

• observed fact;
• plan;
• forecast;
• recommendation.

Do not invent certainty, progress, owners, or dates.

4. Draft for the actual destination

Write for the intended channel rather than filling a universal template.

A useful update commonly contains:

• clear opening;
• most important progress or change;
• risks, decisions, or asks;
• next milestone or follow-through.

Keep the main update scannable.

Place optional detail behind links or a small supporting section.

Use evidence links beside claims when recipients can access them.

Match the user's established voice without hiding bad news or overstating success.

5. Route deeper work appropriately

Use the open-loop workflow when missing ownership or contradictory records require cross-system reconciliation.

Use meeting preparation when an update surfaces a decision that needs discussion.

Use specialist workflows when domain judgment dominates, such as:

• client reporting;
• finance reporting;
• incident reporting;
• sales forecasting.

6. Review before sharing

Let the user correct:

• emphasis;
• audience assumptions;
• facts;
• tone;
• detail level.

Check:

• names;
• dates;
• metrics;
• links;
• owners;
• sensitive content.

Keep these separate:

• preparing in chat;
• creating an external draft;
• posting;
• sending;
• publishing.

Confirm audience and destination before external actions unless active scoped permission already covers them.

Verify approved sends or posts and report partial or failed delivery.

7. Make recurring updates reusable

Preserve accepted:

• sources;
• audience rules;
• voice;
• format;
• definitions;
• review behavior

when they prove durable.

A recurring update workflow may:

• check agreed sources;
• compare with the previous accepted update;
• prepare a new draft;
• surface missing or conflicting evidence.

Keep posting, sending, and record changes reviewable unless a narrower recurring action is explicitly approved.

Stop when:

• audience is unclear;
• destination is unclear;
• evidence cannot be reconciled;
• private context may reach the wrong people.