Use an approved source export and an active, proved configuration. The Supervisor imports jobs; Operators then check individual kits prepared from those jobs. Keep the original source reference and revision with the file.
Prepare exact data
On Jobs, select the intended Order source and supported file. Use the published source map for that source. Preserve identifiers, leading zeros and case. Quantities are positive integers in the mapping's required spelling; the importer does not guess locale or convert arbitrary text.
Every mapped header must be present. Unexpected headers, malformed quoting, inconsistent job fields, duplicate lines, unknown options and invalid literals are errors. Do not remove a diagnostic column from the source simply to make a file appear clean.
Preview then accept
Choose Preview upload. Review every job decision and diagnostic. New means no earlier job exists. Unchanged means the same revision and content. Conflict means different content under the same revision. Stale means an older revision. Change means a higher revision requiring source-change handling.
Any error, conflict or stale job prevents the whole file from being accepted. Acceptance rechecks the stored file, active release and preview. If anything relevant changed, prepare and review a fresh preview.
After acceptance, open the job and inspect each kit's stored plan. A line quantity of two creates two individual kits with the same per-kit requirements. A blocked plan has no ready attempt; ask the Author or source owner to resolve the actual issue rather than expecting an Operator to bypass it.
Hand over appropriate references
Use the job's kit references or ready queue. A printed KP1: reference identifies the kit and says it is not a verification result. Requirements CSV or JSON is an expected-content aid, including aggregate primary quantities for preparation. It is not proof of picking or assembly.
A higher source revision can hold the whole job. Follow source changes before activating it. A job absent from a later file is not automatically cancelled.
If an acceptance answer is lost, inspect the recorded upload and job state before creating another operation. Identical reacceptance is a no-op, but that does not make a changed same-revision file valid. Keep the original reference available when reporting a problem.
Obtain the source's file layout
After selecting Order source, use Download an example file when you need its exact CSV layout. The layout follows that source's published map. Replace the example records with the authorised export and retain all required headers; it is not a generic template for every source.
If a protected ConfigSheets feed needs recovery, stop ordinary uploads from that old generation and follow recover the ConfigSheets feed. An ordinary CSV preview cannot replace that recovery handover.
Inspect a saved requirement decision
On a job's individual kit row, open Explain this saved plan. Read its source revision, outcome, blocking reasons, selected requirements and rule trace. A slot can be selected by its approved default, omitted or stopped; equal-priority rules selecting different requirements stop the plan.
This reads the saved plan, rather than recalculating it under a later configuration. Give its exact identity and source revision to the Author when reporting an unexpected requirement. Correct the approved source or configuration through its normal review path; the explanation cannot clear the blocked kit.