A procedure defines how WorkSteps builds instructions for a family and kind of work. Prepare an approved working method, exact source fields and independently known outcomes before editing. A normal procedure and a rework procedure are separate draft lines.
Build a saved revision
- Open Procedures and create or select the intended family and kind. Check those identities before entering the definition.
- In Draft definition, maintain the complete supported structure. The first identification step must require the unit's exact identifier. Give each step, slot and requirement a stable identity.
- Declare required and optional slots in the intended order. Use Slot conditions for the supported structured conditions. Only declared fields and correctly typed values may be used.
- Define prerequisites and parameter-table keys explicitly. A selected lookup must find one exact row. Do not insert an approximate or fallback parameter to hide missing engineering data.
- Upload required step images, inspect their retained preview and reference, and supply useful alternative text in the definition.
- Save and read back the revision. Resolve every validation message before locking a candidate.
An option can select a different route for two units on the same job. Validate the whole option set, including fields that no current condition reads. Missing required values, unknown options, conflicting slots, missing prerequisites or missing parameters must block preparation rather than produce shortened instructions.
Preserve issued meaning
Change step or table content under a new revision. WorkSteps refuses different content under an existing pinned revision. Keep the old revision available for issued travellers. Editing the draft does not update issued work.
If the editor says the draft changed, do not overwrite it from your old tab. Reload, compare the saved work with your intended change and save a considered next revision. Tell the other author what you changed.
Prepare the review handover
Write examples covering selected and omitted options, exclusion conflicts, missing input and important parameter boundaries. State the expected route and requirements from the approved method. An example that merely copies calculated output cannot establish that the method is right.
Follow proof and publication. Include the family, kind, revision, changed steps, source assumptions and any operational concerns in the handover. A draft is not a production instruction until the required review, publication and assignment are complete.
Use a proposed condition deliberately
For an optional slot, choose its identity under Slot conditions. When available, Describe this condition in words (optional) and Propose a condition request a proposal. The screen states that each request contacts an external AI provider and counts against the displayed limits. Do not include personal or confidential details. A proposal does not change the working method by itself.
Read the proposal's restatement, condition and diagnostics against the approved method. Only the current eligible proposal offers Accept into the draft. Accepting a proposal saves a new revision. A structured condition edit remains unsaved until you use Save draft revision. Check the resulting saved revision before preparing proof. If another revision has replaced the proposal's starting revision, review the current draft instead of accepting old assumptions.
Under Step images, choose Image file and inspect the uploaded preview. Choose the intended Add to step value and Add. This puts the reference into the unsaved definition. Write its alternative text there and use Save draft revision. An uploaded preview on its own does not place the image in a saved instruction.
For a step requiring a tool check, follow required ToolCustody checks before preparing the candidate.