Scenarios

A scenario is an alternative version of the plan: a copy branched from the live plan at a given moment, which you edit without anyone else seeing the changes. Under the hood a scenario is a draft — it appears in the drafts list with a branch-point badge, and shares its tooling with the drafts module.

Creating and working in a scenario

New scenario needs only a name, and optionally a production — without one, the scenario is org-wide. The branch point is set at that moment, and is the baseline the comparison is computed against.

The scenario tabs: Overview with the feasibility verdict and Run feasibility check, Report with the findings, and the three merge tabs below.

Diff, cherry-pick, and conflicts

• Diff — every change against live, grouped as Added, Modified, and Removed, with the field changes visible.
• Cherry-pick — the same list, but with Apply and Reject per change. Applying a change writes it to the live plan right there.
• Conflicts — when the live plan has moved underneath the scenario, fields where both sides changed are flagged. Choose Live (theirs) or Draft (mine) field by field — or “keep all” one way — and the merge base advances.

Three-way merge

The comparison is three-way: the branch point, live, and the draft. If only you moved a field, it’s a clean change; if live moved the same field a different way, it’s a conflict. Two identical moves are no change at all.

Merging everything

Merge all into live takes the whole scenario in one operation: allowed changes are written, changes that need approval become requests, and conflicts are skipped with a prompt to resolve them first. Only when nothing remains is the scenario marked published.