I have sat through hundreds of steering committee meetings on EPC megaprojects. As a planner, as a project controls lead, as a commercial manager reviewing someone else's programme. The pattern is always the same.
The PM puts up a Gantt chart. Thirty thousand activities compressed onto one slide. Someone on the committee squints and says "so are we on track?" The PM talks for eight minutes. Nobody in the room is any clearer. The committee moves to the next item. The schedule discussion achieved nothing.
This is not a presentation skills problem. It is a translation problem. The PM knows the schedule inside out. The committee needs five specific answers. The gap between those two things is where the meeting dies.
The five questions
Every steering committee on every capital project asks the same five questions. They may phrase them differently. They may ask them in a different order. But this is what they need to know:
| Question | What they actually mean |
|---|---|
| 1. Where are we? | Give me the current completion forecast and tell me how it compares to the baseline. One number. One comparison. |
| 2. Are we late? | What is the float on the critical path? Is it trending down? How fast? |
| 3. Why? | What are the top three or four drivers behind the current position? Not root cause analysis. Not a 40-page delay narrative. What moved the needle this period? |
| 4. What are we doing about it? | What is the recovery path? What has to happen for the forecast to hold? |
| 5. What could go wrong? | What are the near-critical paths? Where is the next risk? What are we watching? |
Five questions. Five slides. That is the format. Not a Gantt chart. Not a resource histogram. Not a progress curve buried in an appendix. Five slides that answer the five questions the committee walked into the room to have answered.
How to pull these from P6
All five answers live in your XER file. You are already collecting this data. The problem is that P6 is a scheduling tool, not a reporting tool. It stores the answers but it does not present them.
Slide 1: Completion forecast
Run the schedule. Look at the finish date of the last activity on the longest path. Compare it to the baseline finish date. The delta between those two numbers is your headline. That is the first thing out of your mouth.
"Current forecast completion is 14 November 2026, eight days behind the baseline of 6 November." The committee now has the single most important fact in the room. Everything else is context for that number.
Show a simple S-curve: planned versus actual cumulative progress. Not 30 lines on the chart. Two lines. Where we said we would be, and where we are. The gap between them is visible at a glance.
Slide 2: Float position and trend
Total float on the critical path. Not free float. Not the average float across all paths. The total float on the path that determines the finish date.
More importantly: the trend. Plot total float over the last six reporting periods. If it was 22 days four months ago and it is 4 days now, the committee can see the trajectory without you saying a word. A chart that goes down and to the right tells the story. If you have to explain the chart, the chart is wrong.
In P6, filter to the longest path, pull the total float, and track it period over period. Most PMs already have this data. They just do not present it as a trend line.
Slide 3: What drove the position this period
This is where most PMs get lost. They try to explain everything that happened in the last month. The committee does not want everything. They want the three or four items that moved the critical path or consumed the most float.
Run a comparison between the current schedule and the prior period. P6 will show you which activities slipped, which logic ties changed, which constraints moved. Filter to the ones that affected the longest path or near-critical paths. Those are your drivers.
Present them as a simple list. Activity, area, what happened, impact in days. No narrative beyond what the committee needs to understand why the forecast moved.
Slide 4: Recovery actions
For each driver on Slide 3, what is the recovery? If structural steel slipped because of a procurement delay, what is the revised delivery date and what does the re-sequencing look like?
The committee wants to know that someone has a plan. Not a perfect plan. A plan. If the answer is "we are still assessing", say that. Do not fabricate recovery schedules under pressure in the meeting. But if you have already modelled the recovery in P6 as a what-if scenario, present the comparison. "If we accelerate mechanical in Zone 3 by working weekends in May and June, we recover 12 of the 18 days and the forecast moves to 2 November."
The what-if scenario capability in P6 exists for exactly this purpose. Use it before the meeting, not during it.
Slide 5: Risk and near-critical paths
The steering committee needs to know what to worry about next month. Not a risk register with 200 entries. The three or four near-critical paths that could become critical if something goes wrong.
In P6, sort by total float ascending. The paths with float between 0 and 20 days are your watch list. For each one, name the area, the current float, and what would cause it to go critical. That is the risk view the committee actually needs.
The principle: Every slide answers one question. Every chart supports one finding. Every number traces back to the XER file with a data date the committee can verify. No decoration. No filler. No slides that exist because they were in last month's pack.
The common mistakes
Showing the Gantt chart. The committee cannot read 30,000 activities on one slide. Nobody can. The Gantt is your working tool, not your presentation tool. If a committee member asks to see it, pull it up. But it is never Slide 1.
Presenting data without a finding. A chart without a headline is a test, not a report. Every slide needs to lead with what the data means, not what the data is. "Float is 4 days and trending down at 4.5 days per period" is a finding. A float chart with no label is homework for the committee to interpret themselves.
Mixing schedule and cost. Keep them separate unless you are specifically presenting earned value. Cost has its own five questions. Trying to answer both in one pack doubles the length and halves the clarity.
Updating the pack the night before. If your reporting cycle does not give you enough time to analyse the data before the meeting, the problem is the process, not the presentation. Build the pack incrementally as each period update is loaded. By the time the meeting arrives, you are reviewing the pack, not building it.
The real problem
The real problem is time. A PM on a major EPC project has 4-8 hours per month to turn a schedule update into a steering committee pack. Most of that time goes to extracting data from P6, building charts in Excel, formatting slides in PowerPoint, and manually writing the narrative around each finding. The analysis itself takes 30 minutes. The translation takes the rest of the day.
This is the problem we built Allsignal to solve. Upload your XER. The six engines calculate critical path position, float trends, baseline variance, period-on-period drivers, risk assessment, and earned value. Five slides. Five answers. The pack that took half a day is done in minutes.
But even if you never use Allsignal, the five-slide structure works. It works because it is built around what the committee needs, not what the PM has. Start with their questions. Answer each one on a single slide. Support each answer with one chart and one finding. That is the whole method.