{
  "status": "Illustrative acceptance plan, not an executable test suite or observed production result",
  "topic": "Customer-facing incident communications",
  "date": "2026-11-04",
  "sourceArticle": "https://aptixlabs.com/insights/saas-incident-communication-template",
  "setup": [
    "Use synthetic accounts and records",
    "Record the environment and implementation version",
    "Agree the expected product contract before testing"
  ],
  "reviewSequence": [
    "Define incident stages and an accountable communicator",
    "Describe user impact before internal architecture",
    "Verify recovery before announcing resolution"
  ],
  "cases": [
    {
      "id": "1",
      "condition": "Cause is still unknown",
      "expectedBehavior": "The message does not present a hypothesis as fact",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "2",
      "condition": "Only some workflows recover",
      "expectedBehavior": "The update states partial recovery",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "3",
      "condition": "A workaround is suggested",
      "expectedBehavior": "Its affected path has been tested",
      "observedBehavior": null,
      "status": "not_run"
    }
  ],
  "tradeoff": "Frequent updates can become noisy if they repeat no useful information. A predictable update time and honest \u201cstill investigating\u201d statement are often better than speculative detail."
}