Why blind counts matter
On a job site, ledger quantity and shelf quantity drift apart. Issues are logged against the wrong item, transfers stall, or goods sit on a shelf before receipt is posted. Periodic counting exposes the gap; blind counting reduces bias because system quantity is hidden until entry is complete.
Ad-hoc adjustments leave no audit trail. A count session stores system quantity, counted quantity and variance on each line. When the session is posted, variances become stock adjustment movements so finance and the workshop see the same result.
Opening a count session
Define scope first: one warehouse, the whole site, or high-value items only. Record start date and count type (full, cycle, spot). Freezing all movements is rarely practical, but minimising receipts and issues during the window makes variances easier to interpret.
Separate roles: the person who counts should not be the same person who posts adjustments. If one person does both, honest error and intentional manipulation look the same. In blind mode, counters see item name, unit and bin location only.
Field steps: count, label, recount
Tidy the floor first: remove empty boxes, quarantine unlabelled parts, make bin labels readable. Confirm the unit of measure on each line; mixing each with pack quantity is the most common variance source.
Large variances on the first pass should be recounted the same day. Smaller differences follow your ABC rules: tight tolerance on A items, longer intervals on C items. Photos on the count sheet shorten later disputes.
- Keep the count window short instead of trying to lock all movements for days.
- If one item sits in several bins, count each bin line separately.
- Note open receipts and pending transfers in the session comment.
- Close the session with a named approver when counting is finished.
Variance analysis
Surplus often points to unposted receipts, wrong item selection or unit conversion mistakes. Shortage usually means unrecorded consumption, issues not tied to a work order or wrong transfers. Read the report by item and last movement date, not only by total value.
Repeating variance on the same bin and the same fitter suggests process failure; scattered low-value gaps point to recording discipline. After each posted session ask which movement type was missing, who needs training, and whether the next cycle interval should change.
Adjustments and valuation
Approved variances post as adjustments valued at weighted average cost. Large corrections should carry a project or cost centre; otherwise site overhead lands on a single machine. If negative stock is allowed, scan negative balances before counting.
After adjustment, reorder points and critical stock alerts should reflect the new quantity. Otherwise the system stays quiet while the shelf runs dry. With warehouse and inventory management, count sessions, blind mode and posted corrections stay on one chain so the steps repeat cleanly.
ABC and the count calendar
Counting every SKU monthly is unsustainable on most sites. ABC ranks items by annual consumption value: few high-value A lines counted often, many low-value C lines counted rarely. The cycle calendar is published for audit.
A full count is standard when opening a warehouse or at handover; then move to cycle counting. When spare parts inventory module ties item master, bin location and movement ledger together, count lines can be generated automatically instead of maintaining parallel spreadsheets.
Audit and sustainability
Management should read count results as variance rate and repeat frequency, not only currency total. If the same SKUs variance twice in a row, review item setup, units and bin addressing. A short toolbox talk in count week lowers variance percentage.
Blind counting does not replace daily discipline. If receipts and issues are not recorded between cycles, the next session repeats the same gaps and counting cost rises without benefit.
Before closing the count session
For “Before closing the count session” (count), step 1: mirror the Turkish control on site—roles, records and approvals must stay explicit.
For “Before closing the count session” (count), step 2: mirror the Turkish control on site—roles, records and approvals must stay explicit.
Roles and daily rhythm
For “Roles and daily rhythm” (count), step 1: mirror the Turkish control on site—roles, records and approvals must stay explicit.
For “Roles and daily rhythm” (count), step 2: mirror the Turkish control on site—roles, records and approvals must stay explicit.
For “Roles and daily rhythm” (count), step 3: mirror the Turkish control on site—roles, records and approvals must stay explicit.
For “Roles and daily rhythm” (count), step 4: mirror the Turkish control on site—roles, records and approvals must stay explicit.