AWRA OpsHub Search

The Monthly Count That Comes Round on Its Own

A count plan asks you how often you intend to count, requires an answer and stores it. The question worth asking of any system is what happens next. Here a daily job opens the count when the plan says it is due, and tells the person who has to do it.

Inventory Insights AWRA OpsHub Team 10 min read

The most expensive kind of missing feature is not the one that is absent. It is the one that is present, configurable, saved successfully, and connected to nothing — because an absent feature makes somebody ask a question, and a stored setting makes them stop asking.

Stock counting is a good place to look for one, because a count plan's frequency is exactly that kind of setting: easy to capture, easy to show back, and easy to leave connected to nothing. This post describes what the field does here, and how to test it in any system.

What the plan asks you, and what it does with the answer

Setting up a count plan is a considered piece of design. You define what is in scope, who counts it, whether counters can see the expected quantity, and what size of variance needs review. And you are asked how often the count should run — a required field, offered as a fixed set of choices, refused if you leave it blank, defaulting to monthly if you say nothing.

In a system where that answer is stored faithfully, shown back to you, and read by nothing, a plan that says monthly raises exactly as many counts as a plan that says annually, which is none.

Here a plan also carries a next due date and an assignee. Every morning a scheduled job looks for active plans whose date has arrived and opens a count session from each one — the same session you would get by pressing the button yourself, with the plan's scope, its blind and freeze settings and its due window. The assignee is told in the app, or the person who created the plan if nobody is assigned, and the next date moves on one period. Opening a count from a plan by hand moves the date on too, so a manager who counts early does not get a second count a week later.

A rhythm recorded in the product and performed by nobody is a wish. Here the product performs it, and a named person hears about it.

06:20
the daily run that opens every count whose date has arrived
1
person told in the app — the assignee, or the plan's creator
0
counts opened for a plan marked on demand, which stays manual by design

Two details are deliberate. If the previous count from the same plan is still open, the job does not stack a second one on top of it; it skips that day and moves the date on. And a plan set to on demand is never opened automatically, because on demand means exactly that.

It is rarely one setting, and that is the real point

A single inert field is an oversight. Several are a pattern worth naming, and the pattern turns up wherever a product captures a decision in one release and acts on it in another. These are the settings worth testing for an effect, and what each one does here.

Settings worth testing for an effect, and what each does here

  • The count plan frequency — opens a session on the due date and tells the assignee. The subject of this post.
  • A per-item stock rotation policy — chooses earliest-expiry-first or first-received-first per item on every allocation path. Argued in choosing the rotation per item.
  • A capacity on every storage location — shows on-hand against capacity, warns on an edit that leaves a location over, and raises a Smart Alert. Argued in when a shelf is full.
  • A supplier performance record — holds each vendor's scorecard, refreshed nightly from their orders. Argued in the supplier scorecard.
  • Value thresholds on approvals — approval rules a workspace can add, so a requisition, quotation award or supplier bill routes by amount band and department to an ordered chain of signers. Without a rule, approval is by permission.

Inert settings share a shape wherever they turn up. Somebody designs the right model, builds the surface to capture it, ships that, and the part that would act on it is left for later. Later does not arrive on its own, and nothing fails loudly enough to remind anyone — because a stored value looks identical to a working one from every screen in a product.

A field that does nothing is not a small bug. It is a claim, made by the software, that something is being taken care of.

Why this matters more the further apart your sites are

For a single warehouse an inert setting costs almost nothing, because the count happens when the manager decides it happens and the plan is never doing the remembering. The person and the rhythm are in the same building.

Now run distribution across a country that is long — a head office in one city, branches strung out along the coast and inland, some of which nobody from head office will visit this quarter. The plan is not a convenience there. It is the supervision. It is the mechanism by which somebody in Cairo knows that stock in Alexandria and Aswan is being verified on a rhythm, without being present to see it.

Where a plan is inert that assurance is not weakened, it is imaginary — the plan exists, it is correct, it reads monthly, and everybody who looks at it concludes that counting is under control. With the schedule acting on it, the count appears in the Aswan branch on the morning it is due, assigned to a named person, whether or not anybody in Cairo remembered.

How much of the counting discipline is actually enforced by the system

Recorded only Enforced by the system

The count rhythm

A due count is opened and assigned on its own. What is still recorded only: a count that runs late, or a day skipped because the last one was still open.

Who may count

Permission-gated properly — counting, reviewing and approving are separable.

Blind counting

If the plan hides expected quantities, the counter genuinely cannot see them.

Variance review

