> For the complete documentation index, see [llms.txt](https://docs.output.industries/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.output.industries/archive/workflows/adhoc-production-tracking.md). # Adhoc Production Tracking Operators using the 'Quick Schedule Start' to record what production they are currently working on. ### Benefits Allows access to valuable Busroot features without the need for a strict scheduling system. By adding a simple SKU list, production can be tracked at a granular level. ### Setup All SKUs to be produced must be uploaded into Busroot, for basic production count data no performance target is required. For more detailed data at SKU level, a Performance Target must be set. This is the ideal rate that the SKU should be produced, based on Cycle Time, Units per Minute, Units per Hour or an Independent Process Speed. For stations that have a typical cycle time for the machine, a target can be set at station level. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.output.industries/archive/workflows/adhoc-production-tracking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.