You present your five slides. The completion forecast, the float trend, the period drivers, the recovery plan, the risk watch list. The project director nods. Then someone on the committee says: "What about Area 3 mechanical? We heard they lost two weeks."
This is not in your five slides. Your five slides cover the project-level picture. Area 3 mechanical is three levels down in the WBS. You know the answer because you updated the schedule last week. But you do not have a slide for it. So you start talking without visuals, the committee loses the thread, and the conversation becomes adversarial because nobody can see the data.
Backup slides solve this problem. Not more main slides. Backup slides. A separate set of pre-built, data-backed slides that cover the questions you expect the committee to ask beyond the five-slide summary.
What makes a good backup slide
A backup slide has four properties:
- It answers one question. "What is the progress on Area 3 mechanical?" One chart. One finding. One slide.
- It uses the same data as the main slides. Same XER file, same data date, same reporting period. No separate data source. No different cut-off date. The backup slide and the main slide are looking at the same schedule.
- It has a finding, not just data. The chart shows the S-curve for Area 3 mechanical. The title says "Area 3 mechanical is tracking 8% behind plan, driven by cable tray installation delay." The committee reads the title and understands the answer before they look at the chart.
- It is pre-built. Not assembled in the meeting. Not pulled from P6 live. Built before the meeting, reviewed, and ready. If you have to build it in the room, it is not a backup slide. It is a scramble.
How to decide which backup slides to build
You cannot anticipate every question. You can anticipate most of them. The committee's follow-up questions come from a predictable set of patterns:
| Pattern | Example question | Backup slide |
|---|---|---|
| Drill down by area | "What is happening in Area 3?" | S-curve filtered to Area 3, with progress vs baseline |
| Drill down by discipline | "Where are we on mechanical?" | Activity status histogram by discipline, showing not started / in progress / complete |
| Specific delay event | "How much did the cable tray delay cost us?" | Milestone variance waterfall showing the drift on affected milestones |
| Resource concern | "Are we getting the welders we need?" | Float trend filtered to activities requiring welding resources |
| Historical comparison | "Did we see this coming?" | Float trend over six periods for the affected path, showing the trajectory |
On most EPC projects, 80% of follow-up questions fit these five patterns. If you build one backup slide per area (typically 4-6 areas), one per major discipline (3-4 disciplines), and 2-3 for known hot topics, you have 10-12 backup slides that cover nearly every question the committee will ask.
The anatomy of a backup slide
Keep the format identical to the main slides. Same dimensions (1280x720 if you are using standard widescreen). Same margins. Same font. Same colour system. The backup slide should look like it belongs in the same pack. It does belong in the same pack.
Header
Number the backup slides separately. A-1, A-2, A-3. Not slide 6, 7, 8. The "A" prefix tells the committee these are appendix slides, not part of the main narrative. This matters because it sets the right expectation: the main story is five slides, these are supporting evidence for specific questions.
Title
State the finding, not the topic. "Area 3 mechanical: 8% behind plan, cable tray driving" is a finding. "Area 3 Mechanical Progress" is a topic. The committee reads the title and already has the answer. The chart is confirmation.
Chart
One chart per slide. The same chart types you use in the main slides: S-curves, float trend lines, activity status histograms, milestone variance waterfalls. The chart is filtered to the scope the question covers. Area 3 only. Mechanical only. This contractor only.
Narrative
Two to three sentences below the chart. What the data shows, what is driving it, what the project team is doing about it. No more than 300 characters. If you need more than 300 characters to explain a backup slide, the slide is covering too much ground. Split it.
Footer
Data date, source label, report reference. Same as the main slides. The backup slide is part of the contemporaneous record. It needs the same traceability.
When to pull backup slides into the main pack
Sometimes a backup topic becomes the main topic. Area 3 was a background item last month but this month the delay has consumed the critical path float. The backup slide becomes Slide 3 (period drivers) or Slide 5 (risk). Promote it. Move it into the main five. Demote whatever it replaced to backup.
The five-slide structure is not rigid about which five questions get answered at the project level. It is rigid about the structure: five questions, five slides, one finding per slide. The content rotates based on what matters this period.
The test: If you walk into the steering committee and the project director asks a question about a specific area, discipline, or delay event, can you put a slide on screen within five seconds that answers it with a chart and a finding? If yes, you are prepared. If no, you need backup slides.
The time problem
Building 10-12 backup slides per month is another 2-3 hours on top of the 4-8 hours most PMs already spend on the main pack. This is why most PMs do not build them. The time does not exist.
The backup slides use the same data as the main slides. The same S-curve engine, the same float calculation, the same baseline comparison. The only difference is the filter: this area instead of the whole project, this discipline instead of all disciplines. The computation is identical. The formatting is identical. The only variable is the scope.
If the computation and formatting are automated, building a backup slide is a 30-second operation: select the chart type, select the scope filter, write the title, write the narrative. Ten backup slides in five minutes.
This is what Allsignal's Build Your Backup feature does. Select the chart type from the catalogue. Filter to the scope. Write the finding. Lock the slide. It renders from the same engines, using the same data, with the same visual format as the main panels. The PM's time goes to deciding what to say, not to building the chart.
But even without automation, the principle holds. Ten backup slides, pre-built, covering the predictable follow-up questions, ready to pull up when the committee asks. The PM who has them looks like they understand their project. The PM who does not looks like they are learning about it in real time.