{
  "example_kind": "invented job and manual worksheet",
  "slug": "report-export-missing-context",
  "title": "Share a report people can interpret without the original meeting",
  "layout": "dispatch",
  "story": "When a report leaves the dashboard where it was created, I want its meaning to travel with it so another reader can use the figures correctly.",
  "problem": "A screenshot says twelve blocked tasks. It omits that only the Alpha project is shown, the view is a Wednesday snapshot and archived tasks were excluded.",
  "symptoms": [
    "The recipient reads a project snapshot as a whole-company total.",
    "A screenshot loses filters that gave the number meaning.",
    "A historic count is discussed as if it were current."
  ],
  "failed_workaround": "Exporting a sharper image does not restore the report’s scope or counting convention.",
  "before": "Blocked tasks: 12.",
  "after": "Report context: Alpha project, Wednesday 10:00 snapshot. Twelve distinct tasks matched the declared blocked-status rule; archived tasks were excluded. This is a snapshot, not the number of new blockers this week. Ask the Alpha owner for the current task list before making a staffing decision.",
  "success_check": "A receiver can state what was counted, when it was observed and what further evidence the next decision requires.",
  "choices": [
    [
      "A one-time snapshot is shared",
      "Include its observation boundary",
      "Do not label it a period’s incoming work."
    ],
    [
      "A trend is requested",
      "Collect comparable observations",
      "Changing filters can create a misleading trend."
    ],
    [
      "The recipient needs private task details",
      "Confirm authorized access and purpose",
      "A context note is not permission to expose the underlying records."
    ]
  ],
  "route": [
    {
      "label": "Inspect the underlying scope",
      "capability": "task-record",
      "action": "Identify the relevant project tasks and state selection used for the report.",
      "human_check": "The preparer checks that scope and exclusions are correct."
    },
    {
      "label": "Prepare a bounded report summary",
      "capability": "report-summary",
      "action": "Use available summary context as input, retaining observation time and scope.",
      "human_check": "The summary’s completeness and counting rule need review."
    },
    {
      "label": "Keep the interpretation with the update",
      "capability": "daily-report",
      "action": "Place the context note beside the reported count in the approved reporting route.",
      "human_check": "Verify receiving access before sharing sensitive work details."
    }
  ],
  "editor": {
    "heading": "Prepare a useful update",
    "fields": [
      {
        "key": "scope",
        "label": "Work scope",
        "example": "Alpha project",
        "help": "Name the actual included work."
      },
      {
        "key": "asof",
        "label": "Observation time",
        "example": "Wednesday 10:00",
        "help": "Distinguish a snapshot from a reporting interval."
      },
      {
        "key": "finding",
        "label": "Reported figure",
        "example": "12 distinct blocked tasks",
        "help": "Keep count and unit together."
      },
      {
        "key": "rule",
        "label": "Counting rule and exclusions",
        "example": "Declared blocked state; archived tasks excluded",
        "help": "Explain what entered or stayed out."
      },
      {
        "key": "use",
        "label": "Next decision boundary",
        "example": "Check the current task list before a staffing decision",
        "help": "Name what the figure alone cannot decide."
      }
    ],
    "template": "Context accompanying the report\nScope: {scope}.\nAs of: {asof}.\nFinding: {finding}.\nRule: {rule}.\nDecision boundary: {use}.\nKeep this context with any shared copy of the figure."
  },
  "limitations": "The figure is fictional. The guide prepares context, not a native export, authorized external share or validated trend.",
  "tasks": [
    [
      "Recover the view definition",
      "Report preparer",
      "Project, snapshot time, blocked rule and archived exclusion are known."
    ],
    [
      "Attach the interpretation note",
      "Coordinator",
      "The image and note remain together in the approved share packet."
    ],
    [
      "Check the receiving question",
      "Report owner",
      "The recipient can distinguish a snapshot count from arrivals during a period."
    ]
  ],
  "faqs": [
    [
      "Does everyone need access to the original dashboard?",
      "Not always, but a share packet still needs enough authorized evidence and context for its intended decision."
    ],
    [
      "Is the screenshot a weekly trend?",
      "Not without comparable observations and a defined time basis. This example contains one snapshot."
    ],
    [
      "How can TeamBoost support the share packet?",
      "Its documented task/report records provide source context for a reviewed summary. The recipient-facing note and sharing permission remain human responsibilities; this guide does not verify a native export or external-sharing feature."
    ]
  ]
}