Plan and manage schedule
In the app: Project → Gantt (Timeline · List · Variance) · Completion band · Schedule compression
PMP ECO · Process (41%) · Task Pr8. Build a schedule from the work, find the path that sets the finish date, and when the work slips, see where the slip goes and what it would cost to get the time back.
What it is
Schedule management runs from planning to control:
- Define and sequence the activities. Every work package becomes activities, linked by dependencies: finish-to-start (FS), start-to-start (SS), with leads and lags.
- Estimate durations (analogous, parametric, three-point / PERT: (O + 4M + P) ÷ 6).
- Develop the schedule with the critical path method: a forward pass gives each activity's early dates, a backward pass its late dates, and the difference is total float. Activities with zero float form the critical path: the longest path through the network, which sets the finish date.
- Baseline it, and control it: compare the working schedule with the baseline, forecast the finish, and act on the variance.
When the finish is at risk, two compression techniques pull it in:
| Crashing | Fast-tracking | |
|---|---|---|
| What it does | Adds resources to shorten critical activities | Overlaps activities that were planned in sequence |
| Costs | Money | Risk: rework if the earlier work changes |
| Only helps if | It shortens every critical path | The overlapped activities are on the critical path |
Why it matters
- A day lost on the critical path is a day lost on the finish. A day lost on an activity with float may cost nothing. Knowing which is which decides where the PM spends attention.
- Slips travel. A late activity hands its delay to everything after it on the path. The activities that haven't started yet are already late.
- A single finish date hides the risk. "12 September" sounds certain. "One chance in three of meeting the committed date" is the honest version.
Where you do it in VanillaPM
- Gantt → List is the activity network in schedule order: each activity's dependencies with their type and lag, start, finish, duration and total float, with the critical path flagged.
- Gantt → Variance compares the working schedule with the baseline, activity by activity, and says what kind of slip each one is: finished late, running late, or knock-on (late because a predecessor is). It shows the baseline finish against the forecast finish.
- Completion band (Monte Carlo) re-runs the schedule from each activity's three-point estimate and gives P50/P80/P90 finishes and the chance of meeting the baseline.
- Schedule compression lists the critical links you could fast-track, and builds a crash plan for a target number of days, at the cheapest cost per day.
- The integrated plan (Pr1) checks Working plan matches the baseline and Scope, schedule and cost cover the same work.
Free tools: PERT / three-point estimate calculator · Critical path and float calculator.
Walked example — Coral Ridge Resort
The committed finish, baseline v3, is 31 August 2028. The schedule has 21 activities; 17 of them are critical. That's normal for a building: the frame, the facade, the services, the fit-out and the approvals follow each other, with planned overlaps.
What has happened so far:
- Piling finished 25 days late and the raft 18 days late. Neither moved the finish: the frame started over the basement as planned (start-to-start), which absorbed both.
- The RCC frame (floors 1–5) is running 12 days late, and it's on the critical path. Nothing absorbs that, so the nine activities after it are each 12 days late before they've started. The forecast finish is 12 September 2028.
- The Monte Carlo band agrees, and is wider: about a one-in-three chance of meeting 31 August.
Two more findings from the integration checks: the integrated plan now flags the working finish as +12 days against the baseline, and the landscaping and external works (the beachfront deck, terraces, parking and access roads) are in the scope but in neither the schedule nor the budget.
The workspace — the theory behind each screen
Every screenshot is the actual sample project, not a mock-up.
1 · The network and the critical path
The theory: sequence activities and develop the schedule. Link each activity to what it depends on, with the right relationship and lag. The critical path method then gives every activity its float. Zero float is critical; small float is near-critical, and worth watching just as closely.

Reading the screenshot: 21 scheduled activities, 17 on the critical path, 784 working days, scheduled finish 12 Sep 2028. The links show how the plan overlaps work: Structural & geotechnical design starts SS +28 wd after the architectural design; the RCC frame floors 6–10 follows floors 1–5 FS. Site prep has 1 wd of float and Cores, stairs & lift shafts has 1 wd too: near-critical. The Basement remedial works have 768 wd: nothing waits for them (Pr4 smoothed them for that reason).
✅ Do model overlaps as start-to-start links with a lag, so the network matches the plan.
❌ Avoid activities with no successor. Their float is meaningless, and the critical path is wrong.
2 · Variance: where the slip goes
The theory: control schedule. Compare the working schedule with the baseline. A slip on an activity with float may be absorbed; a slip on the critical path moves every later activity, and the finish.

Reading the screenshot: baseline finish 31 Aug 2028, forecast 12 Sept 2028, 12 days after the baseline. The grey bars are the baseline; the coloured bars are the working schedule. Piling and the raft finished late (25 and 18 days) without moving the finish. RCC frame floors 1–5 is running 12 days late (red), and from floors 6–10 to the brand pre-opening audit every activity is +12 d knock-on (amber): late before it starts.
✅ Do look for the first late activity on the critical path. That's the one to fix.
❌ Avoid re-baselining to clear the red. That hides the variance instead of deciding it.
3 · The finish is a range, not a date
The theory: schedule risk analysis. A three-point estimate per activity, simulated many times, gives a distribution of finish dates. Report the date you'd commit to (often P80), and the chance of meeting the baseline.

Reading the screenshot: P50 late September 2028, P80 early November, P90 late November; only about 30% chance of finishing by the baseline (31 Aug 2028). The tornado shows what drives the spread: the guest-room fit-out, the MEP first fix and the RCC frame. That's where better estimates, or more management attention, change the answer. Each re-run samples again, so the figures move a little; the picture doesn't.
✅ Do quote a finish with its confidence: "P80, early November".
❌ Avoid reporting the deterministic date as if it were certain.
4 · Getting the time back: crash or fast-track
The theory: schedule compression. Crashing buys time with money, cheapest day first, and only on the critical path. Fast-tracking overlaps work in sequence, and buys time with risk.

Reading the screenshot: asked to pull the finish in by 12 working days, the crash plan saves 1 day for USD 4,000 (one day off the upper frame) and stops: Couldn't reach the full 12-day target. The cores and lift shafts run alongside the frame with 1 day of float, so after one day they are critical too, and nobody has priced crashing them. The fast-tracking list shows where the time really is: start the sea-facing curtain wall on the lower floors while the upper frame is still going up, at the price of coordination risk. Whichever the PM proposes, it's a decision with cost and risk, so it goes to the change control board with the impact stated.
✅ Do check what's running in parallel before promising a crash. Parallel paths cap it.
❌ Avoid fast-tracking work whose design is still changing. The overlap turns into rework.
Best practices & pitfalls
- Do link every activity into the network, from the charter to the last approval before handover.
- Do watch near-critical activities; one day of float disappears fast.
- Do forecast with a range, and say which percentile you're committing to.
- Pitfall: a schedule that ends at "practical completion" when the project's commitment is "open". The occupancy certificate and the brand audit are on the critical path too.
- Pitfall: crashing a non-critical activity. It costs money and moves nothing.
On the PMP exam
Schedule is technique-heavy. Know the forward and backward pass, total float (late start − early start) and free float, and that the critical path is the longest path with zero (or the least) float. Know FS, SS, FF and SF, leads and lags, and PERT ((O + 4M + P) ÷ 6). Know crashing (adds cost, only on critical activities) and fast-tracking (adds risk, overlaps sequential work). In scenarios, the best answer analyses the impact on the critical path first, compresses where it's cheapest or least risky, and takes any change to the baseline through integrated change control.