# Team Versioning

### What is Team Versioning?

**Team Versioning** provides the flexibility to view metrics based on **how teams were structured during the selected time period**, preserving historical accuracy.

By default, Hivel metrics reflect the current team structure - meaning that past metric values are calculated based on **today’s team structure**, not how the team was structured historically.

**With Team Versioning enabled:**

* Historical data remains intact.
* Team member additions, removals, and transfer dates are respected.
* Metrics reflect who was actually part of the team during the selected date range.

This prevents productivity metrics from being retroactively distorted when team composition changes.

***

#### **🔍 Default Behavior (Without Team Versioning)**

* Metrics are always calculated using the **current team structure**.
* If an author moves teams, their past contributions are still shown under their **new team**, not where they were when the work was done.
* Only current state data is visible.
* Removing a team member from all the teams removes them from all views.
* Historical contributions are not time-aware.

**Example:**

* Author A was in Team B from Jan to Feb.
* In March, Author A is moved to Team C.
* You view Team B metrics from **Jan 15 – Feb 15**: 👉 Without Team Versioning, **Author A's contributions will not show** under Team B (since they are now in Team C).

***

#### **📦 Behavior With Team Versioning Enabled**

With Team Versioning enabled, Hivel utilizes **historical team structures** to calculate metrics. This ensures each metric reflects which authors were part of a team **at the time the work occurred**.

* Historical data is preserved.
* Visibility is filtered by the selected date range.
* Contributions remain visible for the period when the member was active.
* No new data for a team is shown after the member’s exit date from the team.

**Example 1:**

* Author A is in Team B (Jan–Feb), then moved to Team C in March.
* You view metrics for:
  * **Jan 15 – Feb 15**: ✅ Author A's contributions appear in **Team B** metrics.
  * **Mar 15 – Apr 15**: ❌ Author A's contributions do **not** appear in Team B metrics, but are part of Team C instead.

**Example 2:**

Team members: X, Y, Z

* X and Y are existing employees.
* Z joined the team on March 20, 2026.

Selected date range: February 2026

* Visible members: X, Y

Selected date range: Feb 22 – March 19, 2026

* Visible members: X, Y

Selected date range: Feb 22 – March 20, 2026

* Visible members: X, Y, Z

If Y exits the team on March 20, 2026:

* Y’s historical contributions remain visible for periods prior to March 20, 2026.
* No new activity from Y is shown from March 21, 2026.

**Example 3:**

Assume Teams A and B both had 10 members in January 2026.

* 3 members were removed from Team A effective January 31, 2026.
* 3 members were removed from Team B effective February 28, 2026.

If **February 2026** was selected and teams are viewed separately:

* Team A shows **7** total members (the 3 members already left).
* Team B shows **10** total members (removal of 3 members occur at the end of February).

### Metric calculation note (duration sensitivity)

* Weekly metrics are normalized to a 7-day week.
* If a member was active for only part of a week (for example, 2 days) and then left the team or organization, the metric is still divided by 7.

As a result, that member’s weekly metric may appear lower than expected when viewed at weekly granularity.

***

{% hint style="info" %}
**Please Note:** The feature is based solely on user movement across teams, rather than the actual teams themselves. If a team is removed from Hivel, all the associated versioning data will not be retained.
{% endhint %}

### Summary and troubleshooting checklist

Team Versioning provides:

* Historically accurate reporting
* Date-aware visibility based on join and exit dates
* More reliable metrics and insights during team changes

If a dashboard or metric looks inconsistent, verify:

* The selected date range
* Members join and exit dates

#### **📌 Why Use Team Versioning?**

We recommend using Team Versioning to:

* Analyze metrics accurately for historical team performance.
* Avoid misleading trends caused by team structure changes.
* Support performance reviews and retrospectives based on actual team dynamics at the time.

If you’re unsure whether Team Versioning is enabled or want to enable it, reach out to [<mark style="color:purple;">support@hivel.ai</mark>](mailto:support@hivel.ai).


---

# Agent Instructions: 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.hivel.ai/set-up/team-versioning.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.