Schedule Communication and Reporting
Reporting that drives decisions
Schedule communication converts analysis into information each audience can act on. Concepts: audience and level of detail (executive summary, management, working level); Gantt and milestone charts; S-curves for planned versus earned progress; earned value schedule indicators (SPI, SV); forecast completion dates; dashboards; exception reporting; variance narratives with cause, impact, and recovery; and data integrity across calendars, scales, and units.
Traps: reporting SPI or percent complete without critical path context - a project can show SPI near 1.0 while the critical path carries negative float; mixing hours, cost, and duration units; comparing progress to the current schedule rather than the baseline; presenting colors and scales inconsistently between periods; and burying bad news. Another trap is a report with no forecast and no requested decision.
Worked example: SPI is 0.92 and the critical path shows 5 days of negative total float against a contractual milestone. The report should lead with the milestone exposure and recovery options, using SPI as supporting trend evidence rather than the headline.
Rule of thumb: report by exception against the baseline, and pair every variance with its cause, schedule impact, and recovery action. If a chart would not change a decision, move it to the backup.