Count sessions

A count session belongs to a stock request and organization. It records the zone, counted date, physical units and any recount units. Cycle Count Operations captures what is physically present before an independent reviewer decides whether a variance can affect the ledger. Keeping the count blind prevents an expected balance from becoming the answer a counter writes down.

Suppose a team counts a zone for an item with an active stock request. The counter records the physical units and the date. If the count seems wrong, Inventory Coordinator can record a recount. The session remains identifiable by its parent request and revision, so the reviewer can compare the submitted result with the request’s current scope and evidence. The reviewer records a decision separately; a count number alone is not approval.

• Physical observation. Capture the zone, date and physical quantity in the count session.
• Recount trail. Retain recount units on the same session when the team repeats the observation.
• Independent decision. Link a reviewer decision to the parent request and source revision before an adjustment proceeds.

A session can move from Draft to Submitted. A reviewer can approve or reject it. Completion follows the decision and the check of any related stock effect. This sequence keeps an unreviewed count from being treated as a posted change.

Define how zones are named, who may count the same area twice, and how a recount is requested. Assign a reviewer who did not prepare the source count. Decide which supporting file belongs on the parent request and when its visibility should be Internal or Shared. Agree how a rejected count returns for correction and how a changed request revision is reviewed again.

Set the point at which a session is called Completed. The team should check the posted movement and operation receipt, when an adjustment is made, against the approved source revision. A completed count without a reconciled effect can hide a stock difference. Program Manager should own the closeout check.

Create a request for one item and location, then record a count for its zone. Record a recount with a different quantity and submit the session. Ask Inventory Reviewer to inspect both quantities, the attachment and the current request revision. Have that reviewer approve or reject with a reason. If approved, follow the related movement and receipt through reconciliation. The session should carry a clear decision date and should reach Completed only after the outcome is checked.

• Count Session Board — Counts across draft, submitted, approved, rejected and completed states.
• Count Sessions Awaiting Review — Submitted counts waiting for the reviewer.
• Approved Counts — Approved counts with decision date and parent request visible.

See count and review and reconciliation.