# Separate finish dates for different milestones

Illustrative planning brief; no automatic product import.

Synthetic planning case: A pilot package needs two days of preparation and one of review. Wider rollout additionally needs three days of localization after pilot review; both endpoints have separate receivers.

## Decision

Pilot-ready is day three and wider-rollout-ready is day six in the supplied sequence. Do not use one finish label for both receiving decisions.

## Owned work

- Name both receiving scopes
  - Owner role: Project owner
  - Acceptance evidence: Pilot and wider rollout have distinct accepted output boundaries.
- Trace each endpoint’s predecessors
  - Owner role: Planner
  - Acceptance evidence: Localization is required for rollout and is not silently required for pilot.
- Communicate two readiness decisions
  - Owner role: Receiving leads
  - Acceptance evidence: Day-three and day-six model results remain separately labelled and reviewed.

## Workflow

1. Name both receiving scopes. Check: Pilot and wider rollout have distinct accepted output boundaries.
2. Trace each endpoint’s predecessors. Check: Localization is required for rollout and is not silently required for pilot.
3. Communicate two readiness decisions. Check: Day-three and day-six model results remain separately labelled and reviewed.

## Judgment

Readiness milestones are scope-specific. The invented sequence does not prove live availability or successful rollout.


## Filled manual planning note

Pilot-ready is day three and wider-rollout-ready is day six in the supplied sequence. Do not use one finish label for both receiving decisions. Pilot readiness=2+1=3. Wider readiness=3+3=6. The additional localization does not erase the earlier bounded pilot endpoint. Readiness milestones are scope-specific. The invented sequence does not prove live availability or successful rollout.


## Workflow questions

### Can the pilot begin while localization is unfinished?

Only if its agreed scope does not require that localization; confirm the receiving boundary.

### Does pilot-ready imply all customers have access?

No. This manual schedule says nothing about deployment or account entitlement.

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

Endpoint or activity | Model duration | Ready day
--- | --- | ---
Preparation | 2 | 2
Pilot review | 1 | 3
Pilot-ready milestone | 0 | 3
Localization after review | 3 | 6
Rollout-ready milestone | 0 | 6

### Reasoning

Pilot readiness=2+1=3. Wider readiness=3+3=6. The additional localization does not erase the earlier bounded pilot endpoint.

### Bounded result

Pilot-ready is day three and wider-rollout-ready is day six in the supplied sequence. Do not use one finish label for both receiving decisions.

### Distinct decision

The artifact separates terminal milestone scopes instead of declaring one global completion date.

### Limits

Readiness milestones are scope-specific. The invented sequence does not prove live availability or successful rollout.

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