CalmStatusFictional worked example

Fictional example · verify your own facts

Partial outage status update example

See a fictional partial-outage status update and customer email that name the unavailable subset and unaffected scope without inventing a cause or count.

By Electricity Studio · Published · Updated

Verified facts for this fictional scenario

  1. Affected workflow

    Invoice PDF downloads

  2. Affected scope

    EU workspaces

  3. Current state

    Invoice PDF download requests fail for EU workspaces

  4. Unaffected scope

    Invoice PDF downloads for US workspaces complete normally

  5. Unaffected workflow

    On-screen invoice viewing remains available in all regions

  6. First observed

    13:05 UTC

  7. Current update

    13:20 UTC

  8. Cause

    Not yet confirmed

  9. Next update promised

    13:40 UTC

Customer-ready messages

  1. Partial-outage update · status page

    Update 13:20 UTC: Invoice PDF downloads are failing for EU workspaces. Invoice PDF downloads for US workspaces are completing normally, and on-screen invoice viewing remains available in all regions. We first observed this at 13:05 UTC and are investigating. We have not yet confirmed the cause. We will share another update by 13:40 UTC, even if there is no material change.

  2. Partial-outage update · customer email

    Subject: Update on EU invoice PDF download failures Invoice PDF downloads are failing for EU workspaces. Invoice PDF downloads for US workspaces are completing normally, and on-screen invoice viewing remains available in all regions. We first observed this at 13:05 UTC and are investigating. We have not yet confirmed the cause. We will send another update by 13:40 UTC, even if there is no material change.

Why these drafts stay bounded

  1. The failed subset stays explicit

    The drafts name failed invoice PDF downloads for EU workspaces and normally completing downloads for US workspaces without estimating a customer count or percentage.

  2. Unaffected states stay separate

    On-screen invoice viewing remains available in every region; the drafts report that verified state without presenting it as a workaround or guarantee.

  3. Unknown stays unknown

    The cause is not yet confirmed, so neither channel adds a theory, remediation detail, or restoration estimate.

  4. Cadence stays bounded

    Both drafts promise the next communication at 13:40 UTC without turning that promise into an expected recovery time.

Draft from your verified facts.

The free acknowledgment and resolution composer runs entirely in your browser.

Open the composer →

Use the incident update checklist →