# Turn “the report is wrong” into an investigation someone can start

Manual worksheet; invented situation, no automatic product import.

## Owned work

- Identify the disputed output — Service analyst — Report identity, relevant period and expected result are recorded.
- Request the bounded comparison — Customer contact — One authorized expected-versus-observed pair names the missing region row.
- Return a useful investigation finding — Case owner — The next output is a reproduced mismatch, an explained filter or a specific remaining gap.

## Workflow questions

### What if screenshots cannot be shared?

Use an authorized redacted description naming the expected and observed result, relevant period and disputed row.

### Should we create a correction task immediately?

Track the investigation if useful, but keep implementation proposed until the evidence supports it.

### How does TeamBoost help here?

Use a documented owned task and its context for the disputed output and next reproduction action. It does not establish a native support inbox or automatic report-error detection.

## Job to be done

When a complaint has no reproducible example, I want the smallest relevant comparison so we can investigate the mismatch without guessing a fix.

A customer says a report is wrong but sends no usable comparison. Their expectation is three region rows; the observed report shows two.

### Recognizable symptoms

- A broad complaint is assigned as if its cause were known.
- The investigation asks for a whole account export instead of one relevant example.
- A corrective task is promised before the mismatch can be compared.

### Shortcut that fails

Starting implementation or collecting every account detail can add work without identifying which result is disputed.

### Before

Report wrong. Please fix the dashboard.

### After — invented worked answer

Investigation intake: identify the report and observation period, then compare the expected region rows with the observed rows. Request one redacted comparison showing the missing row; do not request an entire account export. The analyst will reproduce that bounded mismatch before proposing a correction or explaining the relevant filter.

### Conditional next moves

- If The report identity or context is missing: Ask for that bounded information. Different views can make an apparent mismatch incomparable.
- If A comparable mismatch is available: Investigate its cause. Reproduction evidence comes before a corrective commitment.
- If The result follows a relevant filter: Explain the rule and actual next choice. Not every unexpected result is a software defect.

### TeamBoost route — confirm account availability

- Own the investigation result: Track the reproduction/comparison task with the responsible analyst. Your check: Do not relabel the complaint as a confirmed software defect.
- Preserve the minimal evidence: Record the authorized expected-versus-observed pair and reporting context. Your check: Avoid unnecessary customer account contents.
- Report the finding checkpoint: Explain whether reproduction, filter clarification or another precise question is next. Your check: A human reviews the finding before any corrective commitment.

### Success check

The analyst can start a bounded comparison and the customer knows what useful finding to expect next.

### Editable draft facts

- Disputed output [report]: Regional task report — Name the output the complaint concerns.
- Observation context [context]: Current project view for the agreed report period — Keep scope and time explicit.
- Expected result [expected]: Three named region rows — Describe the concrete expectation.
- Observed result [observed]: Two region rows; one expected row absent — Use the same unit and scope.
- Investigation output and owner [next]: Analyst compares one redacted pair before proposing a correction — Define an evidence result, not a guessed fix.

### Draft pattern — replace every placeholder

```text
Reporting investigation brief
Output: {report}.
Context: {context}.
Expected: {expected}.
Observed: {observed}.
Next owned result: {next}.
Keep the cause unresolved until the comparison supports it.
```

### Limits

The sample is invented. The editor does not inspect customer records, detect defects or open support tickets.

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