# Replace a hidden lag with owned work

Illustrative planning brief; no automatic product import.

Synthetic planning case: A plan inserts a two-day gap after artwork before publication. The gap actually contains one day of rights review and one day of receiving approval.

## Decision

Represent the two owned review activities explicitly before relying on the publication date; a bare lag hides their evidence and responsible roles.

## Owned work

- Investigate the gap
  - Owner role: Planning owner
  - Acceptance evidence: The supposed lag contains two distinct review obligations.
- Assign the hidden work
  - Owner role: Review coordinators
  - Acceptance evidence: Rights review and receiving approval have separate roles and evidence.
- Update publication readiness
  - Owner role: Publisher
  - Acceptance evidence: Both reviews are accepted before the publication gate is crossed.

## Workflow

1. Investigate the gap. Check: The supposed lag contains two distinct review obligations.
2. Assign the hidden work. Check: Rights review and receiving approval have separate roles and evidence.
3. Update publication readiness. Check: Both reviews are accepted before the publication gate is crossed.

## Judgment

The example does not supply legal clearance or a publication permission. Apply the organization’s actual review process.


## Filled manual planning note

Represent the two owned review activities explicitly before relying on the publication date; a bare lag hides their evidence and responsible roles. The visible sequence still spans two days in this model, but its components are one-day reviews with separate proof. Equal totals do not make their semantics interchangeable. The example does not supply legal clearance or a publication permission. Apply the organization’s actual review process.


## Workflow questions

### Does making the activities visible shorten the plan?

Not by itself. It makes responsibility and missing evidence inspectable.

### Can a genuine external wait stay a lag?

It may, with an explicit meaning and end condition; do not hide required owned work inside it.

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

Stage | Model days | Meaning
--- | --- | ---
Artwork complete | 0 at handoff | Upstream output
Rights review | 1 | Owned review work
Receiving approval | 1 | Owned acceptance work
Publication | After both | Next permitted stage

### Reasoning

The visible sequence still spans two days in this model, but its components are one-day reviews with separate proof. Equal totals do not make their semantics interchangeable.

### Bounded result

Represent the two owned review activities explicitly before relying on the publication date; a bare lag hides their evidence and responsible roles.

### Distinct decision

This distinguishes an unexplained schedule lag from activities that require ownership and proof.

### Limits

The example does not supply legal clearance or a publication permission. Apply the organization’s actual review process.

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