Output quality

A production log describes work performed, including good and scrap output. Quality Reviewer makes the later decision about the batch. A batch identifies work order, lot number, production date and expiry date, with disposition Pending, Released, Held or Rejected. Work order status gives the reviewer context from the linked production record without treating the log as an inspection result.

The quality-release workflow accepts a Pending batch only when its work order has reached Quality review. It then sets disposition to Released once. A repeat request cannot provide another eligible Pending-to-Released transition. The team still needs an inspection routine that lets the reviewer decide whether the actual output meets its requirements before using that action.

• Pending output. Identify the batch and its work order before the reviewer acts. A lot number helps staff discuss the physical output, while production date and expiry date retain the recorded production and expiry context where the business uses them.
• Human decision. Quality Reviewer checks the output and chooses whether to release an eligible Pending batch. Production Operator’s reported good units cannot substitute for this decision or grant the operator quality authority.
• Exception disposition. Held and Rejected exist as disposition choices. Agree who may choose these outcomes and who decides the next treatment for the affected output before go-live.

Agree what inspection evidence the reviewer needs and where it lives. Use the inspection source your team relies on for measurements and certificates. Ask the reviewer to explain how the reported output relates to the physical lot being inspected. Keep the release decision focused on that lot and its actual evidence.

Configure the release action for Quality Reviewer and test direct access as well as the screen. Decide who may assign Held or Rejected and who resolves the resulting work. Completing work orders is a separate controlled update after the team checks the remaining obligations; releasing a batch does not automatically mark its work order Completed.

Create a demonstration batch linked to running work and leave its disposition Pending. Try to release it while work order status is In progress. The quality guard should reject the action because the work has not reached Quality review. Submit a valid production interval through the production workflow and verify that the work order enters the required state.

Ask Quality Reviewer to inspect the demonstration output using the agreed evidence source and release the eligible batch. Repeat the release request and verify that the original batch remains Released without another successful decision. Include a batch the reviewer would hold and explain the exception action instead of sending it through the accepted-output path. Finally, check whether the planner can still see outstanding work on the work order and decide completion separately.

• Pending batch review — Pending lots with the linked work state visible.
• Production schedule — Released, running and quality-review work with planned dates.

Follow production to quality release. Check reports for disposition and reported-output questions and integrations for an external inspection source.