# Documents module

> Work instructions, drawings, and certificates at the machine or workstation, always the current version, tied to the order and the operator in front of it.

URL: https://optipeople.com/modules/documents

## The right instruction, at the right place

Work instructions, drawings, and certificates where the work happens: at a machine, a station, a line, a warehouse, or a lab, in the version that applies to the job in front of the person doing it.

## What changes

- **Current** One approved version, everywhere
- **Paperless** Binders off the shopfloor
- **Traceable** Who read what, and when

## Documentation on the floor goes stale quietly

Instructions live in binders by the machine or workstation, in a shared drive nobody trusts, and in the head of whoever set the job up last time. When a drawing is revised, the old print stays on the floor until someone notices. Tying documents to the machine and the order means the operator opens what applies right now, and the revision reaches the floor the moment it is approved.

## Documentation that follows the work

- **Instructions at the machine or workstation**: Open the setup sheet, drawing, or work instruction from the panel at the machine or workstation, filtered to the order being run.
- **Versions that cannot drift**: One current version, one history. Approve a revision and the floor has it immediately, no printed copy outliving it.
- **Find it by machine, workstation, or order**: Documents are linked to machines or workstations, items, and orders, so finding the right one does not depend on knowing a folder structure.
- **Read and understood**: Ask for confirmation on the documents that need it, and see who acknowledged which version and when.
- **Audit-ready by default**: Certificates, calibration records, and signed-off instructions sit with the production data they belong to, ready when an auditor asks.
- **Panel, tablet, or phone**: The same document set on the operator panel, on a tablet at the line, and on a phone in maintenance.

## How it works

1. **Upload**: Bring in instructions, drawings, and certificates, and link them to the machines or workstations, items, and orders they apply to.
2. **Publish**: Approve a version and it becomes the one the floor sees. Earlier versions stay in the history, not on the machine or workstation.
3. **Confirm**: Operators open what applies to the job and acknowledge the documents that require it, logged with the production record.

## Documents next to the data they describe

The instruction for a job, the stops registered on it, and the quality checks that followed all sit on the same order, so a question about what happened has one place to go.
