# Fix a stale AI status report before it sends the team backwards

Manual worksheet; invented situation, no automatic product import.

## Owned work

- Read the change after the summary — Update reviewer — Schema approval time and attachment match the actual export task.
- Keep unresolved conditions separate — Delivery owner — Test-account access remains open despite the schema being available.
- Publish a reviewed correction — Reporting lead — The corrected note names its observation time, remaining owner and next check.

## Workflow questions

### Should I ask AI to rewrite it immediately?

First provide the corrected task facts and ask it to preserve unresolved conditions; review the output before sharing.

### Does one resolved blocker mean the task is unblocked?

Only if all required blocking conditions are resolved. The access condition in this case remains open.

### How does TeamBoost help?

Its documented task updates and daily-report records provide places to keep the correction tied to the work. AI assistance is publicly positioned; verify the functions enabled for your account.

## Job to be done

When an AI summary repeats an old blocker, I want to reconcile it with current task evidence so people act on the work that still needs help.

An overnight summary says the export is blocked by a missing schema. A later task comment attaches the approved schema, but test-account access is still missing. The report was prepared at 09:00, before the 09:10 evidence, and has already reached the morning review group.

### Recognizable symptoms

- Yesterday’s summary is treated as the latest observation.
- A resolved issue keeps receiving escalation messages.
- Removing one blocker risks making the entire task look ready.

### Shortcut that fails

Regenerating a prettier summary from the same old context can repeat the mistake. Reconcile the changed facts first.

### Before

Export blocked: schema missing. Please chase the schema owner again.

### After — invented worked answer

Correction to the 09:00 report, checked Wednesday 09:30: the schema claim is superseded by the approved schema in the 09:10 task note. Test-account access is still missing; that condition is unchanged. Send this correction to the morning review group that received the old report, retaining the prior observation time and the changed source. The access owner should confirm an approved account by 12:00 or name the next check. This corrects a stale report; it does not close the export task.

### Conditional next moves

- If Later evidence resolves one condition: Correct that claim and retain the rest. A newer timestamp does not resolve unrelated blockers.
- If Later note is ambiguous: Ask for the missing confirmation. Do not turn an attachment name into approval evidence.
- If All required conditions are evidenced: Update the ready-for-review boundary. Receiving acceptance may still remain.

### TeamBoost route — confirm account availability

- Read the latest task context: Compare the later task note with the report’s observation time. Your check: A person confirms the evidence addresses the same task and condition.
- Correct the work update: Record the 09:00 report observation, the later 09:10 source and the 09:30 correction together. Share the correction with the original morning review audience through an approved route. Your check: Do not treat a rewritten note as proof that access works.
- Retain the next action: Keep the access work owned and visible in the task record. Your check: The owner supplies receiving evidence before closure.

### Success check

The original report audience can distinguish the superseded observation, later resolving evidence and unchanged access need without erasing the reporting trail.

### Editable draft facts

- Old report time → correction time [asof]: 09:00 report → checked Wednesday 09:30 — Keep the old observation and the later check distinguishable.
- Resolved condition and evidence [resolved]: Schema approved in the 09:10 task note — Name what changed and its source.
- Still-open condition [open]: Approved test-account access missing — Retain independent conditions.
- Next responsible role [owner]: Access owner — Choose the person who can change the condition.
- Correction audience and next checkpoint [check]: Morning review group receives correction; access owner replies by 12:00 — Reach the people who received the superseded report and keep the remaining check owned.

### Draft pattern — replace every placeholder

```text
Correction record — {asof}
Changed claim and later source: {resolved}.
Unchanged open condition: {open}.
Still needed from {owner}.
Correction recipients and next check: {check}.
Retain the old observation with this correction; do not present a corrected report as task closure.
```

### Limits

The example is invented. An AI summary cannot validate evidence or exercise product permissions; current task facts and account functions need confirmation.

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