Izveidot kontuCreate account
‹ All playbooks
Count stock and reconcile

ops.inventory-count·version 1.0.0·draft1 to verify

Count stock and reconcile

Physical stock is counted, differences against the book records are explained or corrected, and the count is archived as evidence.

MārisOperations Managerruns itProfile ›
Whenscheduled · quarterly — quarterly count, or on demand before an audit, a loan application or an insurance review
Who actsthe agent acts after approval
Time30 min prep + counting time (2 h for a small stockroom) + 30 min reconcile
Countryany country
Sign in to run thisThis playbook opens inside Brain Club. Sign in to read and run it.

When to use

A scheduled quarterly count, or an on-demand count before money.annual-report-lv, money.loan-application or ops.insurance-review. Not for a single item that went missing — record it as a one-off adjustment and investigate; a full count is for proving the whole list. Not for ordering what the count reveals to be low — that is ops.purchase-approval after this playbook closes.

Before you start

  • The scope and date are decided by the owner; receiving and shipping are paused or cut off at a stated time.
  • The book stock list is exported per location the evening before.
  • Counters are named; each location has one counter who does not count a location they alone control, where possible.

What a run requires3

  • Approval · S5 · ownerthe run stops until a named person records the decision
  • Approval · S7 · ownerthe run stops until a named person records the decision
  • Irreversible · S7an agent never closes it alone

Any step can wait until a date and reopens by itself; every closed step leaves evidence (a note, a link, a number).

The trail8 steps

  1. Freeze movements and cut offagent

    Note the cut-off time; nothing is received, shipped or moved between locations from that moment until the count closes.

    Done when the cut-off time is written on the count sheet and staff know.

  2. Prepare count sheetsagent

    From the book list, produce sheets per location: item, code, unit, book qty (hidden or on a separate column — blind count), empty column for counted qty.

    Done when every in-scope location has a sheet and the sheets together cover the whole scope.

  3. Countagent

    Physical count, blind (counters do not see book quantities). Two people count high-value items independently.

    Done when every line has a counted quantity and the counter's name.

  4. Compute differencesagent

    Enter counted quantities; produce the difference list with book value per difference and a first-pass cause guess (in transit, unrecorded sale, breakage, theft, unit error).

    Done when the difference list is complete with values.

  5. Decide correctionsownerneeds approval · owner

    Approval · S5 · owner — the run stops until a named person records the decision

    Walk the differences: accepted as explained (e.g. in transit at cut-off), corrected in the books, or written off. Write-offs above a set value need the owner's explicit yes.

    Done when every difference line has a decision: explain · correct · write-off.

  6. Recount disputed linesagent

    Any line the owner questions, or any large difference, is recounted by a different person before books change.

    Done when each recounted line has a second count and a final figure.

  7. Apply correctionsagentneeds approval · ownerirreversible

    Approval · S7 · owner — the run stops until a named person records the decision

    Irreversible · S7 — an agent never closes it alone

    Update book stock per the decisions; write-offs are recorded with reason and value so they land in the right period's accounts.

    Done when book stock equals counted stock for every closed line and the write-off list is dated and signed off.

  8. Record and follow upagent

    Archive the count sheets and the difference list; open a task for each unexplained difference above threshold (bc tasks add "Investigate stock difference: <item>"); note repeat offenders (same item shrinking twice).

    Done when the archive link and the task list are sent to the owner.

Checks — how we know it worked

  • Sum of counted value + explained differences = book value before the count (read the totals back, not "it balances").
  • Every difference line has a decision and, for write-offs, a reason and value.
  • No location in scope has an empty sheet; no counted line lacks a counter name.
  • Book stock after S7 matches counted stock line by line for corrected items.

If it goes wrong

SymptomResponse
Goods moved during the countStop, note the time, recount only the affected location; do not blend pre- and post-move figures.
A large unexplained differenceRecount with a different counter (S6); if it stands, open a task and escalate to the owner — do not write it off silently.
Counters disagree on the same lineCheck units (pieces vs boxes vs pallets) first — most disagreements are unit errors, not theft.
Book list was wrong before counting startedNote it on the sheet, count physically anyway, flag the book-keeping source to money.month-close.
Same item differs every quarterStop treating it as noise: check the item's unit of measure, its receiving records, and its storage location.

What each step leaves behind

  1. S1the cut-off time is written on the count sheet and staff know.
  2. S2every in-scope location has a sheet and the sheets together cover the whole scope.
  3. S3every line has a counted quantity and the counter's name.
  4. S4the difference list is complete with values.
  5. S5every difference line has a decision: explain · correct · write-off.
  6. S6each recounted line has a second count and a final figure.
  7. S7book stock equals counted stock for every closed line and the write-off list is dated and signed off.
  8. S8the archive link and the task list are sent to the owner.

Evidence to keep

Count sheets per location with counter names and date · the cut-off time · the difference list with values · the owner's decisions in S5 (who, when) · write-off records with reason and value · the archive link.

How this playbook improves

After every 4 runs (one year) ask: did unexplained difference value fall? Which location or item repeats? How long did counting take per location, and would a different cut-off time (e.g. end of day vs mid-morning) remove goods-in-motion noise? A new version changes the step that caused the repeat or the wait, and says so in its change note.