WhenMathReview & Approval Timeline Planner
Add a fixed number of review cycles to any phase, each with its own duration. Every review cycle is a visible block in the schedule, not a hidden guess at how long rework usually takes.
Want to learn more?
Worked example
A Draft phase takes 3 days, with two 1-day review cycles added after it. The receipt shows the draft finishing on day 3, the first review finishing on day 4, and the second review finishing on day 5, the actual project finish, 2 full days later than the draft work alone would suggest. Drop that same plan down to a single review cycle instead, and the finish moves back up to day 4, one day earlier, since only one review block now sits after the draft.
Common mistakes
- Estimating only the "doing" time for a phase and forgetting that review and approval cycles are real elapsed time, not free time layered on top.
- Assuming review cycles can overlap with the next phase's work. Each cycle is chained sequentially, so its full duration always counts before anything downstream can start.
Limitations
Each review cycle is a fixed duration declared directly. This does not model the chance that a review triggers rework beyond what has already been entered as separate cycles.
Frequently asked questions
- Can review cycles run in parallel with other phases?
- No, each review cycle is chained sequentially after the phase or prior review cycle it belongs to, since a review genuinely needs its input finished first.
- Can a phase have zero review cycles?
- Yes, setting review cycles to zero for a phase means it schedules exactly like a plain phase with no review time added on afterward.