# Demand and coverage

> **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).

Set [demand](https://chrona365.com/glossary/demand-based-scheduling) for the workers you need, then compare it with scheduled shifts on the board.

## Add demand

1. Open **Demand** and add a row for each need on your scheduler.
2. Set required **Start**, **End** and **Min headcount**, then **Role** and **Max headcount** as needed. Times must be on the hour or half-hour, end after start, and maximum at least minimum. Auto Schedule stops and identifies invalid rows in the period.
3. Choose **Group** and **Subgroup** for group-specific shifts, made and filled with that group's workers. Leave both empty for scheduler-wide demand in its own strip.

Where demand rows overlap, the board takes the highest minimum and the lowest maximum.

## The coverage strip

On the **Timeline** layout, a **Coverage** strip above each group shows every half hour as met, under or over. You cannot edit the strip. Change the shifts or the demand, and it follows.

## Demand drivers

A driver is a number that sets how many shifts you need, such as guests per service or orders per day. A template with a driver makes more shifts when the number goes up. Each scheduler has its own drivers and their values.

1. Open **Demand drivers** and add a driver: its **Name**, **Unit name**, **Counted per** (**Day**, **Service**, **Week** or **Custom**) and its **Scheduler**.
2. In the driver's **Values** grid, add a value for each window: its **Window start** and **Value**. For a driver counted per service, add the **Service name**.
3. On a template, set **Demand driver**, then **Shifts needed** for each **Per driver units**. For example, 1 shift per 20 guests.
4. Set the limits: **How many** is the fewest shifts the template makes, and **Maximum** the most. Leave **Maximum** empty for no limit.
5. Set **Distribution**: **Per occurrence** applies the count to each day, and **Across window** spreads it over the driver's window. **Rounding** sets how a part shift rounds: **Round up**, **Nearest** or **Round down**.

Then select **Generate** on the board. See [Shift types, coverage and Generate](https://chrona365.com/docs/workforce/templates).

## Staffing standards

A staffing standard sets the hours each role needs for each unit you count, every day. **Generate** adds open shifts until the hours are met.

1. Open your [scheduler's settings](https://chrona365.com/docs/workforce/scheduler-settings#staffing-standards) and go to **Staffing standards**. In **Staffing counted per**, pick the demand driver that holds your count, such as Residents, and select **Save**.
2. Select **Add standard**. Pick the **Group** (and a **Subgroup** if you want one) and the **Role**, and enter the hours per unit. Pick **All groups** for a standard on your whole scheduler. To limit a standard to one shift type or one site, select **Limit to a shift type** or **Limit to a site**. To count a standard by another of your demand drivers, select **Use another demand driver**. To round the shifts another way, select **Change rounding** (see [Rounding](https://chrona365.com/docs/workforce/demand#rounding)).
3. The standards show as a table: **Group**, **Subgroup**, **Role** and the hours per unit each day. The **Demand driver**, **Shift type** and **Site** columns show only when a standard uses them. **Rounding** shows only when a standard rounds other than up.

An agent can configure **Staffing counted per**, standards and the staffing check after your confirmation. See [Install with an agent](https://chrona365.com/workforce/install-with-an-agent).

Your own system can send the driver's values, one for each day, group and subgroup. A group with no value of its own adds up its subgroups' values. A day with no value uses the latest earlier one. To add a value by hand, select **Add value** under the table named after the driver. A value for a day and group that has one replaces it.

When you select **Generate**, each standard multiplies the day's value of its demand driver by its hours. **Generate** adds whole shifts to that role's coverage rows for the group, in proportion to their counts, until the shifts' paid hours reach the need, or as the standard's **Rounding** says. A group with no coverage row for the role gets shifts on the role's shift types, spread evenly. Shifts added for a standard are required, even above a coverage row's **Maximum**. A standard on all groups adds only what the group standards leave short.

On the **Roster** layout, read each group's rows under its workers:

| Row or value | Meaning |
| --- | --- |
| **Filled / needed** | A check if every day's shift is filled, otherwise its open count, such as **3 open**. |
| **Against standard** | Planned hours (filled and open) against required hours, shown in whole hours. **−16 h** is 16 hours short; **Generate** adds open shifts. A dash means the standard is met. |
| **No value** | No driver value for that day; the tooltip says where to add it. |

Each role counts separately; any role short makes the day short. The tooltip gives each role's short/over hours, planned and filled hours, standard in hours and per unit, and the day's driver value. All shift types count. Ungrouped assigned shifts count for their worker's home group, as in **Filled / needed** and **Generate**.

### Rounding

The need of a standard often works out to part of a shift: 60 hours on 8-hour shifts is 7.5 shifts. **Rounding** says what **Generate** does with the part:

| Rounding | 7.5 shifts | 7.51 shifts | 7.4 shifts |
| --- | --- | --- | --- |
| **Round up** (empty) | 8 | 8 | 8 |
| **Nearest** | 8 | 8 | 7 |
| **Round down** | 7 | 7 | 7 |
| **Up from .51** | 7 | 8 | 7 |

**Up from .51** carries the shifts to two decimals and rounds up from .51. When shift lengths differ, **Generate** rounds what is still short in shifts of the length of the next shift it adds. **Against standard** on the **Roster** reads within the standard when the plan is short by less than **Rounding** needs to add one more shift.

Example: New Jersey's proposed rule for nursing homes (New Jersey Administrative Code (N.J.A.C.) 8:39-25.3) counts certified nursing aides (CNAs) from the midnight census. It carries the result to two decimals and rounds up from .51. To roster it with 8-hour shifts:

1. Make a demand driver, such as Residents, and send it each day's midnight census as that day's value. Pick it in **Staffing counted per**.
2. Add three standards for the role CNA, each limited to its shift type, with **Rounding** set to **Up from .51**: Day 1.0, Evening 0.8 and Night 0.57 hours per resident.
3. With 60 residents, **Generate** gives 7 Day aides (7.50 shifts), 6 Evening aides (6.00) and 4 Night aides (4.28).

When a value falls, a role can have more shifts than its standard needs. The day then shows the hours over, for example **+8 h**, so you see it without the tip. A day shows over only when **Generate** would remove or flag a shift of the role that day; a plan that is less than one whole shift above the standard counts as within it. **Generate** removes open shifts nobody has changed and flags the shifts someone works, pinned or changed. The tip only shows this. **Generate** makes the changes when you select it.

## The staffing check

The staffing check updates open shifts after driver values change. With **Chrona Scheduled tasks** on, it runs every **Check staffing every** hours (1–24; empty means 1). For an immediate check, open **Auto Task Log** and select **Run now** on **Staffing check**. See [Auto Task Log](https://chrona365.com/docs/workforce/auto-task-log) to turn on the flow.

The check reads each scheduler that has a driver in **Staffing counted per**:

- The first check adds no shifts. It records the counts, and later checks compare with them.
- When a value rises, the check adds open shifts for the rise only. It compares each value with the value it read at its last check. A value you raise and lower again between two checks adds nothing. It does not add back a shift that you removed.
- When a value falls, the check removes nothing. The day shows the hours over the standard, for example **+8 h**, and you decide what to remove.
- A shift that has started stays as it is.
- In a published roster period, the check publishes the shifts it adds at once.

### Fill new shifts automatically

When **Fill new shifts automatically** is on in your scheduler's settings, **Auto Schedule** fills the open shifts each check adds. It is on unless you turn it off.

- Only the shifts the check added change. Every other shift stays as it is.
- Each filled shift shows **Auto scheduled** in its details.
- A shift that nobody can work stays open.
- In a published roster period, the filled shifts are published at once.
- When **Auto Schedule** is already running for the scheduler, the check adds the open shifts and fills them at its next run. The **Auto Task Log** says so.

**Auto Schedule** needs Chrona to be connected, as on the board. The check sends the same data as a run from the board: see [What a run sends](https://chrona365.com/docs/workforce/auto-schedule#what-a-run-sends).

In your scheduler's settings, the hint under **Check staffing every** says when the check last read the values: **Last checked**. **Clean-up of old values** deletes values older than 90 days: see [Auto Task Log](https://chrona365.com/docs/workforce/auto-task-log).

## Shifts made from demand

When your scheduler has demand and shift types that list the demand's role, **Auto Schedule** makes the shifts the demand needs. A shift someone works is saved with that worker. When nobody can work a shift the demand needs, it is saved as an open shift that needs cover, and your workers can pick it up like any open shift. Shifts the run makes but does not need are not saved.

With self-rostering, the pick window's opening makes the demand shifts as open shifts and publishes them, so your workers can pick them before the roster is made. See [Self-rostering](https://chrona365.com/docs/workforce/self-rostering).

Run **Auto Schedule** again, and it makes the demand shifts again: it keeps the shifts you pinned, makes the others again, removes the open shifts that are now covered, and adds open shifts only for what is still short. The review lists the shifts it adds and removes before you select **Apply**.

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