This step waits for a person. It is the plain-language task: tell somebody what to do, and make them write down what they did.
It appears in the Add Step list as Instruction.
| Automatic? | No - a person does it and writes up what they did |
| Who does it | The person it is assigned to |
| Needs first | Nothing |
| Produces | The completion notes |
| Where you work it | The work order page, then the instruction screen |
What it does
Not everything in a job is a document or a stock movement. Inspect this. Phone the customer. Photograph the damage before you start. Label the crate.
This is the step for all of it. It asks for nothing up front - it consumes no fields at all, which is why it can sit anywhere in any WorkFlow without needing something before it.
Its one real output is the completion notes: what the assignee actually did. That is published, so a later step or a person reading the run can see it.
Completing it
- It completes when the assignee marks it done. Notes are required - it will not close on a blank, because an instruction with no account of what happened is not a record of anything.
When not to use it
- The work is a repair - a Repair Task records parts, an outcome and a unit, which an instruction cannot.
- You need a decision, not an action - that is an Approval.
- You need stock moved - that is a Move Order. Writing 'go and fetch six of these' in an instruction leaves the stock records untouched.