Bring instructions, materials, measurements, and review gates into the operator’s workflow. Capture what happened against the revision that governed it.
Show the relevant approved step, required inputs, limits, and source context together. An operator can see both what to do and why the step has those requirements.
Capture actual measurements and confirmations in the execution record. Keep units and accepted ranges explicit so the same observation can support later review.
When work cannot proceed, show the unmet requirement and a path to resolve it. Link investigation and review to the affected step rather than letting an exception become an unexplained status.
A later draft should not change the historical basis of a completed step. Keep the governing revision, actual observations, and review decisions together.
An execution record follows an approved recipe revision. It captures actual observations; it does not redefine the record type.
Interface reference · sample recordsProduction and quality use the same execution context. The reviewer can follow the observation back to the applicable instruction and its limits.
Choose a template, shape your workspace, and try the work for yourself. The sandbox is free forever.