A session cannot be closed while lines are unreviewed. This is a hard stop, not a warning.

Recount of a disputed line

A per-line recount with a reason and an audit entry; an approved line cannot be quietly edited.

Writing variances to stock

A variance raises an adjustment for approval rather than moving stock directly.

The rhythm decides whether any of the rest ever happens, and here it happens on its own; what is left is noticing when it happens late.

What to do about it today

Give every plan an assignee and a first due date, and check the frequency is the one you meant — a plan left at the monthly default will produce a count every month. If a plan exists only so somebody can start a count when they choose, set it to on demand.

And keep asking the question this post started with, of every scheduling field in every system you run, ours included. The test is not whether the field exists. It is whether anything has ever happened because of it.

The verdict

Everything hard about stock counting is built here and built well — blind counts, per-line recounts with reasons, sessions that refuse to close over unreviewed variances, and a count that cannot silently rewrite your stock. The easy thing is the one that decides whether any of the rest ever runs, and here a plan opens its own count on the date it is due and tells a named person. What a far-flung operation needs on top is a view of the counts that ran late and the locations that were never counted — and that is the next thing we would build.

Four questions to ask about any scheduling setting

Set a plan to weekly. Show me the count it raises next week.

What a straight answer sounds like

A session appearing on its own, assigned to somebody. Ours does this.

Why it matters

This is the whole test. Every scheduling field in every system should be asked to demonstrate one occurrence.

Which of my locations has not been counted this quarter?

What a straight answer sounds like

A report. Ours is the next thing we would build.

Why it matters

Coverage is the question a plan is supposed to be answering. If nothing reports it, somebody has to work it out.

What happens when a scheduled count is missed?

What a straight answer sounds like

An escalation, a flag, or nothing.

Why it matters

A schedule with no consequence for being missed is a preference, not a control. Ours logs a skipped day; surfacing it is the next build.

Which settings in this product are stored but not yet acted on?

What a straight answer sounds like

Discomfort, then an honest list.

Why it matters

Every mature product has some. A vendor who can name theirs is telling you they know their own system.

Stock counting — what ships today, and what we can add

What AWRA OpsHub does today

  • Counts opened on the plan's schedule. A daily job opens a session from every active plan whose due date has arrived, with the plan's scope, blind and freeze settings and due window, and moves the next date on one period.
  • The assignee told in the app when a scheduled count opens — or the plan's creator, where nobody is assigned.
  • Blind counting that is genuinely blind — where the plan says so, the counter cannot see the expected quantity.
  • Per-line recount with a reason and an audit entry, so a disputed line is settled without re-running the whole count and an approved line cannot be quietly changed.
  • Sessions that will not close over unreviewed lines, which is a hard refusal rather than a warning.
  • Variance thresholds on the plan, so large discrepancies are separated from rounding.
  • Variances raised as adjustments for approval, rather than written straight to stock — so a count cannot silently rewrite your inventory.
  • Separable permissions for counting, reviewing and approving.

More we can add to your workspace

  • An overdue notice for a scheduled count, so a count that runs past its due window, or a day skipped because the last count was still open, reaches a person rather than a log. Commission it
  • A count accuracy measure — variance is captured per line, and aggregating it into a score, a trend and a comparison between counters or locations is the build. Commission it
  • A coverage report, answering which of your locations have not been counted this quarter in one screen. Commission it

Where we point you to a specialist

  • We publish no statutory stocktake requirement for any country in this region. Where a rule appears anywhere on this site it carries a date and a source, and this would not.
  • We are not presenting the counting module as weak. It is one of the better-built parts of this product, and the two pieces above are what turn a well-run count into a managed programme.

What we would build next

The clock is built. Two pieces remain

The scope, the blind setting, the variance thresholds and the schedule are all built and working. What is left is seeing when the schedule slipped, and measuring what the counts found.

Overdue visibility

A scheduled count that has passed its due window without closing, or a day the schedule skipped, surfaced to somebody — with the branch, the plan and how long it has been. The schedule already writes the event; this puts it in front of a person.

Coverage and accuracy reporting

Which locations were counted, when, and how accurate they turned out to be. Variance is already captured per line, so the raw material is there. Without this, a counting programme can be run but not managed.

The scheduler is the piece that makes the frequency field mean something. Overdue visibility is the half that makes it a control rather than a convenience, and it is the one we would build first.

Talk to us about stock counting

Tell us how many sites and how far apart

We will show you a plan opening its own count, what the counting module enforces today, and what still depends on somebody noticing.

Talk to us about counting

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center