# Share a report people can interpret without the original meeting

Manual worksheet; invented situation, no automatic product import.

## Owned work

- 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.

## Workflow questions

### 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.

## Job to be done

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.

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.

### Recognizable 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.

### Shortcut that fails

Exporting a sharper image does not restore the report’s scope or counting convention.

### Before

Blocked tasks: 12.

### After — invented worked answer

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.

### Conditional next moves

- If A one-time snapshot is shared: Include its observation boundary. Do not label it a period’s incoming work.
- If A trend is requested: Collect comparable observations. Changing filters can create a misleading trend.
- If The recipient needs private task details: Confirm authorized access and purpose. A context note is not permission to expose the underlying records.

### TeamBoost route — confirm account availability

- Inspect the underlying scope: Identify the relevant project tasks and state selection used for the report. Your check: The preparer checks that scope and exclusions are correct.
- Prepare a bounded report summary: Use available summary context as input, retaining observation time and scope. Your check: The summary’s completeness and counting rule need review.
- Keep the interpretation with the update: Place the context note beside the reported count in the approved reporting route. Your check: Verify receiving access before sharing sensitive work details.

### Success check

A receiver can state what was counted, when it was observed and what further evidence the next decision requires.

### Editable draft facts

- Work scope [scope]: Alpha project — Name the actual included work.
- Observation time [asof]: Wednesday 10:00 — Distinguish a snapshot from a reporting interval.
- Reported figure [finding]: 12 distinct blocked tasks — Keep count and unit together.
- Counting rule and exclusions [rule]: Declared blocked state; archived tasks excluded — Explain what entered or stayed out.
- Next decision boundary [use]: Check the current task list before a staffing decision — Name what the figure alone cannot decide.

### Draft pattern — replace every placeholder

```text
Context accompanying the report
Scope: {scope}.
As of: {asof}.
Finding: {finding}.
Rule: {rule}.
Decision boundary: {use}.
Keep this context with any shared copy of the figure.
```

### Limits

The figure is fictional. The guide prepares context, not a native export, authorized external share or validated trend.

Local text preparation only; no workspace read, task creation, send or approval. Source interfaces do not establish account availability or live feature completion.