Identify work versus event
Owner role · Schedule owner
Evidence: The milestone records completion of the already-modelled proof review.
Dependency schedules / Delivery leads, planning owners and acceptance reviewers
Decision deskKeep milestones separate from activity duration
Distinguish a checkpoint event from the work that must precede it.
The artifact prevents duplicate duration when an activity and its completion event are both scheduled.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Original worked case · Manual planning resource
Inspect the decision, not just the summary.
Start with the invented evidence, follow the reasoning, and retain its limits when adapting the brief.
01 · Inspect the inputs
Every record stays visible
| Schedule element | Model duration | Meaning |
|---|---|---|
| Proof review | 2 days | Work performed |
| Proof accepted | 0 days | Checkpoint after review |
| Print preparation | 1 day | Starts after accepted checkpoint |
Use horizontal scrolling for wide tables. These records are invented, not customer data.
02 · Follow the reasoning
How the case leads to a decision
With the checkpoint correctly represented, the sequence is 2+0+1=3 model days. Giving both review and its acceptance event two days would produce an unsupported five-day sequence.
The bounded result
Keep the reviewer activity at two days and the acceptance milestone as a zero-duration checkpoint in this model. Do not charge the same review twice.
Definitions and method context
Records, decisions and policies are original synthetic examples. External references supply context; they do not validate these cases or TeamBoostAI capabilities.
GAO Schedule Assessment Guide ↗
General schedule-model context. All records, local policies and arithmetic are original toy examples, not a certified or optimized schedule.
External references checked 6 October 2026. Demand for these topics has not been measured.
Decision desk
Decide before adding more work
Decision to make: Keep the reviewer activity at two days and the acceptance milestone as a zero-duration checkpoint in this model. Do not charge the same review twice.
Synthetic planning case: A draft gives the “proof accepted” milestone two days, while its actual reviewer activity already has a separate two-day duration.
Retain the actual review activity
Owner role · Reviewer
Evidence: Two days of review and its evidence remain visible.
Link the next activity
Owner role · Production owner
Evidence: Print preparation starts only after the acceptance checkpoint.
Filled manual planning note
Invented planning text. Adapt it to your evidence and confirmed owners.
Keep the reviewer activity at two days and the acceptance milestone as a zero-duration checkpoint in this model. Do not charge the same review twice. With the checkpoint correctly represented, the sequence is 2+0+1=3 model days. Giving both review and its acceptance event two days would produce an unsupported five-day sequence. Zero is a milestone convention in this example, not an assertion that people make instantaneous decisions.
Questions about this workflow
Does zero duration mean no acceptance work is needed?
No. The two-day review activity supplies that work and evidence.
Can every approval be a zero-duration milestone?
An approval activity may take time; its completion event is the checkpoint. Model both meanings deliberately.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.
Put the outline to work
- Identify work versus event. Check: The milestone records completion of the already-modelled proof review.
- Retain the actual review activity. Check: Two days of review and its evidence remain visible.
- Link the next activity. Check: Print preparation starts only after the acceptance checkpoint.
From a useful outline to team work
Explore TeamBoostAI for your team
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 the workflows available in your account before adopting this outline.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.