> For the complete documentation index, see [llms.txt](https://docs.diracinc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diracinc.com/operator-guide/operator+/operator-input.md). # Operator Input This will cover the options for giving feedback as an Operator+ user ## What is Operator Input? Operator Input is information collected during runs that is passed from operators to engineers. This information can help engineers inform future revisions by providing context on errors, improvements, and other relevant information. Operator input is classified into 4 categories: * **Work Notes:** Used for observations and abnormalities found during a run

Symbol for Work Notes

* **Suggested change:** Used to recommend changes to an instruction's implementation

Symbol for suggested change

* **Non-Conformance:** Used to report non-conformances and other errors preventing completion of a step

Symbol for non-conformance

* **Required/Recorded Data:** Used to input data required by an engineer for completion of the step. Data outside of the acceptable range will generate a non-conformance

Symbol for recorded/required data

## Submitting Input To submit input, click the feedback icon corresponding to the feedback you wish to deliver, which you can find at the top of the viewer. This will prompt you to type and submit your comments in a text box, after which you can confirm your submission to complete the process.
## Undo Progress As an Operator+ user progresses through a work instruction, they can undo a completed step by clicking the back arrow during a run. This reveals an undo button, which, when clicked, requires confirmation and for the user to enter a reason for undoing. This reason will appear as a work note in the runs dashboard.