> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/reference/work-and-time-management/product/workforce-productivity/employee-scoring.md).

# Employee Scoring & Scorecards

We360.ai employee scoring & scorecards — a single, configurable monthly performance score that benchmarks each employee against team and company.

**Employee Scoring** turns the metrics you already track into a single, easy-to-read performance number. Each employee gets a monthly **score from 0 to 100**, and an **Employee Scorecard** that benchmarks them against their team and the whole company.

{% hint style="info" %}
Employee Scoring is an early-access (trial) feature. Availability and options may change — contact your account manager to confirm access.
{% endhint %}

## How the Score Works

The score is calculated **per month** from the metrics you choose to include. Each metric is normalized to a 0–100 scale and then combined as a **weighted average**, so you decide what "good" means for your organization. If no metrics are enabled, no score is produced.

Metrics you can enable and weight:

| Metric               | What it reflects                                                              |
| -------------------- | ----------------------------------------------------------------------------- |
| **Work Units**       | Output — from productive hours and/or task story points, or manually uploaded |
| **Productive Hours** | Productive time against a monthly target                                      |
| **Attendance %**     | Attendance against expected working days                                      |
| **Online Hours**     | Total time online                                                             |
| **Idle Penalty**     | Inverted — more idle time lowers the score                                    |
| **Distance Units**   | Travel distance, for field staff                                              |

## Configuring Scoring

A Tenant Owner configures scoring under **Settings → Scoring**. For each metric you set an **Enable** toggle and a **weight** (0–100), with a running total of the enabled weights.

Global options let you tune how the score is calculated, including:

* **Monthly Work-Unit Benchmark** — the output target a full score is measured against.
* **Story-Point Multiplier** and **Default Story Points** — how task points convert into work units (per-project overrides take precedence).
* **Kilometers per Distance Unit** — for field/travel scoring.
* **Extra Goal-Achievement Multiplier** — rewards hours logged above the daily goal (set to 1.0 to disable).
* **Default Effort Metric** — whether effort is measured by Productive, Online, or Active time.
* **Include calculated values in score** — turn off to use only uploaded work units (a Time-&-Materials style score).

{% hint style="warning" %}
Saving a change **recomputes all past months**, so scores update retroactively to reflect the new configuration.
{% endhint %}

## The Employee Scorecard

Each employee's scorecard appears on the **Scorecard** tab of their [User Details](/reference/work-and-time-management/user-interfaces/portal/universal-tools/user-detail.md) page. It brings the score to life with:

* A comparison of the employee against **team** and **company** averages (radar chart and table).
* **Monthly Attendance** and **Monthly Goal** summaries.
* **Activity** and **Productivity** trend charts.
* **Top Application** and **Wellness** panels, when those modules are enabled.

Scorecards can be exported for sharing in reviews.

## Getting Accurate Scores

For meaningful productivity-based scoring, set a **Company Goal** under **Settings → Productivity → Goals**. Without one, the score falls back to a default daily target, which may not match your expectations.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.we360.ai/reference/work-and-time-management/product/workforce-productivity/employee-scoring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.