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

# Analytics

> How your team's Review backlog, review time and friction move over time.

> [!TIP]
>
> **Admins** can see Analytics. See [Roles](https://support.duna.com/roles.md#analytics).

Analytics shows how your team's [Review](https://support.duna.com/managing-reviews.md) workload and performance move over time. You find it under **Analytics** in the left sidebar. It has two pages, **Capacity** and **Performance**, which share the same period and filters. Figures update hourly, and every figure compares with the period of the same length before it.

## Capacity

Capacity answers whether your team keeps up with the work that arrives: the backlog at the end of each day, week or month, and the Reviews that entered and left it in between.

| Figure | What it counts |
| - | - |
| **Backlog** | Reviews waiting on your team: open, or awaiting a [Sign-off](https://support.duna.com/sign-offs.md). Reviews waiting on the [Connection](https://support.duna.com/connections.md) after a [Follow-up](https://support.duna.com/follow-ups.md) are not in the backlog. |
| **Reviews in** | Reviews that entered the backlog in the period: **created**, plus **resumed** after the Connection answered a Follow-up. |
| **Reviews out** | Reviews that left the backlog in the period: **finalized** (accepted or declined), **returned** to the Connection with a Follow-up, and **cancelled**. |
| **Backlog change** | Reviews in minus Reviews out, with the backlog at the start and at the end of the period. |

The backlog at the end of a period is the backlog at its start, plus Reviews in, minus Reviews out.

## Performance

Performance looks at the Reviews **finalized** in the period, the ones with an accept or decline decision.

### Speed

| Figure | What it measures |
| - | - |
| **Time to decision** | Days from the creation of the Review to its accept or decline, including the days the Review spent with the Connection on Follow-ups. Median over the Reviews finalized in the period. |
| **Connection waiting time** | The same clock without the days spent waiting on the Connection: queue, handling and Sign-off together. Median over the Reviews finalized in the period. |

Both are calendar days.

### Friction

| Figure | What it measures |
| - | - |
| **Straight-through Processing (STP)** | Share of finalized Reviews decided without sending the Connection a Follow-up. |
| **Application friction** | Finalized Reviews by rounds of Follow-ups before the decision: none (STP), one, two or more. A round is one return to the Connection, however many Follow-ups it carried. |
| **Internal friction** | Among finalized Reviews that had a Sign-off request: how many the signer approved without a return, returned once, or returned two or more times. |

## FAQ

> **Why is the backlog smaller than the list of open Reviews?**
>
> The backlog counts Reviews waiting on your team only. The [Reviews](https://support.duna.com/managing-reviews.md) page also lists Reviews that wait on the Connection after a Follow-up.

> **Why don't Time to decision and Connection waiting time add up?**
>
> Both are medians over different distributions. The median of the whole is not the sum of the medians of its parts.

> **Why does Internal friction show no data?**
>
> No Review finalized in the period had a Sign-off request. Choose a longer period, or check whether your policies require Sign-offs.

> **Why does Today show nothing on Performance?**
>
> Performance counts finalized Reviews. Until a Review is accepted or declined today, there is nothing to measure. Choose 7 days or longer.

> **Can I see the figures for one analyst?**
>
> Not yet. Analytics shows the whole organization, narrowed by Review type and Connection country.


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