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.
- Warehouse Labor Management
- Features
- Review and attachments
Review and attachments
Keep decisions and supporting files with the work they explain.
OverviewReview history×
Warehouse Labor Management · Review and attachments
New
Review history
Review decisions
| Parent | Source revision | Decision | Decided at | Reason | Reviewer | |
|---|---|---|---|---|---|---|
| WO-88151 | 890 | Approve | 12 Oct | Approve rd-542 | ||
| WO-87931 | 650 | Return | 07 Oct | Reject rd-396 | ||
| WO-65718 | 380 | Approve | 05 Oct | Return rd-518 | ||
| WO-16130 | 240 | Return | 26 Oct | Approve rd-905 | ||
| WO-65538 | 770 | Approve | 15 Oct | Reject rd-508 |
6 of 6 records
Approve rd-542Review decisions · RD-66191
ApproveParentWO-88151
Source revision890
Decided at12 Oct
What you can do
Keep the reason beside the decision
Review decisions record an outcome against a particular source revision. A decision has an Approve, Reject or Return value, a reason, decision time, operation key, parent work order and team member reviewer. Supporting attachments also belong to the work order. They carry a title, file, evidence type, upload time, visibility and uploader. Together, these records let the next shift understand why staffing or work was accepted and what evidence the reviewer saw.
A supervisor submits a labor assignment for a cold-storage zone. Labor Reviewer sees that its proposed start overlaps coverage already planned for that zone. The reviewer records Reject with a clear reason and the revision under review. The supervisor changes the coverage and submits a new revision. The later approval should stand beside the earlier rejection, rather than erasing why the plan changed.
How the work is organized
- Decisions. Reviewer, source revision and reason identify who decided and what was reviewed.
- Files. Attachments give the work order a place for a shift sheet, image or other supporting document.
- Visibility. Internal and Shared values help the team distinguish who should see an attachment.
What to agree during setup
Define which decisions belong to the labor review and which belong to final work acceptance. The decision table links to the work order, so the reason should identify the assignment or evidence being discussed when several items share a parent. Agree how operation keys are created and kept unique for a guarded action. Rehearse a Return decision as well as an approval and rejection so the team knows when more information is needed.
For attachments, agree a naming convention and evidence type vocabulary. An uploaded file should have an owner and a visibility value chosen intentionally. The team should test whether staff with different access levels can see only the files appropriate to them. Keep the file linked to the parent job even when a shift changes or the job closes.
Check the handoff on an actual case
Take an assignment submitted for a dock repair. Attach the shift coverage sheet to the parent work order and mark it Internal. Have Labor Reviewer inspect the assignment revision, then record a Return decision asking for a corrected start time. Shift Supervisor updates the proposed coverage and submits it again. The reviewer records Approve with the new source revision. Warehouse Manager should be able to read the whole sequence and see which attachment supported the decision.
Next, upload a file marked Shared and verify that the expected roles can open it. Check that a person outside the authorized review path cannot alter the decision history. During final work acceptance, have Warehouse Manager read the work evidence and the relevant decisions before changing the work order status.
What your team sees
- Review history — Decisions by parent work order, reviewer and source revision.
- Shared work files — Supporting files marked for sharing.
- Submitted assignments — Coverage that still needs a reasoned decision.
Follow the work through
See review assignments and accept work. Use roles to rehearse who can see and change the record.
What it keeps track of
Data model- Review decisions
- Independent review outcomes recorded against a specific source revision.
- Record attachments
- Supporting documents and evidence files attached to a work order.
- Work orders
- Warehouse work planned and executed against an asset under a controlled revision lifecycle.
- Labor assignments
- Shift-level labor assignments submitted, reviewed and approved per zone.
- Team members
- Warehouse staff eligible for labor assignment and review authority.
- Work evidence
- Recorded hours and source evidence produced while executing a work order.
Who uses it
Permissions- Labor Reviewer
- Records assignment decisions.
- Shift Supervisor
- Responds to returned or rejected coverage.
- Warehouse Worker
- Supplies evidence files.
- Warehouse Manager
- Reads the review trail before acceptance.
- Admin
- Checks access to files and decision records.
Set up Warehouse Labor Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.