> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/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/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-sales/weekly-summary-of-meals-by-time-period.md). # Weekly summary of Meals by Time Period Maitre'D weekly summary of meals by time period report shows meal count information by half-hour time slices for the week requested. From the report filter window, select the appropriate start date and time slices to be included in the report. The following is a sample of the weekly summary of meals by time period report: ![Sample - Weekly Summary of Meals by Time Period](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/ReportCenter/Sample-WeeklySummaryOfMealByTimePeriod.jpg) For each half-hour of each mode of each day of the week, this report shows the meal count. **From-To** Beginning and end of half-hour time slice. **Sun to Sat** Sunday through Saturday. **Total** Total meals of that half-hour slice for the week. **Mode** Total meals for that mode on that day and for the whole week. **Total** Total meals of that day. --- # 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/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-sales/weekly-summary-of-meals-by-time-period.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.