Fictional product team / calendar-day planning

Will the promise survive the plan?

Learn why a dependency schedule can meet the promise while the team cannot cover the work. Synthetic launch assumptions.

View dates and capacity · Try the prediction exercises

Loading the schedule…

Project dates, name and files

Import current JSON

DEPENDENCY READY DATE

—

AGAINST THE PROMISE

—

CHANGE FROM BASELINE

—

Team capacity and overload dates

What changed, and why?

Compare changed tasks with baseline

02 / FOLLOW THE DEPENDENCIES

One change travels downstream.

Chart schedule

Bars use calendar days. The numbered rows match the exact schedule below. Use horizontal scrolling to explore dates.

Critical · zero float Has scheduling floatRead-only dates · dependencies enforced

Read the exact task schedule

Revised dates versus baseline · end dates are the boundary after work finishes
Task	Start → end	Days / type	Team / people per day	Depends on	Total float	End Δ

Edit this launch scenario

03 / CHANGE THE PLAN

Edit the assumption. Keep the consequence.

This scenario editor changes existing tasks and milestones. It does not add or delete work; a different plan can be imported as validated JSON.

Reload resets this tab. saves dates, dependencies and capacity assumptions; the comparison baseline is not included.

Dates are calculated from dependencies. A task starts after every predecessor finishes and after its earliest permitted start.

Edits apply together so a partially entered date or dependency cannot silently reschedule the plan. Changing the promise changes only the buffer. Native date pickers follow your browser locale; displayed dates use Nov 29, 2026.

How to read this schedule and its JSON

A day is a calendar date

Intervals include the start and exclude the end. A 2-day task starting January 5 occupies January 5 and 6; its successor can start January 7. All weekdays, weekends and holidays count. Dates use calendar arithmetic, without time-of-day or daylight-saving shifts.

Criticality and the promise answer different questions

Total float measures how many days a task can move without delaying the earliest project completion. Zero float means critical; it is not a probability or an importance score. The promised-date buffer is the number of calendar days between earliest completion and the promised ready date. It can be negative. Release constraints can also control the schedule.

Dependency dates and capacity are separate

All tasks must complete. Dependencies require finish-to-start order with no lag. Each task uses its assigned team’s entered people per day throughout its occupied calendar days. Daily demand is summed across overlapping tasks and compared with constant team capacity. Overload warnings do not move dates: this tool does not automatically level work, optimize staffing, or estimate uncertainty, costs or compliance readiness. Milestones consume no days or people; successors may start on the milestone date. Safety testing here is fictional scheduled work, not a safety assessment.

Local files, explicit contract

Import replaces only the current plan after full validation; the baseline stays unchanged. Export saves only the current plan. Files remain in memory in this tab; reloading restores the example. Download JSON to keep your work.

Version 2 fields: name, start, promise, resources, tasks. Resources have id, name and capacity (people/day). Each task has id, name, kind (task or milestone), duration, release (date or null), dependencies (task-ID array), resource and allocation (people/day). Milestones require duration 0, resource null, allocation 0. Version 1 files lack these assumptions and are rejected explicitly. Dates are YYYY-MM-DD from2020–2035; names1–80characters;1–30tasks; task durations1–365days;milestones0days; IDs start with a letter and use letters, digits, underscores or hyphens up to40characters. No extra fields. Schedule horizon≤730days and completion by2036. File limit128KiB. See the downloadable example for exact shape.