# Make the evidence usable before asking someone to approve the work

Manual worksheet; invented situation, no automatic product import.

## Owned work

- Locate the blocked evidence route — Receiver — The task opens but the correct test report does not.
- Arrange approved access — Document owner — The intended receiving group has an authorized route to the evidence.
- Verify the receiving check — Review coordinator — A receiver opens the correct version before the review request resumes.

## Workflow questions

### Does seeing the task prove the attachment is accessible?

No. A linked system can have a separate access boundary.

### Should I make the link public?

Use the approved sharing process and actual receiving need; this worksheet cannot authorize broader exposure.

### Can TeamBoost fix permissions on another service?

No such universal capability is established. Use the task context to coordinate the document owner and record the checked route.

## Job to be done

When a reviewer can open the task but not its evidence, I want an approved access route so their verdict is based on what they can actually inspect.

The receiving lead can read the work item but the linked test report returns access denied. The task is already marked ready for approval.

### Recognizable symptoms

- Task visibility is treated as permission to every linked document.
- Review reminders arrive before the receiver can inspect evidence.
- A public-link shortcut is proposed without checking the content or sharing rules.

### Shortcut that fails

Sending another approval reminder cannot repair access; opening a document to everyone may create a different problem.

### Before

Please approve the task. The evidence link is already in the description.

### After — invented worked answer

Receiving-access request: the task is visible, but the test report is not. The document owner will arrange the approved receiving route. A representative receiver must open the correct report before approval is requested again. Evidence access enables review; it does not itself approve the result.

### Conditional next moves

- If Task opens but evidence does not: Coordinate the document access owner. Task visibility does not imply external-file access.
- If Evidence opens but is the wrong version: Resolve the governing artifact. Accessible evidence can still be irrelevant.
- If Correct evidence is inspectable: Resume the receiving review. Keep access repair distinct from acceptance.

### TeamBoost route — confirm account availability

- Keep the review task identifiable: Retain the receiving review work rather than marking it approved. Your check: Evidence visibility and result acceptance are separate states of the work.
- Record the access gap: Name the inaccessible artifact and the approved route to arrange. Your check: The document owner handles the actual permissions.
- Report the repaired review path: State when receiving access was verified and what review remains. Your check: Opening a file is not a passing verdict.

### Success check

The intended receiver can inspect the right evidence through an approved route before being asked for a verdict.

### Editable draft facts

- Evidence needed [artifact]: Correct test report version — Name the specific artifact.
- Intended receiver [receiver]: Receiving lead — Use the approved audience.
- Access problem [gap]: Task visible; report access denied — Separate the two boundaries.
- Access route owner [owner]: Document owner — Choose someone who can arrange the route.
- Receiving proof [proof]: Representative receiver opens the correct report — Verify through the actual receiving context.

### Draft pattern — replace every placeholder

```text
Evidence-access request
Artifact: {artifact}.
Intended receiver: {receiver}.
Observed gap: {gap}.
Route owner: {owner}.
Access proof needed: {proof}.
After access works, request the separate review verdict.
```

### Limits

The page does not grant sharing permission, change document access or establish a native attachment-hosting feature.

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