Management Summary Schedule

What a management summary schedule is

This is the practical application of the schedule levels: where the hierarchy is explained elsewhere, this lesson is about producing the top of it well — the one view leadership actually reads to answer "are we on track, and where are the risks?"

Roll up — never rebuild

The single most important principle: the summary must be a roll-up of the working schedule, derived through WBS and coding — not a separate schedule someone maintains by hand. The moment it's hand-built, it drifts from reality.

Done right, the summary updates automatically each period when the detailed schedule is statused. The executive's milestones and the foreman's lookahead move together, because they're the same data at different zoom.

What makes a good summary schedule

1. Key milestones — start, major phase completions, handover, contractual dates — the events leadership tracks.
2. Major phases / areas — a handful of summary bars (by phase, area, or system) — enough to show the shape, not the detail.
3. Status vs baseline — planned vs current/forecast — so the reader instantly sees ahead/behind and by how much.
4. The critical issues — the headline risks and the critical path at a summary level — what could move the finish.
5. Clarity over completeness — one or two pages, readable in a minute, no jargon. If it needs explaining, it's too detailed.

Using the summary schedule

The summary schedule is a communication and decision tool, produced each reporting cycle alongside the detailed update:

Ten things to remember

1. The management summary schedule is the Level 1–2 view for leadership — milestones, phases, status.
2. Its job is decisions, not detail — surface what matters at that altitude, omit the rest.
3. Roll up, never rebuild — derive it from the working schedule via WBS/coding.
4. A hand-built summary drifts — the "two schedules" disease destroys reporting credibility.
5. It updates automatically when the detailed schedule is statused.
6. Show key milestones, major phases, status vs baseline, and the critical issues.
7. Show the forecast, not just the baseline — leadership needs the variance, honestly.
8. Clarity over completeness — one or two pages, readable in a minute, no jargon.
9. Produce it each cycle alongside the detailed update, as a decision tool.
10. It completes the levels picture — one source of truth, many altitudes.