> For the complete documentation index, see [llms.txt](https://help.allwage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.allwage.com/modules/time-and-attendance/reports/employee-activity.md).

# Employee Activity

See the units each employee captured per activity, per day, with totals and averages, optionally split by site or block

This report shows the activity units captured for each employee, with a column for each day. Use it to compare employees' production on an activity over a period.

Only activities with units captured against them (activity items) appear. Hours on an activity without units are in the [Activity Site / Block Duration](https://help.allwage.com/modules/time-and-attendance/reports/activity-site-block-duration.md) report instead.

## Open and generate the report

1. Navigate to [**Reports > Clocks and Activities > Employee Activity**](https://app.allwage.com/#/reports/time/activity-item).
2. Select the date range.
3. Optional: tick **Site / Block Grouping** to give each site or block its own row.
4. Click **Generate**.

You need permission to read employee clocks to open this report.

## Columns

There is one row per employee and activity, or per employee, activity and site or block when **Site / Block Grouping** is ticked.

* Employee and activity details: **Employee Number**, **Name**, **Team**, **Activity Category**, **Activity** and, with grouping, **Site / Block**. **Label 1**, **Region**, **Area**, **Produce** and **Variant** can be added under **Columns**.
* One column per day with the units captured that day.
* **Total**: all units in the date range.
* **Calculated**: the total multiplied by the activity's unit factor, in its calculated unit (for example rows converted to metres).
* **Average**: the total divided by the number of days the employee captured units on the activity.
* **Average Absent** (under **Columns**): the total divided by all the days in the report that have any units, so days the employee didn't capture units count as zero.

Example: over a report with 5 days of data, an employee captured 40, 50 and 60 rows on 3 days. **Total** is 150, **Average** is 50 and **Average Absent** is 30.

## Export

Click **Export** above the table to download it to Excel.

To check or correct the captured units, use **Activities data review** at the bottom of the report.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.allwage.com/modules/time-and-attendance/reports/employee-activity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
