# Fit a handoff inside both teams' overlap

Illustrative planning brief; no automatic product import.

Synthetic planning case: The sending team can attend 13:00–15:00 UTC and the receiving team 14:30–16:00 UTC. The required joint handoff is 45 minutes.

## Decision

The intersection is 14:30–15:00 UTC, only thirty minutes. The proposed 45-minute joint handoff does not fit; move a window or revise the verified handoff protocol.

## Owned work

- Confirm one time basis
  - Owner role: Coordinator
  - Acceptance evidence: Both availability windows refer to the same UTC day.
- Inspect the intersection
  - Owner role: Handoff owner
  - Acceptance evidence: The actual shared window is thirty minutes, not either team’s full availability.
- Agree a feasible session
  - Owner role: Receiving lead
  - Acceptance evidence: The full 45-minute requirement fits a changed window or an approved revised protocol.

## Workflow

1. Confirm one time basis. Check: Both availability windows refer to the same UTC day.
2. Inspect the intersection. Check: The actual shared window is thirty minutes, not either team’s full availability.
3. Agree a feasible session. Check: The full 45-minute requirement fits a changed window or an approved revised protocol.

## Judgment

Real calendars may have exceptions. This example uses fixed UTC windows on one day and a stated continuous requirement.


## Filled manual planning note

The intersection is 14:30–15:00 UTC, only thirty minutes. The proposed 45-minute joint handoff does not fit; move a window or revise the verified handoff protocol. Overlap begins at the later start, 14:30, and ends at the earlier finish, 15:00. Thirty minutes is fifteen short of the stated requirement. Real calendars may have exceptions. This example uses fixed UTC windows on one day and a stated continuous requirement.


## Workflow questions

### Can the sender’s two hours count as joint availability?

No. Only the intersection is available to both roles.

### Would an asynchronous packet solve it automatically?

No. The receiver must agree that route and its acceptance evidence; the worksheet does not waive the joint requirement.

## Product connection

Use the owned checks and downloaded brief to discuss this planning decision alongside your TeamBoostAI tasks. Confirm available fields, roles and account features separately. The example is manual; it does not calculate live analytics, create work or run an experiment in the product.

Confirm account availability before adopting this manual outline.

## Original worked case

Synthetic records, manual planning only. No account import or live analytics.

### Inspect the invented case records

Team or requirement | UTC window | Duration
--- | --- | ---
Sending team | 13:00–15:00 | 120 minutes
Receiving team | 14:30–16:00 | 90 minutes
Shared intersection | 14:30–15:00 | 30 minutes
Required joint review | One continuous session | 45 minutes

### Reasoning

Overlap begins at the later start, 14:30, and ends at the earlier finish, 15:00. Thirty minutes is fifteen short of the stated requirement.

### Bounded result

The intersection is 14:30–15:00 UTC, only thirty minutes. The proposed 45-minute joint handoff does not fit; move a window or revise the verified handoff protocol.

### Distinct decision

This computes whether a specific receiving session fits shared availability, rather than giving general time-zone coordination advice.

### Limits

Real calendars may have exceptions. This example uses fixed UTC windows on one day and a stated continuous requirement.

### Definitions and method context

- GAO Schedule Assessment Guide — https://www.gao.gov/products/gao-16-89g — General schedule-model context. All records, local policies and arithmetic are original toy examples, not a certified or optimized schedule.