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.
- Production Dashboard
- Features
- Batch quality
Batch quality
Let the quality reviewer decide on the exact pending lot using completed production evidence and guarded release checks.
OverviewBatch release inbox×
Production Dashboard · Batch quality
New
Batch release inbox
Approval conditions
| Name | Lot number | Work order | Produced at | Expiry date | Disposition | |
|---|---|---|---|---|---|---|
| Batche 244 | L26-9931 | WO-8458 | 03 Oct | 07 Oct | Pending | |
| Batche 957 | L26-1950 | WO-8307 | 09 Oct | 11 Oct | Pending | |
| Batche 300 | L26-1912 | WO-5593 | 25 Oct | 29 Oct | Pending | |
| Batche 624 | L26-2533 | WO-6172 | 22 Oct | 27 Oct | Pending | |
| Batche 592 | L26-0229 | WO-3337 | 11 Oct | 16 Oct | Pending |
6 of 6 records
Batche 244Batches · BTC-89209
PendingLot numberL26-9931
Work orderWO-8458
Produced at03 Oct
Expiry date07 Oct
What you can do
Review the lot before accepting its output
Each batch identifies lot number, production date, expiry date and disposition against work order. Quality Reviewer uses the quality release action to approve an eligible Pending batch. The workflow checks the authenticated actor, exact batch identity, linked work order lifecycle and completed production interval before accepted output can be released.
The batch has a different purpose from the shift result. A shift result describes reported output against a target; a batch records a lot’s quality disposition. A favorable target comparison cannot authorize release. The reviewer must use the guarded decision on the exact evidence under review.
How the work is organized
The quality release action checks that good terminal output has not already been received and that a finished-goods stock balance exists for the batch lot. Quality Reviewer has read access to production records and exercises approval through the named action. The permission list does not grant raw editing of reviewer decisions or protected balances.
- Pending decision. Begin with the exact batch whose disposition is Pending.
- Evidence check. Follow work order to completed production intervals and validate the lifecycle and lot-specific inventory prerequisites.
- Guarded approval. Quality Reviewer approves the submitted revision; repeated acceptance cannot create another good terminal receipt.
What to agree during setup
Define who can act as Quality Reviewer and which organizational scope they may inspect. Review exact submitted revisions and preserve the configured independence requirements. An operator’s ability to read batch context does not permit them to record the reviewer decision. Admin and Manager must preserve the reviewer’s decision authority when preparing access.
Prepare the finished-goods balance for the exact lot before the pilot decision. Agree the inspection evidence the reviewer needs before the first decision. The release action requires a completed production interval. Set up any additional customer inspection evidence with its source owner and rehearse how the reviewer checks it.
Check the handoff on an actual case
A work order has completed production evidence and a Pending batch. Quality Reviewer opens the batch, follows its work order and checks the relevant interval. They confirm the finished-goods balance for lot number and invoke the quality release action. The eligible decision moves disposition from Pending to Released through the guarded workflow.
Repeat the decision on the same terminal output and confirm the action cannot receive it again. Then rehearse a batch without completed production evidence and another whose finished-goods lot balance is missing. Both should remain unreleased after the failed action, with their prerequisite gaps available for resolution.
Test the action with a Production Operator account. Its read access cannot substitute for Quality Reviewer authority. Keep the batch unreleased when a prerequisite fails and record the issue for the planner to resolve. The review should explain which lot and evidence need attention before the next attempt.
What your team sees
Configure the review views with the appropriate decision owner:
- Batch release inbox — Show Pending batch evidence to Quality Reviewer before approval.
- Batch disposition board — Review recorded lot outcomes without giving every viewer decision rights.
- Production interval history — Inspect the completed interval behind the release prerequisite.
Follow the work through
Batch evidence to release defines the decision rehearsal. Check roles for protected actions and reports for the distinction between output and released disposition.
What it keeps track of
Data model- Batches
- Produced lots and their quality disposition.
- Work orders
- Production work orders released to the shop floor.
- Production logs
- Operator production intervals with good and scrap units.
- Inventory balances
- On-hand and reserved quantity by item, location and lot.
- Items
- Materials, components and finished goods.
- People
- Production staff and their linked platform user accounts.
Who uses it
Permissions- Quality Reviewer
- , Production Planner, Production Operator, Manager.
- Quality Reviewer
- Approves eligible output.
- Production Planner
- And Production Operator provide and inspect relevant context.
- Manager
- Reviews business exceptions while the quality decision stays with Quality Reviewer.
Set up Production Dashboard your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.