> 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/activity.md).
# Activity
Maitre'D Activity report shows each
From the report filter window, select the appropriate day of the week, time period and time slice to be included in the report. Take note we only go back 7 days.
#### The following is a sample of the activity report:
**Beginning:**
Beginning time your time slice
**End:**
Ending time of your time slice
**Sales:**
Net sales
**Customers:**
Amount of customers
**Labor hours:**
Total labor hours worked by all employees that were clocked in for the time slice.
NOTE: The minutes are printed as percentage of an hour.
**Salary:**
Payable salary for all employees that were clocked in for that time slice
**Labor cost:**
Salary divided by Sales multiply by 100
**Average / Customer:**
Average $ amount per customer seat. Sales divided Customers
**Production ratio:**
Sales divided by Labor Hours
**Customers ratio:**
Customers divided by Labor 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/activity.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.