Gantt chart
Place dated tasks and owners on a timeline, then examine the calendar, dependencies and available person-hours.
Use a Gantt chart after stage outcomes are clear and you need task-level dates. Identify dependencies before assuming tasks can run in parallel. The bars display a schedule; they do not establish reliable estimates or available people.
Task IDs, inclusive start and finish dates, a working calendar, predecessors, owners, effort and capacity assumptions, and actual progress records if available.
A task timeline with dependency and resource checks, plus the tasks and assumptions affected by a delay.
How to use it
- List deliverables and task IDs, completion conditions and owners.
- Define the work calendar, inclusive date convention and dependency rules.
- Estimate duration and effort, then check each person's daily capacity.
- Draw the timeline and distinguish plan, actual progress, gates and unconfirmed arrangements.
- When a task changes, review affected successors and resources, preserving assumptions and review dates.
Keep its limits in mind
Workdays, elapsed calendar days and person-hours are different units. Parallel work needs both dependency and capacity support. This diagram displays entered dates; it does not infer progress, critical paths, resource leveling or completion probability. Check missing or invalid dates instead of filling them with defaults.
Checking a seven-workday preparation schedule
Fictional teaching example: Pinebridge is preparing a booking-service pilot. Packet F0 records one mature W0 cohort: 100 eligible requests, 60 confirmed bookings and 48 completed services within those 60. The future pilot, staffing and plans are unapproved and unexecuted.
On a small screen, scroll across the diagram to read it.
Reproduce the dates: A takes two workdays, B three, C two, D one and E one. B and C start after A, while D waits for both. The seven-workday chain ends Oct 27; Oct 28 is unallocated reserve.
Check people separately: The fictional calendar treats listed weekdays as available without holidays, leave or overtime. The Analyst, Builder, Ops and Lead are each assumed available four hours per workday, and the Sponsor one hour. D needs four hours from each of Builder and Ops, not four hours combined. These availabilities remain unconfirmed.
Review a delay: If B finishes Oct 26 rather than Oct 23, D shifts to Oct 27 and E to Oct 28. The reserve is consumed. This scenario neither reschedules people automatically nor guarantees the later decision.
The calendar is a teaching assumption and dates are inclusive. D needs four hours from each of two people. The reserve does not absorb every risk; the figure does not calculate actual progress or level resources.
Next step: The Lead should confirm each person's calendar and capacity, then update the draft against actual records rather than treating bar length as progress.
Three reasons to pause before trusting the bars
A Gantt chart becomes useful when each bar has a defined output, a working calendar and an owner whose capacity can be checked. Start with the dependency statements, then place the dates. A visually tidy overlap does not show that two people are free or that one person can perform both tasks.
Pause if dates omit holidays, leave or an agreed work pattern. Pause if duration is being calculated by dividing a team total by assumed full-time staffing. Pause if progress is represented by today’s position on the bar rather than an actual record of completed work. Resolve missing inputs openly; a blank completion status is more honest than a guessed percentage.
Keep original dates and a separate revision note. When a predecessor slips, inspect every dependent task and its participants before accepting a new endpoint. This page displays entered dates. The schedule checks below are explicit reasoning about the fictional inputs, not automatic resource leveling or critical-path detection by the figure.
Choose dates, dependencies or responsibilities
Use the calendar view for a dated conversation. If the uncertainty concerns which activities must wait or who may authorize an output, start with the corresponding material rather than disguising the question as a date problem.
| Method | Input needed | What it clarifies |
|---|---|---|
| Gantt chart | Dated tasks, calendar, dependencies and capacity | A proposed schedule and conflicts to inspect |
| PERT chart | Task network and single or three-point durations | Conditional path lengths and float |
| Roadmap | Stage outcomes and enabling conditions | Why a phase is needed before a later decision |
| RACI matrix | Deliverables and supported decision rights | Who should perform, decide or be consulted |
Worked case: reproduce the seven workdays and each person’s effort
This continues fictional Pinebridge F0, not the independent Xinggang PERT example. Preparation runs from A through E. The supplied calendar lists October 19, 20, 21, 22, 23, 26, 27 and 28, 2026 as workdays, without holidays, leave or overtime. Dates include both endpoints. The proposed chain A–B–D–E uses 2+3+1+1 = seven workdays through October 27; C runs after A alongside B.
The effort ledger explains what “alongside” requires. Analyst, Builder, Ops and Lead are each assumed available four hours per workday; Sponsor has one hour. B therefore needs three Builder workdays for 12 hours, while C needs two Ops workdays for eight hours. D occupies one date but needs four hours from each of Builder and Ops: eight person-hours in total. E requires four Lead hours plus one Sponsor hour. Every availability is unconfirmed.
Total estimated effort is 8+12+8+8+5 = 41 person-hours across all roles. That total is neither 41 elapsed hours nor seven full-time days. October 19 through 27 includes nine calendar dates, with the weekend excluded from the working calendar. Do not divide 41 by a nominal team size to infer a delivery duration.
| Task / dates | Predecessor | Effort / capacity check |
|---|---|---|
| A: October 19–20 | None | Analyst 8h across two 4h workdays |
| B: October 21–23 | A | Builder 12h across three 4h workdays |
| C: October 21–22 | A | Ops 8h across two 4h workdays |
| D: October 26 | B and C | Builder 4h AND Ops 4h that day |
| E: October 27 | D | Lead 4h AND Sponsor 1h that day |
Review a delay without inventing progress or availability
Under the original assumptions, the dates fit the stated dependencies and daily limits. That is the conclusion of a draft check, not confirmation from the people involved. The Lead should ask each role about its actual calendar, parallel duties and task estimate before treating the schedule as usable.
For the supplied scenario where B finishes October 26 instead of October 23, D moves to October 27 and E to October 28. The previously unallocated reserve is consumed. Builder and Ops must both be available on the new rehearsal date; the Sponsor must be available for the revised decision. If any of those checks fails, moving the bars one day is insufficient. Revisit scope, sequencing or the decision window with the relevant owner.
At review, preserve the baseline and append actual start, actual finish, remaining estimate, blockers and evidence for each task. Leave unknown progress unknown. Completing D provides rehearsal evidence; it does not approve the pilot or produce the later target of 60 completed services. Record the Sponsor’s actual decision separately. Recheck dependencies, capacity and the meaning of the endpoint after every material revision.
Check your work
- Dates, predecessors, owners and completion conditions agree.
- Duration and effort are separate; daily capacity is checked or explicitly unconfirmed.
- Delay effects and reserve are visible, with no invented progress or completion probability.
Framework references
References explain the framework and its scope; they do not validate the fictional example's results.
Put the framework to work
Copy the outline and add your question, evidence, and open questions.