1. Pallet Tracking System
  2. Features
  3. Review and evidence
Feature · Review and evidence

Review and evidence

Keep decisions, operation receipts and attachments tied to each request.

OverviewFailed Operation Receipts
Pallet Tracking System · Review and evidence

Failed Operation Receipts

Operation receipts

New
Receipt numberSubjectFailure reasonQuantityOccurred atParent
OR-66967Cut to lengthCut to length67018 OctSR-53781
OR-60030Weld frameWeld frame67024 OctSR-33113
OR-52442Drill and tapDrill and tap3003 OctSR-64947
OR-65481DeburrDeburr96026 OctSR-82216
OR-11689AssembleAssemble84027 OctSR-49941
6 of 6 records
Cut to lengthOperation receipts · OR-66967
Failure reasonCut to length
Quantity670
Occurred at18 Oct
ParentSR-53781
Example screen with sample data

What you can do

Read the reason behind each result

Review decisions identify a parent request, reviewer, decision, reason, decision time and source revision. They give Inventory Supervisor a record of what was approved, rejected, returned or escalated. Operation receipts record the attempted action, quantity, owner, time, status and stable operation key. A Failed receipt includes the failure reason. Attachments give the team a place for a photo, document, certificate, signature or manifest linked to a request.

The custom Operations Overview places posted on-hand and available stock beside pending review decisions and failed receipts. Staff can use the exception buckets to find work that needs attention, then open the underlying request and evidence. The overview supports the decision; the request, movement and lot records carry the transaction trail.

How the work is organized

  • Record the decision. Inventory Supervisor reviews a request revision and gives a reason.
  • Keep action evidence. Receipts distinguish Recorded, Verified, Failed and Corrected outcomes.
  • Attach context. Staff link a supporting file or URL to the request under review.

What to agree during setup

Decide what reason is required when a request is rejected, returned or escalated. Agree who reviews Failed receipts and how quickly they should reach the supervisor. Set a naming convention for attachment titles so staff can find the right proof without opening every file. Agree when a photo versus a manifest is useful, and who checks that a URL still points to the intended record.

Decide how staff use the Operations Overview at shift handoff. Pending reviews should have a named supervisor, and failed receipts should have a named follow-up owner. The team should compare the request revision in a decision with the current request before assuming an old approval still governs work. The handover action refuses stale revisions and already Executed or Cancelled requests.

Check the handoff on an actual case

A clerk submits a request linked to a staged pallet. Inventory Supervisor approves the current revision with a reason. The decision and operation receipt share the parent request; a manifest attachment adds the shipping context. The clerk then executes approved stock work. The Posted movement and Recorded receipt show what changed and when. At reconciliation, a matching movement total produces a Verified receipt.

If the posted total differs from authorized quantity, reconciliation produces a Failed receipt and leaves the request unchanged. The supervisor reads the failure reason, request quantity and movement ledger. If a reversal is needed, the compensating movement preserves the original for the auditor. The next shift sees the failed receipt on Operations Overview and can follow it to the source records.

What your team sees

  • Failed Operation Receipts — See blocked actions and reasons that need follow-up.
  • Returned and Escalated Decisions — Find requests sent back or raised for further review.
  • Record Attachments Index — Find supporting records by type and parent request.

Follow the work through

What it keeps track of

Data model
Review decisions
Approved, rejected, returned or escalated decisions on source records.
Operation receipts
Recorded, verified, failed or corrected operation evidence.
Record attachments
Documents and links attached to operational records.
Stock requests
Requests to receive, move, reserve or issue stock.
Stock movements
Posted signed-quantity movements that change on-hand inventory.
Team members
Warehouse staff and reviewers linked to an organization and platform user.
Organizations
Operating organizations that own warehouses, stock and team members.

Who uses it

Permissions
Inventory Supervisor
Decides and investigates.
Inventory Clerk
Adds request evidence.
Auditor
Reads decisions, receipts and postings.

Set up Pallet Tracking System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started