Analyze a scenario

A scenario shows you that the schedule changed. To answer the question behind it — did this actually help, and what does it cost? — you need numbers. Owl PM gives you three ways to measure a scenario against your schedule, from a glance to a column per activity.

You want toUse
See a whole dashboard as the scenario has itThe dashboard's schedule picker
See the schedule and the scenario on one chartAn analytic's Compare with
See, activity by activity, what movedA formula column that reads the scenario

Run a dashboard on a scenario

Every dashboard (and every analytic in its own tab) has a schedule picker at the top, set to Current schedule. Open it and choose a scenario.

"The Project Health dashboard with its schedule picker open, listing Current schedule and each scenario."121Current schedule — the picker at the top of every dashboard.2The picker lists the current schedule and every scenario. Pick one and every card is worked out on that scenario.

Every card on the dashboard is worked out again on the scenario's own activities, assignments and resources: the figures, the S-curve, the hours, all of it. Nothing about your schedule or the dashboard changes, and switching back is instant. Flip between Current schedule and the scenario and read the same cards side by side.


Compare on one chart

To see both on the same chart, compare the analytic with the scenario. In the analytic editor, under Compare with, click Add and pick the scenario under Scenarios. Then choose how to draw it:

  • Ghost — each series is drawn again for the scenario, beside itself: a dashed line next to a line, a dashed outline over stacked steps, a tick on a bar, a "vs" on a figure.
  • Difference — each series becomes the schedule minus the scenario, period by period. Above zero, your schedule has more.
"Weekly labor hours by resource with the Derisked Schedule drawn as a dashed ghost: the scenario's peak sits in February 2027, nine weeks after the current schedule's December peak."

In this example — weekly labor hours against what the crew can work, compared with the Derisked Schedule — the scenario's peak (dashed) comes about nine weeks later than the current schedule's and still goes over the available hours. The The numbers table under the chart lists both, week by week.

Ask Owl
Compare weekly hours with the Derisked Schedule scenario.
Show the forecast finish, critical activities and budget as figures, against the Full Governance Parallelization scenario.
Which scenario finishes first, and what does each do to the peak crew?

See what moved, activity by activity

A formula column can read any field as a scenario has it, with IN(SCHEDULE("name"), …). This column is how many working days each activity's finish moves in the Derisked Schedule:

Formula
=WORKDAYS([Finish date], IN(SCHEDULE("Derisked Schedule"), [Finish date]))

Add it to the grid, sort or filter by it, or chart it. See What-ifs and other schedules for more, including quick what-ifs that don't need a scenario at all.


Decide

Compare the things the scenario was meant to change:

  • Finish dates — does the scenario pull the finish in, and by how much?
  • Crew and cost — does it raise the peak, or spend more?
  • Critical path and schedule health — did it trade one bottleneck for another, or add negative float?

If the numbers justify it, merge the scenario into the schedule. If not, you've answered the question and can leave it as a draft or delete it. Either way you decided with data.

Tip: Compare on the same dashboard or chart rather than from memory: same cards, same axes, so the scenario is the only thing that changes.


What to do next