# Leave the next shift a handoff they can act on without waking you

Manual worksheet; invented situation, no automatic product import.

## Owned work

- Identify the governing handoff version — Outgoing owner — The approved file and marked exceptions are accessible to the receiver.
- State the next permitted action — Coordinator — Correct category labels is distinguished from resending the export.
- Receive the return evidence — Incoming owner — The corrected sample or a specific blocking exception is recorded after acknowledgment.

## Working artifact

- Governing version / Approved export with marked rows / Receiver verifies access
- Permitted action / Correct category labels only / No resend before review
- Return artifact / Corrected sample or blocking exception / Receiving owner reviews actual result

## Workflow questions

### Do we need a live overlap meeting?

Sometimes, but first make the known action and boundary usable without one.

### Should the receiver simply mark the handoff done?

Only after the agreed receiving action and evidence are completed; acknowledgment alone is not correction.

### How does TeamBoost support this?

Keep the task owner, handoff context and dated work update together in the documented workflows. This does not promise native shift scheduling, time-zone automation or automatic acknowledgment.

## Job to be done

When the next owner starts after I log off, I want a usable action boundary so they can progress without guessing or waiting for a meeting.

Lagos finishes an export check after the receiving team’s workday. Two rows have wrong category labels; the export must not be resent before correction is reviewed.

### Recognizable symptoms

- The receiver gets context but no permitted next action.
- A late handoff depends on asking the sender what they meant.
- The receiver resends the file instead of correcting the known exceptions.

### Shortcut that fails

Adding more history to the handoff can still leave the next action and its limits missing.

### Before

Export checked. Please take over; details in the thread.

### After — invented worked answer

Next-shift brief: use the approved export version and inspect the two marked category rows. Correct labels only; do not resend the export. Return the corrected sample for receiving review, and record any exception that prevents that action. The receiving owner acknowledges the boundary at the start of their shift.

### Conditional next moves

- If The action and boundary are clear: Proceed with the agreed correction. The receiver need not invent scope.
- If The artifact is inaccessible or ambiguous: Return the specific handoff gap. More background text does not fix access or version uncertainty.
- If An unplanned exception appears: Record it and seek the appropriate decision. Do not widen permission to keep the shift busy.

### TeamBoost route — confirm account availability

- Make the next work owned: Identify the receiving correction task and incoming owner. Your check: Responsibility is agreed rather than inferred from time-zone coverage.
- Write the runnable handoff: Name the approved artifact, marked rows, permitted action and prohibited resend. Your check: The receiver confirms access and the governing version.
- Report the return result: Record the corrected sample or the actual blocking exception. Your check: A human receiving review decides whether the correction is accepted.

### Success check

The incoming owner can name the version, permitted action and return evidence without asking the outgoing person for the missing instruction.

### Editable draft facts

- Governing artifact [artifact]: Approved export version with two marked category rows — Use a version the receiver can access.
- Permitted next action [action]: Correct the marked category labels — Make progress concrete.
- Do-not-cross boundary [boundary]: Do not resend the export before review — State what is not authorized.
- Return evidence [return]: Corrected sample for receiving review — Define what the next owner hands back.
- Acknowledgment checkpoint [ack]: Incoming owner confirms the boundary at shift start — Agree when the receiver establishes understanding.

### Draft pattern — replace every placeholder

```text
Next-shift handoff
Use: {artifact}.
Next action: {action}.
Boundary: {boundary}.
Return: {return}.
Acknowledge: {ack}.
If the action cannot proceed, record the exact exception instead of guessing.
```

### Limits

The example does not configure shift schedules, automated handoffs or universal file access. Actual ownership and receiving routes need agreement.

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