INVENTORY / WORKFLOW GUIDE

From expected quantity to a reviewed variance

How a physical inventory observation moves through scan, count, difference and reconciliation states.

PRIVATE PILOTTechnical resource · Reviewed 29 September 2026
GUIDE CONTEXT

Follow expected → observed → difference → reviewed.

How should a team explain the difference between expected, observed and reconciled?

Who this is for
Operations managers, count teams and internal-audit reviewers.
What you will leave with
A shared vocabulary for a count session that keeps evidence and unresolved work visible.
Product state
Inventory · PRIVATE PILOT
EVIDENCE LABEL

One item, five states

Expected, counted, difference and review state keep one variance traceable.

Synthetic public representation of the current workflow
  • Expected
  • Scanned and counted
  • Difference and reconciliation decision

Expected is the starting point

Expected quantity is the reference for a scoped count. It should remain visible when raw scans and observed quantities arrive so that the later difference is explainable.

Scanned is evidence, not yet a decision

A raw scan connects an item identifier to a count session and location. A match can be useful evidence, but it should not silently become a reconciled quantity before review.

Difference needs a reason

  • Show expected and observed values together.
  • Label the variance and keep the affected location/session visible.
  • Allow a reviewer to classify the difference without erasing the observation.

Reconciled means reviewed

A reconciled state can mean that a human reviewed the difference and recorded the next state in the pilot workflow. It does not mean an external ERP, finance or stock ledger was automatically updated.

Last reviewed29 September 2026
Product contextInventory private pilot
Next review triggerReview when supported scan, count or reconciliation states change.
NEXT STEP

Review the reconciliation workflow.

Use the proof surface to keep the difference and its review state visible.