> For the complete documentation index, see [llms.txt](https://docs.logilica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.logilica.com/metrics-and-reports/team-management/team-pulse.md).

# Team Pulse

## Purpose

The Team Pulse is a team manager's view to stay on top of the team's activity. It shows the most recent progress of your team across tickets and PRs, and highlights some of the risks to delivery as well as team health issues to watch out for. This report also serves as a communication basis with a team to sync on progress and concerns.

{% hint style="success" %}
**Improvement Actions**: The Pulse view highlights a number of delivery risks to watch out for, as well as the load of individual staff. Some level of risk is normal, but unexpected high levels should be investigated. Similarly, if more/less activity in the timeline view is expected, the reasons should be addressed with the team. Some actions might be to change resourcing, set expectations, and distribute workload more effectively.
{% endhint %}

## Explanations

Some of the information in this report includes:

**Cycle time**: The PR lifecycle time from the first commit to being merged/closed averaged out across all teams.

**Work Type**: The predominant type of code changes — adding new code, reworking recently written code (your own or others'), or maintaining older, established code.

**Alerts**: Risk coming out of the [planning stage](/metrics-and-reports/planning/ticket-activities-risks.md) and the [coding activities](/metrics-and-reports/code/code-activities-risks.md). This combined view gives a good idea of where to focus the attention and where potential improvement in the process should be made.

**Timeline Ticker**: Shows the most recent activities on both tickets and PRs. An activity is defined as a workflow stage change for the [tickets](/metrics-and-reports/planning.md) and [PRs](/metrics-and-reports/code.md) owned by the team.

**Team Overview**: This view shows the activity and load of each team member, including:

* **WIP**: the number of open PRs or assigned tickets to the team member
* **Reviewer**: the number of open PRs the team member is assigned to as a reviewer or made a review comment on
* **Todo**: the number of tickets in the backlog assigned to the team member
* **Done**: the number of tickets closed and PRs closed/merged by the team member
* **Blockers**: the number of items that potentially indicate a team member being blocked. This includes a complex review, long PR response time, long ticket response time, sprint overrun, or unplanned work. See also the [Glossary](/metrics-and-reports/glossary.md) for details.
* **Load**: the load of each team member is categorised as
  * **available**: no open tickets or PRs
  * **active**: a healthy number of open tickets and PRs
  * **overloaded**: open tickets and PRs combined exceed a pre-defined healthy capacity

## Good to Know

The Pulse view serves as an entry point for a conversation with the team for process improvements. It is not intended as a performance tracker. Note, the timeliness of the data is also affected by the scan frequency as defined by your organisation, which is 24h by default. The advantage of this view is that all the information is computed and aggregated without any overhead by the team itself and creates minimal interruption to their daily activity.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.logilica.com/metrics-and-reports/team-management/team-pulse.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.