> For the complete documentation index, see [llms.txt](https://documentation.civalgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.civalgo.com/documentation/operations/validating-worked-hours-payroll.md).
# Validating Worked Hours - Payroll
This feature lets you **review and validate the hours worked by employees before payroll processing**. The tool provides an overview of weekly hours and highlights daily reports that require validation.
#### **Prerequisites**
None
### **Tracking Worked Hours – Overview Section**
In the **Overview** section under the **Payroll** tab, go to the **“Worked Hours”** tab.
Here you will find:
* An **overview of weekly hours** worked by your resources based on the selected date range.
* A **list of your employees** with the total hours per week.
* A **“Daily Report Status” column** showing if some reports still need validation.
* A **“Pensions” column** showing weekly pensions selected.
* **Filters and sort options** for each column to help you analyze data more effectively.
**Tip:** If you hover your cursor over a cell in the **“Daily Report Status”** column, a tooltip will appear showing:
* The **list of daily reports** for that employee and the status of each report.
* The **number of hours entered per day.**
* A quick overview of the **team name, team lead, shift, and daily report title** for that period.
This helps you quickly identify incomplete or unvalidated entries and ensure accurate time entry before exporting to payroll.
---
# 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://documentation.civalgo.com/documentation/operations/validating-worked-hours-payroll.md?ask=&goal=
```
`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.