These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Recipe / Formulation Mgmt
- Features
- Batch quality
Batch quality
Keep pending, held and rejected lots visible while the authorized reviewer decides whether accepted output can be received.
OverviewBatches Awaiting Quality Review×
Recipe / Formulation Mgmt · Batch quality
New
Batches Awaiting Quality Review
Approval conditions
| Id | Work order | Lot number | Produced at | Expiry date | Disposition | |
|---|---|---|---|---|---|---|
| IDD-198 | WO-6196 | L26-3215 | 20 Oct | 29 Oct | Pending | |
| IDD-681 | WO-1876 | L26-0765 | 12 Oct | 17 Oct | Pending | |
| IDD-594 | WO-1138 | L26-5678 | 26 Oct | 01 Nov | Pending | |
| IDD-994 | WO-4231 | L26-3928 | 05 Oct | 12 Oct | Pending | |
| IDD-492 | WO-1255 | L26-5245 | 21 Oct | 26 Oct | Pending |
6 of 6 records
IDD-198Batches · BTC-64359
PendingWork orderWO-6196
Lot numberL26-3215
Produced at20 Oct
Expiry date29 Oct
What you can do
Make the output decision explicit
A batch identifies produced output through its work order and lot number, with production and expiry dates for the team’s review. Its disposition distinguishes Pending, Released, Held and Rejected output. Quality Reviewer decides eligible accepted output through the guarded release action after inspecting the required production and quality evidence.
The reviewer reads the underlying records and uses the authorized workflow to make the release decision. This matters when preparing access: the pending queue supplies operating context, while the action checks the actor and the output. Production Operator’s ability to read the batch supports the handoff without granting the reviewer’s decision authority.
How the work is organized
Production Operator records the completed production interval and reported output. Production Planner follows the linked work and investigates discrepancies. Quality Reviewer approves inspected accepted output. A successful release receives finished goods once and then completes the linked work order.
- Review the pending lot. Open its production work and inspect the product and interval evidence before deciding.
- Respect adverse outcomes. Keep Held and Rejected output outside the accepted-release action while the responsible people investigate.
- Confirm the receipt. Inspect the successful release result so a repeat action cannot receive the same finished output again.
What to agree during setup
Agree how the team’s testing source supplies inspection evidence and accepted production output to the release request. Demonstrate those inputs during the operating rehearsal with the source owner present. The reviewer needs to know which evidence applies to the lot being presented and how to investigate a contradictory result.
Choose who maintains the recorded expiry date and who investigates Held or Rejected output. Agree any later recovery or disposition procedure before attempting a changed outcome. Staff should retain the original production and decision context so the later action can be explained to the responsible reviewer.
Check the handoff on an actual case
Use a rehearsal batch whose production interval has been saved and whose disposition is Pending. Quality Reviewer inspects the required evidence and submits the accepted-output action. Verify that the successful result identifies the released batch, the finished-goods receipt and completion of the intended production work.
Submit the same release request again and inspect the response. Already-received output must be rejected rather than creating another inventory receipt. Repeat with an otherwise similar batch marked Held and then Rejected. Neither adverse outcome may pass the accepted-release action merely because the underlying production interval has a positive good quantity.
Try the request using an ordinary Production Operator account. The unauthorized actor must fail even when the operator can read the batch and entered the production evidence. Ask the reviewer to show the actual decision result behind the release. Use that result and the balance effect when reconciling output at the end of the rehearsal.
What your team sees
- Batches Awaiting Quality Review — Inspect Pending lots with their production and expiry dates before deciding.
- Held and Rejected Batches — Keep blocked outcomes visible for investigation with the responsible team members.
- Production Interval Register — Review the reported production evidence behind the selected lot.
Follow the work through
Rehearse production to quality release with a repeat request and a held lot. Confirm identity and action access on the roles page, then review implementation before expanding the operating cycle.
What it keeps track of
Data model- Batches
- Produced batch identity, lot number, expiry and quality disposition.
- Work orders
- Released production work for a product, order and resource.
- Production logs
- Operator-captured production intervals with good and scrap units.
- Inventory balances
- Item quantity on hand and reserved by location and lot.
- Items
- Materials, components and finished goods with standard cost and unit of measure.
- People
- Production staff and their role titles.
- Users
- Users
Who uses it
Permissions- Quality Reviewer
- , Production Planner, Production Operator, Admin.
- Quality Reviewer
- Owns accepted-output approval; the planner and operator provide the production context.
Set up Recipe / Formulation Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.