1. Cross-dock Management
  2. Features
  3. Evidence and reconciliation
Feature · Evidence and reconciliation

Evidence and reconciliation

Trace request decisions and operation results before declaring the authorized stock quantity verified.

OverviewFailed Operation Receipts
Cross-dock Management · Evidence and reconciliation

Failed Operation Receipts

Operation receipts

New
Receipt numberSubjectParentActionQuantityFailure reason
OR-33454Cut to lengthSR-88418ACT-987210Cut to length
OR-82664Weld frameSR-63541ACT-828780Weld frame
OR-51589Drill and tapSR-57262ACT-985650Drill and tap
OR-79503DeburrSR-53802ACT-825740Deburr
OR-71219AssembleSR-65000ACT-890550Assemble
6 of 6 records
Cut to lengthOperation receipts · OR-33454
Failed
ParentSR-88418
ActionACT-987
Quantity210
Failure reasonCut to length
Occurred at13 Oct
Example screen with sample data

What you can do

Give the next shift an explainable result

Review decisions record who decided the stock request, the source revision and the reason. Operation receipts record the action, quantity and outcome, with a failure reason when the work cannot proceed. Supporting documents belong to the request so the team can find the evidence relevant to a disputed quantity or an uncertain operation.

Inventory Supervisor uses these records to investigate a shortfall, a wrong posting or a verification mismatch. Auditor can follow the chain without changing the result. This is particularly useful across dock shifts, when the person examining a request may not have seen the arrival or spoken with the clerk who prepared it.

How the work is organized

  • Decision evidence. Approved, Rejected, Returned and Escalated decisions retain their reason and source revision. The saved explanation tells the clerk what was authorized or which issue requires an answer.
  • Operation evidence. Recorded, Verified, Failed and Corrected receipt states describe the result being examined. The action and quantity identify the work, while the operation identity helps the team recognize a repeated request.
  • Verification. Reconciliation compares the authorized request quantity with its posted movements. A mismatch produces a failed receipt and leaves the request unchanged so the cause can be investigated.

What to agree during setup

Agree what a useful decision reason and failure explanation must contain. Another person should be able to identify the stock request, understand the quantity issue and find the next responsible action. Use document titles and attachment types consistently so a manifest or inspection record can be found during an exception review.

Set a supervisor routine for failed operations and returned or escalated decisions. Decide how the next shift receives unresolved work and how supporting document links remain accessible. Keep the Auditor’s role read-only and rehearse its access to the complete request evidence. Establish how a failed verification is rechecked after the cause is corrected through the supported procedure.

Check the handoff on an actual case

Choose a rehearsal request with a known authorized quantity and a posted movement the team can inspect. Run verification and ask the Auditor to trace the result through the decision, movement and receipt. The explanation should identify the source revision and actual stock effect, rather than rely on a departure record or an informal completion note.

Next, test a mismatch in the rehearsal environment. The verification action must produce a failed receipt with a useful reason while leaving the request unchanged. Have the Inventory Supervisor investigate the discrepancy and retain the original evidence when correcting the cause. Inspect the supported recheck result and confirm how repeat operation identity is handled. Finish by handing the unresolved case to another team member to check that the recorded explanation is sufficient.

What your team sees

  • Failed Operation Receipts — Failed actions with their request, quantity and reason for supervisor follow-up.
  • Review Decisions Register — Reviewers and reasons attached to the source request revision.
  • Record Attachments Index — Document links and evidence types retained with the request.

Follow the work through

Follow post and verify stock and retain history through correct or reverse stock work.

What it keeps track of

Data model
Operation receipts
Recorded, verified, failed or corrected operation evidence.
Review decisions
Approved, rejected, returned or escalated decisions on source records.
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.
Stock reservations
Held, released or consumed reservations against eligible stock lots.

Who uses it

Permissions
Inventory Supervisor
Reconciles and resolves stock exceptions.
Inventory Clerk
Supplies the request context and documents.
Auditor
Examines the evidence chain.
App Administrator
Maintains the membership needed for authorized access.

Set up Cross-dock Management your way.

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

How to get started