Inventory count specialist at a neighborhood fresh-food store - the variance handling SOP - recount, four-way routing, tiered approval, and a tolerance line that says how much variance is allowed to be normal

You are the stocktake SOP writer for a neighborhood fresh-food chain.
Write us a Count Variance Handling SOP. I am the inventory count
specialist; the executors are me, the store manager, and the stock
clerks; the approval chain runs up to the owner. Deliverable: one
and a half pages, archivable, usable to train a new hire.

Scope: everything between "variance report printed" and "adjustments
posted" for monthly and spot counts. How the count is staffed and how
raw sheets get audited are out of scope.

Write the SOP in steps; every step carries: who / does what / what to
do when it goes wrong:

Step 1 - Recount (led by me, within 24 hours)
- Every variance line gets recounted: the original counter steps
  aside; I recount with one employee from another zone. Weighed
  items are re-weighed with tare deducted
- Lines where the variance vanishes on recount are "counted wrong":
  correct the number on the spot, sign, done
- The recount must finish within 24 hours of the report printing -
  three days later the floor has moved and a recount proves nothing

Step 2 - Routing (me; four fates, invent no fifth)
- Counted wrong: recount already resolved it; correct the number
- Booking gap: document timing (received-not-keyed, shrink-filed-
  not-deducted, in-transit counted) - fix the documents, do not
  touch stock
- Shrink: genuine loss (moisture loss, damage, unattributable
  leakage) - through the shrink process, into the shrink ledger
- Unresolved: variance survives recount and fits none of the above -
  freeze the adjustment, escalate to the store manager, hand to loss
  prevention or the head office

Step 3 - Approval and posting (dollar tiers; the store sets the
amounts, the SOP keeps placeholders)
- Single-category variance at or under [direct-adjust line]: I
  adjust directly and report afterward
- Between [direct-adjust line] and [manager line]: store manager
  approves, then adjust
- Above [manager line], or the same category drifting the same
  direction two months running: owner approval, and the category
  becomes a priority item in next month's cycle count

Step 4 - Ledger (me, after every count)
- Line-by-line: date / store / category / variance amount (over and
  short in separate columns) / fate (one of the four) / approver /
  resolved or not
- One monthly summary page: variance rate by category vs [category
  tolerance]; categories over tolerance become next month's priority
  cycle-count items

Red lines (put them in the SOP, no commentary):
- Never "post first, investigate later" - adjustment follows recount
  and routing, always in that order
- Never bury unresolved variances in shrink - once the shrink rate is
  polluted, next year's ordering budget and shrink targets are built
  on fiction
- Recovery and discipline do not travel through the count process:
  a big gap that points at a person goes to the store manager and
  loss prevention. I do not draw conclusions, and I do not hold
  the conversation

Output format:
- Four sections, stepwise, directly usable as training material
- A ledger header template attached
- A one-card quick reference: three dollar lines, four fates, two
  red lines - to tape up in the count room

Do not:
- Write "strictly comply with financial regulations" - the SOP is
  the regulation; self-referential filler gets cut
- Invent tolerance numbers for us - every dollar line and tolerance
  stays a [placeholder]
- Design a year-end "write off accumulated variances" step - writing
  off is laundering a problem into a non-problem, and the ledger
  exists precisely so that cannot happen

Why it is written this way

Variance handling is the stretch of the count nobody wants to touch: the count itself ran late, the report prints, and everyone just wants it gone. Without an SOP the default moves are the two extremes - the owner shrugs it all into shrink with "fresh food varies," or the clerk gets charged for the difference. Both destroy the count: the first turns the shrink rate into a landfill; the second makes next month's raw sheets come in suspiciously even.

"Unresolved" as its own fate is the pivot of this SOP. It turns "couldn't figure it out" from a mark of failure into a legal holding state: freeze, escalate, hand off. Without it, an unexplained variance has exactly two exits - forced into shrink or forced onto an employee - and both are miscarriages.

The dollar tiers stay as placeholders because thresholds must scale with the store: whether fifty dollars should wake the owner is a different question in a store doing $1,200 a day versus $4,500. What an SOP can fix is the structure - who may adjust how much, what must escalate - and structure travels across stores while numbers do not.

The recovery red line and the shrink-burial ban are two faces of one rule. The count specialist sits closest to the numbers and furthest from personnel authority; explicitly carving discipline out of the role is what lets real variances keep flowing upward. The variance report telling the truth is the precondition for the whole machine.

Variables