> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/centre-de-documentation-payfacto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/centre-de-documentation-payfacto/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-t-and-a/coffee-break-by-employee-name.md).
# Coffee Break by Employee Name
Maitre'D coffee break by employee name report shows each employee break and its length. The report lets you know if the employee is still in its coffee break and if not, the report shows a comment to let you know if it was shorter or longer than your T\&A pre-defined coffee break time. The report is sorted by employee name.
From the report filter window, select the appropriate week or custom date and employee(s) to be included in the report.
#### The following is a sample of the coffee break by employee Name report:
**Begin:**
Coffee break start date and time
**End:**
Coffee break end date and time
**Length:**
Coffee break length
**Completed:**
A check mark in that field indicates the employee completed the break
**Comment:**
Remark that lets you know if the break was shorter or longer than your T\&A pre-defined coffee break time.
---
# 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.payfacto.com/centre-de-documentation-payfacto/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-t-and-a/coffee-break-by-employee-name.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.