> 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/manual-production-progress-tracking.md).

# Manual Production Progress Tracking

### Benefit

Allows tracking of a manual station to monitor progress and set targets.

### Setup

Each station to be monitored must have a production schedule. This can be created via Schedule Management page or Quick Schedule Start.

All SKUs to be produced must have a Performance Target 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.

TV screens installed on shop floor and a tablet for each station to be monitored.

### Daily Workflow

1. Schedules are added by production manager via schedule management or operator using Quick Schedule Start. Upcoming schedules will appear on Production Progress Chart 24 hours before planned start time.
2. Operator starts a schedule and inputs completed units via the tablet.
3. Production Progress Chart will display whether production is on or behind target and provide an estimated end time. Giving operators and production managers real-time progress of a schedule.


---

# 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/manual-production-progress-tracking.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.