# Check a deadline against required remaining work

Illustrative planning brief; no automatic product import.

Synthetic planning case: A model needs four days of preparation, three of review and one of packaging in sequence. The requested finish is day six from a ready day-zero start.

## Decision

The eight-day chain misses the requested day-six finish by two model days. Disclose the infeasibility and choose a scope, resource or deadline decision instead of moving labels.

## Owned work

- Verify required sequence
  - Owner role: Receiving lead
  - Acceptance evidence: None of the three activities can overlap under the stated inputs.
- Expose the deadline shortfall
  - Owner role: Scheduler
  - Acceptance evidence: Two model days of negative slack are shown beside the requested finish.
- Request a concrete plan change
  - Owner role: Decision owner
  - Acceptance evidence: A real assumption changes or the deadline is renegotiated; no unsupported date is accepted.

## Workflow

1. Verify required sequence. Check: None of the three activities can overlap under the stated inputs.
2. Expose the deadline shortfall. Check: Two model days of negative slack are shown beside the requested finish.
3. Request a concrete plan change. Check: A real assumption changes or the deadline is renegotiated; no unsupported date is accepted.

## Judgment

The durations are assumed, and resources may add further constraints. This ledger is not a forecast or a performance judgment.


## Filled manual planning note

The eight-day chain misses the requested day-six finish by two model days. Disclose the infeasibility and choose a scope, resource or deadline decision instead of moving labels. Required chain=4+3+1=8 days; deadline allowance=6. Slack relative to that request is 6−8=−2 days. The durations are assumed, and resources may add further constraints. This ledger is not a forecast or a performance judgment.


## Workflow questions

### Can I set the finish field to day six?

A label does not remove the eight days of required work under these assumptions.

### Does negative slack prove the team is slow?

No. It describes incompatibility between this plan and the requested window.

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

Activity | Model days | Dependency
--- | --- | ---
Preparation | 4 | Ready start
Review | 3 | After preparation
Packaging | 1 | After review
Requested finish | Day 6 | External planning request

### Reasoning

Required chain=4+3+1=8 days; deadline allowance=6. Slack relative to that request is 6−8=−2 days.

### Bounded result

The eight-day chain misses the requested day-six finish by two model days. Disclose the infeasibility and choose a scope, resource or deadline decision instead of moving labels.

### Distinct decision

The guide tests a fixed deadline against a complete remaining sequence and names the unresolved planning choice.

### Limits

The durations are assumed, and resources may add further constraints. This ledger is not a forecast or a performance judgment.

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