# Scenarios

> **Set up with an AI agent:** Connect Chrona MCP for documentation, setup guidance and configuration recipes. Server: https://mcp.chrona365.com/mcp (Streamable HTTP; authentication: None). Your agent needs separately authorized Dataverse tools to apply changes. In Copilot Studio, after importing Chrona, add the Chrona Scheduler connector to your agent alongside Microsoft’s Dataverse tools. [Connection guide](https://chrona365.com/workforce/install-with-an-agent).

Use [Scenarios](https://chrona365.com/glossary/scenarios) to compare strategies or a what-if change for the same roster period, with cost, coverage and team outcomes side by side.

## Open it

On the board, open **Actions** and select **Scenarios**. The page opens over the board, for that scheduler and its roster period. The board runs each scenario, so open **Scenarios** from the board.

**Current setup** runs as soon as the page opens: your setup and your goal order, planned again.

## Add columns

- **Compare strategies** adds three columns: **Optimize for: Lowest cost**, **Optimize for: Happiest team** and **Optimize for: Best coverage**. Each runs with that preset's goal order. See [Goals](https://chrona365.com/docs/workforce/goals).
- **New what-if** adds one change to your setup:
  - **Someone away**: a worker and the days they are away, inside the period.
  - **Extra workers**: how many, up to five, with their roles and an agreement.
  - **Rate change**: a percent, from −50% to +100%, for everyone or one role.

Every column plans the same shifts, then fills them. Only the change named at the top of the column differs. Close a column with its close button; **Current setup** stays.

## Read the results

The table **Result for** the period has one row for each figure:

| Row | What it counts |
| --- | --- |
| **Shifts filled** | Required shifts with a worker, of all required shifts. |
| **Must rules broken** | Must rules the roster breaks. |
| **Should rules broken** | The agreements' Should rules the roster breaks. |
| **Wages** | Wages at hourly rates, with agreement overtime, and the change from **Current setup**. |
| **Overtime** | Its cost and its hours. |
| **Liked shifts** | Shifts in a worker's preferred time. |
| **Requests granted** | **Unpreferred** days left free, of all Unpreferred days in the period. |
| **Weekend load spread** | The most weekend days one worker works, less the fewest. |
| **Workers near contracted hours** | Workers within one shift of their contracted hours, of all with contracted hours. |

**Best** marks the best value in a row when the columns differ.

Under the table, the chart **Wages against team happiness** puts each column on one dot: wages across, team happiness up. **Current setup** is the dark dot. Team happiness is liked shifts and granted requests, as a share of all shifts worked and all requests made. **Reading this** explains the figures in plain words.

## Use a roster

You need permission to change shifts.

1. Select **Use this roster** on **Current setup** or a strategy column. Scenarios closes and the board opens its proposal.
2. Review, then **Apply** or **Discard** as for [Auto Schedule](https://chrona365.com/docs/workforce/auto-schedule#review-the-proposal). Figures can differ from the column because the board compares with your current roster.

A what-if column is a preview only: its roster rests on a change you have not made. Make the change on the board, then plan again.

Scenarios change no data until you apply a roster, and the page keeps no results: it runs its columns again each time it opens.

## Billing

Scenario runs count workers as Auto Schedule does. The extra workers of a what-if are not billed. See [Plan and billing](https://chrona365.com/docs/account/billing).

---
Product: Workforce Scheduler
Language: English
Canonical: https://chrona365.com/docs/workforce/scenarios
