> 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/platform-onboarding/quick-start/scheduling.md).

# Scheduling

Under SCHEDULING in your Busroot Menu please follow these steps to start scheduling: 

#### ADD PROD. SCHEDULE 

1. To manually enter a schedule click ‘Add New’. 
2. You will need to select the following to setup a schedule 
3. Station 
4. SKU type
5. Individual SKU 
6. Work order ref 
7. Planned start time 
8. Actual start (at a set time or by the operator using a tablet) 
9. Order type 
10. Depending on selection, also quantity and/or time
11. If you want to set non-production schedules you can select the tab to enter schedules

#### UPLOADING A CSV WITH MULTIPLE SCHEDULES

4. You can also upload a CSV or XLSX of a group of schedules. If you send your sheet to the Busroot team they will configure Busroot to extract the required information. With this system there are two points to be aware of:
5. If the station is not in Busroot, no schedules for that station will be uploaded. 
6. If the SKU does not exist in Busroot one will automatically be setup. <br>

For more information click on a link below:&#x20;

[Scheduling ](https://docs.output.industries/features/scheduling)

[OEE Analysis](https://docs.output.industries/features/oee-analysis)

[Adhoc Production Tracking](https://docs.output.industries/archive/workflows/adhoc-production-tracking)

<br>


---

# 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/platform-onboarding/quick-start/scheduling.md?ask=<question>&goal=<endgoal>
```

`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.