> 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/employee-availability.md).

# Employee Availability

Maitre'D employee availability report shows availability for all T\&A employee for both shift. This report shows the number of hours employees have already worked if they have punched in and punched out for the time period shown on the report From the report filter window, select the employee(s) and task(s) to be included in the report.

#### The following is a sample of the employee availability report:

<img src="https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/ReportCenter/EmployeeAvailability_files/image001.png" alt="" height="594" width="811">

**Employee name:**

T\&A employee name

**Phone:**

T\&A employee telephone number

**M T W T F S S:**

M= Monday, T= Tuesday, W= Wednesday, T= Thursday, F= Friday, S= Saturday and S= Sunday.  For both shift, ٱ= employee not available and ■ = employee is available

**Reg:**

Regular hours worked by the employee

**Over.:**

Overtime hours worked by the employee

**Doub.:**

Double hours worked by the employee


---

# 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/employee-availability.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.
