> 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/activity-site-block-duration.md).

# Activity Site / Block Duration

See the hours, units and cost per activity on each site and block, with a chart, saved pivot views and an exportable table

This report shows how many hours employees spent on each activity, per site and block, per day, with the units captured and the cost. Use it to see where work happened and what it cost, for example how many employees worked on each site.

## Open and generate the report

1. Navigate to [**Reports > Clocks and Activities > Activity Site / Block Duration**](https://app.allwage.com/#/reports/time/activity-block).
2. Select the date range.
3. Optional: under **Filter Activities**, choose the activities to include. Leave it empty for all activities.
4. Optional: under **Graph Grouping**, choose how the chart groups the hours: **Activity**, **Activity Category** or **Employee Team**.
5. Click **Generate**.

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

## Chart

The chart shows, for each group you chose under **Graph Grouping**, the total hours, the number of different employees and the total cost for the date range.

## Pivot views

Below the chart, a pivot table summarises the same data. Choose a view in the drop-down above it:

* Views marked **D** are default views that AllWage provides.
* Other views were added for your business.
* **Add new** creates your own view: choose the rows, columns and values to group and total, for example sites as rows and the number of employees as the value.

The text next to the drop-down describes the selected view. See [Custom Reports](https://help.allwage.com/fundamentals/report-summary/custom-reports.md) for how the editor works.

## Table and export

The table at the bottom has one row per employee, activity, block and day, with these columns: **Date**, **Activity Category**, **Activity**, the site, **Block**, **Area**, **Produce**, **Employee Group**, **Employee Name**, **Employee Number**, **Hours**, **Units**, **Calculated Units**, **Cost (R)** and **Rate/Hour (R)**.

* **Columns** shows more columns, such as **Activity Code**, **Block Size (Ha)**, **Employee Label**, **Target Interval (H/D)**, **Calc. Unit Target** and **Unit Target**, or hides them.
* Type in the search box to filter the rows.
* **Export** downloads the table to Excel.

If hours or units look wrong, use **Clocks data review** or **Activities data review** at the bottom of the report to check the captured records.


---

# 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/activity-site-block-duration.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.
