# Stop a done handoff from becoming the next team’s surprise

Manual worksheet; invented situation, no automatic product import.

## Owned work

- State the sender’s completed boundary — Builder — Internal test completion is evidenced without claiming receiving acceptance.
- Perform the receiving check — Receiving owner — The actual delivered file is opened and required fields inspected.
- Retain correction responsibility — Handoff coordinator — The missing field has an owner and a corrected-file receiving check.

## Working artifact

- Sender verification / Internal implementation result / Do not extend to receiver acceptance
- Receiving action / Open the delivered version and check required fields / Return any specific gap
- Closure boundary / Receiver confirms corrected file supports agreed use / Keep artifact and verdict together

## Workflow questions

### Is the sender’s internal test worthless?

No. It is useful evidence for that boundary; it does not prove the receiver can use the delivered file.

### Should we change the official task status vocabulary?

Use the states available in your account and explain the receiving boundary in a note rather than inventing a native state.

### How does TeamBoost support this handoff?

Documented task state, ownership and comments let you keep the sender’s evidence and receiver’s request tied to the work. Receiving acceptance is still a human decision.

## Job to be done

When a sender says done but the receiver has not tried the result, I want the completion boundary stated so the next team knows what it can safely use.

A builder reports an export done after an internal test. The receiver has not opened the delivered file and later finds a missing field.

### Recognizable symptoms

- The sender’s internal completion is read as receiving acceptance.
- The receiving action is implicit rather than requested.
- A file arrives without a named owner for corrections.

### Shortcut that fails

A stronger done label cannot replace the receiver opening the actual delivered artifact.

### Before

Export done. You can use it now.

### After — invented worked answer

Handoff boundary: implementation was checked internally; receiving acceptance is pending. Please open the delivered file and verify the required fields before use. The missing field remains owned by the builder for correction. Close the handoff only when the receiver checks the corrected file and acknowledges the agreed use.

### Conditional next moves

- If Only internal checks passed: Request receiving verification. A delivery label is not proof of usability in the receiving context.
- If The receiver finds a concrete gap: Keep correction owned. The handoff remains open for the agreed missing condition.
- If Receiving use is demonstrated: Record the accepted boundary. Retain the artifact/version that supports the conclusion.

### TeamBoost route — confirm account availability

- Describe the actual stage: Keep the delivery work identified and its state accompanied by a boundary note. Your check: Use the actual states available in the account.
- Request the receiving check: Name the delivered version, required fields and receiver’s next action. Your check: The receiver opens the actual artifact rather than relying on its label.
- Keep the correction visible: State the missing field and next receiving review in the update. Your check: Close only after the agreed receiving evidence exists.

### Success check

The receiver knows which boundary passed, which artifact to inspect and who owns the gap it finds.

### Editable draft facts

- What the sender actually checked [sender]: Internal implementation test — Do not expand this into receiving acceptance.
- Delivered artifact or version [artifact]: Export file v2 — Name what the receiver will inspect.
- Receiving action [receiver]: Open the file and check required fields — Make the next action usable.
- Known gap and owner [gap]: Missing field; builder owns correction — Keep the gap attached to an owner.
- Receiving closure check [close]: Receiver checks the corrected file and confirms agreed use — Describe the actual closure proof.

### Draft pattern — replace every placeholder

```text
Completion-boundary handoff
Verified by sender: {sender}.
Artifact for receiving review: {artifact}.
Receiver action: {receiver}.
Open gap: {gap}.
Closure evidence: {close}.
Do not treat sender completion as receiving acceptance without that check.
```

### Limits

The file and missing field are illustrative. Task labels do not certify external artifacts or receiving readiness.

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