> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-t-and-a/weekly-detail-by-employee-code.md).
# Weekly Detail by Employee Code
Maitre'D weekly detail by employee code shows information on each employee time sheet with a summary of worked hours for a specific week or date range. This report is sorted by T\&A employee code. From the report filter window, select the appropriate week or custom date, the employee(s) to be included in the report.
#### The following is a sample of the weekly detail by employee code report:
For each T\&A employee you get the following information:
**Task:**
Employee's task
**Date:**
Worked date
**Time In:**
Clock in time. The time is affected by your round up setup programmed under your Time & Attendance options and is also affected by an adjustment made by an authorized employee.
**Time out:**
Clock out time. The time is affected by your round up setup programmed under your Time & Attendance options and is also affected by an adjustment made by an authorized employee.
**Reg. Hours:**
Regular worked hours
**Over Hours:**
Overtime worked hours
**Double Hours:**
Double time worked hours
**Total hours:**
Total worked hours
---
# 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://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-t-and-a/weekly-detail-by-employee-code.md?ask=&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.