> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aioncx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Metrics and terms

> Understand Atlas forecast groups, scheduling groups, demand, coverage, shrinkage, findings, and evidence.

Use these definitions when reading Atlas results and configuring workforce work. Check the selected metric's own calculation, scope, exclusions, and time basis before comparing values.

| Term | Meaning |
| - | - |
| Workspace | The operational scope whose data, configuration, and permissions apply to your work |
| Agency | A named area of operational work in Atlas, such as Resource Management or Knowledge Operations |
| Interaction | A durable conversation identity, which can have multiple input and analysis revisions |
| Definition | A published, versioned specification for a selected analysis and its output |
| Finding | A structured observation produced from source material |
| Evidence | The source passage or record supporting a finding or result |
| Forecast group | The defined work scope, forecast configuration, and service targets used to plan demand |
| Scheduling group | The people and planning configuration used to prepare schedules |
| Forecast horizon | The number of future intervals to predict |
| Forecast point | One predicted future interval for one target series; additional quantiles describe that point |
| Grain | The interval of a series, such as 15 minutes, an hour, or a day |
| Staffing requirement | The number of people required over an interval under the selected demand and service assumptions |
| Net demand | The underlying staffing demand before grossing up for the configured loss assumptions |
| Gross requirement | The staffing requirement after the applicable loss assumptions and rounding |
| Productive coverage | Productive scheduled supply compared with exact net demand, accounting for the explicitly assessed residual loss |
| Residual unplanned shrinkage | The additional loss remaining after scheduled nonproductive activity has already been accounted for |
| Adherence | Comparison of actual activity with the published schedule and its activity mapping |
| Occupancy | A workload-to-capacity ratio whose included work, available time, and interval must be stated by the selected metric |
| Quantile | A value at a selected level of the forecast distribution, where the method supplies it |

## Time and scope

A forecast, actual, or staffing requirement belongs to a particular metric, work scope, interval, and timezone. Compare like scopes. Daily and weekly boundaries follow the configured timezone, including daylight saving time.

A full-interval forecast and actual work observed so far are different quantities. Current intraday observations may still be provisional.

## Missing values

An observed zero is a measured value. Missing history, unreadable evidence, and work still processing are separate states. Resolve the stated limitation before using a missing value as a planning input.

## Avoid counting loss twice

Scheduled meals, breaks, and other nonproductive activities already reduce productive supply. Residual unplanned shrinkage represents the remaining additional loss. For example, a residual of `0.10` means a ten-percent additional loss assumption; it does not describe total shrinkage unless that is how the full calculation has been defined.

## Interpret a forecast

`predicted_value` is the operational point returned by the method. It may differ from P50. Inspect `point_statistic`, the returned quantiles, interval fields, and method metadata before interpreting it as a mean or median.

See [forecasting](https://docs.aioncx.com/mach1/forecasting.md) for numerical examples and [Resource Management](https://docs.aioncx.com/atlas/resource-management.md) for the staffing workflow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.