Async Update Facts Card

Use with Writing Async Status Updates With AI, Without the Spin.

Step 1: State your real status first (before using AI)

• Shipped / done: ___________________________________________________
• Blocked on (or “nothing”): ________________________________________
• Next: ______________________________________________________________
• Honest confidence (on track / at risk / blocked — need X by [date]): ____

Step 2: Draft instruction for AI

“Turn this status into a clean async update. Keep the tone plain and factual. Do not add phrases implying more progress or confidence than what I stated. If something is blocked, keep that as the headline, not a footnote.”

Step 3: Spin-word check

• “Great progress” / “crushing it” — does this match what actually shipped?
• “Nearly there” / “almost done” — is this a specific estimate or vague reassurance?
• “On track” — is a real blocker mentioned clearly, if one exists?
• “Should be fine” — is this my honest confidence, or a hope?

Step 4: Escalation trigger

• This is the 3rd+ consecutive update at “at risk” or “blocked” on this item — raise it directly (1:1 or DM) instead of repeating the same status line.

Before sending

• The real status is stated first and plainly, not buried after unrelated positive framing.
• Nothing in the update would make a reader plan differently than my actual status justifies.