CalmStatusFictional worked example

Fictional example · verify your own facts

Degraded performance status update example

See a fictional degraded-performance status update and customer email that describe a slow-but-available workflow without inventing a cause.

By Electricity Studio · Published · Updated

Verified facts for this fictional scenario

  1. Affected workflow

    Dashboard loading

  2. Affected scope

    US workspaces

  3. Current state

    Dashboards are loading more slowly than normal; requests still complete

  4. Unaffected workflow

    API requests continue to process normally

  5. First observed

    09:10 UTC

  6. Current update

    09:25 UTC

  7. Cause

    Not yet confirmed

  8. Next update promised

    09:45 UTC

Customer-ready messages

  1. Degraded-performance update · status page

    Update 09:25 UTC: Dashboards are loading more slowly than normal for US workspaces. Requests still complete, and API requests continue to process normally. We first observed this at 09:10 UTC and are investigating. We have not yet confirmed the cause. We will share another update by 09:45 UTC, even if there is no material change.

  2. Degraded-performance update · customer email

    Subject: Update on slower dashboard loading Dashboards are loading more slowly than normal for US workspaces. Requests still complete, and API requests continue to process normally. We first observed this at 09:10 UTC and are investigating. We have not yet confirmed the cause. We will send another update by 09:45 UTC, even if there is no material change.

Why these drafts stay bounded

  1. Degradation is not an outage

    The drafts say that dashboard requests still complete instead of describing the workflow as unavailable.

  2. Impact and scope stay concrete

    The slower dashboard workflow, US workspace scope, and normally processing API requests stay separate without a customer count, performance percentage, or severity label.

  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 09:45 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 →