# Inspect a branch's available schedule float

Illustrative planning brief; no automatic product import.

Synthetic planning case: A six-day design branch and a four-day data branch feed a one-day assembly. The complete toy model has independent resources and a common start.

## Decision

The data branch has two model days of available delay before it would push assembly beyond day six. Keep that float conditional on the unchanged network.

## Owned work

- Confirm the merge criterion
  - Owner role: Receiving owner
  - Acceptance evidence: Assembly requires both complete inputs.
- Calculate the allowable branch delay
  - Owner role: Scheduler
  - Acceptance evidence: Day six minus day four leaves two model days under the unchanged network.
- Record the float-consuming change
  - Owner role: Project lead
  - Acceptance evidence: Any data delay above two days reopens the finish decision.

## Workflow

1. Confirm the merge criterion. Check: Assembly requires both complete inputs.
2. Calculate the allowable branch delay. Check: Day six minus day four leaves two model days under the unchanged network.
3. Record the float-consuming change. Check: Any data delay above two days reopens the finish decision.

## Judgment

The float belongs to this complete deterministic model. A changed resource calendar or edge can alter it.


## Filled manual planning note

The data branch has two model days of available delay before it would push assembly beyond day six. Keep that float conditional on the unchanged network. The merge is driven by day six. Data can move from day four to day six: two days of model float; a three-day delay would make it ready at seven and push final finish to eight. The float belongs to this complete deterministic model. A changed resource calendar or edge can alter it.


## Working artifact

- Data ready at day 4 / Assembly waits until day 6 / Recheck if either input or gate changes
- Up to two-day data delay / Does not move the merge beyond day 6 / Recheck resource availability
- Three-day data delay / Data then drives a day-7 merge / Replan final finish to day 8 or change assumptions


## Workflow questions

### Is float free capacity?

No. It is conditional schedule allowance, not extra people or permission to omit work.

### Can several downstream edits each spend the same float?

Not independently. Recalculate the full affected network after changes.

## 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

Branch or gate | Earliest ready day | Required by
--- | --- | ---
Design | 6 | Assembly start at 6
Data | 4 | Assembly start at 6
Assembly | 7 finish | Both inputs ready

### Reasoning

The merge is driven by day six. Data can move from day four to day six: two days of model float; a three-day delay would make it ready at seven and push final finish to eight.

### Bounded result

The data branch has two model days of available delay before it would push assembly beyond day six. Keep that float conditional on the unchanged network.

### Distinct decision

The decision sets a specific permissible-delay boundary for one nondriving branch.

### Limits

The float belongs to this complete deterministic model. A changed resource calendar or edge can alter it.

### 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.