How to Set Up a Cycle Counting Routine

When we map out cycle counting for our customers at PAX, we start with the parts that need the most attention and the time the team can realistically set aside. The structure below is one you can use in your own shop, whether you work from a spreadsheet, a paper count sheet or an ERP. Adjust the priorities and frequencies to suit your inventory and the way your team works.

Cycle counting means checking a portion of your inventory at regular intervals. A shop with 160 part numbers might plan 300 counts a year because some parts need checking more often than others. That averages about six parts a week or 25 a month. Deciding which parts belong in those sessions is where the planning begins.

Start with a usable inventory list

Bring together the parts you want to include, with their part numbers, units of measure and stock locations. Make sure everyone understands whether a quantity means individual pieces, boxes or another unit. If one part is stored in several places, the count needs to cover those locations consistently. Record lots separately where your stock records distinguish them.

You can begin with one manageable area, such as purchased components, while you establish the routine. Keep a list of what remains outside that first phase so it does not disappear from the plan. Include active parts whose records show zero stock when their turn comes; an empty record can also be wrong.

Give one person responsibility for keeping the schedule moving. Agree who can help with recounts and who can authorize corrections. In a small shop, people may share these duties, but everyone should know who is following up when a count is unfinished or a difference remains unexplained.

Give each part a counting priority

Different parts need different counting frequencies based on usage and cost. A, B and C are common labels for how much attention each part needs: A is high counting priority, B is medium and C is low.

Annual usage value is a useful starting point:

Annual usage value = Units used during the year × Cost per unit

A $0.20 component used 50,000 times a year represents $10,000 of annual usage. A $250 component used 12 times represents $3,000. Oracle's inventory documentation describes this as one basis for ABC analysis, alongside measures such as transaction volume.

Adjust those priorities for critical or error-prone parts. A cheap component that can stop production may need frequent counts, especially if it takes weeks to replace. A part with repeated discrepancies may also need more attention while you investigate. A costly spare can warrant close control even with little usage. GAO's physical-count guidance considers value, activity and operational importance when choosing count frequency.

Use the groups to organize your schedule, with room for exceptions. Then choose a frequency that fits each group's needs.

Choose a frequency for each group

Once the priorities make sense, decide how often each group needs counting. One simple structure is:

These frequencies are a starting example, not a universal ABC rule. A busy stockroom with frequent discrepancies may need monthly A counts, or more frequent checks on particular parts. A stable, slow-moving item may need less attention than a part with the same purchase price that is handled every day.

Use the frequency to limit how long an error could go unnoticed. Review it as you learn which records stay reliable and which do not. Keep urgent checks outside the ordinary rotation when someone reports a suspected shortage or an unexplained balance.

Work out how much counting you are committing to

Suppose your review leaves you with 30 A parts, 50 B parts and 80 C parts. Using the example frequencies for a full year:

Annual workload = (A parts × A frequency) + (B parts × B frequency) + (C parts × C frequency)

Here, that is (30 × 4) + (50 × 2) + (80 × 1) = 300 count assignments.

An assignment means counting one part on one occasion, including the locations and lots needed to reconcile its balance. It does not mean counting one physical unit. If your count list treats each item-location combination as a separate assignment, use that same basis throughout your workload calculation.

The frequency choices make a real difference. Counting A parts monthly and B parts quarterly, while keeping C annual, would increase this example to (30 × 12) + (50 × 4) + 80 = 640 assignments a year. Check the time that creates before adopting the more frequent plan.

A basic workload calculator can help you compare part totals, counting frequencies and available sessions before you commit to a routine.

Fit the work into realistic sessions

For the original 300-assignment plan:

Use the sessions you can actually hold. If holidays, closures and staffing leave 48 weekly sessions, the average is 300 ÷ 48 = 6.25 assignments. If you can reserve only 40 sessions, it becomes 7.5. These are planning averages; individual sessions will vary.

Try several representative counts before filling the calendar. Include a simple bin, a part stored in multiple places and something awkward to reach. Time the counting and recording, then allow additional time for recounts and investigation.

For example, if straightforward counts take five minutes each, six parts need about 30 minutes. Allowing another 15 minutes for differences gives a 45-minute session. Twenty-five similar parts would take about two hours just to count and record. A mixed session with several lots or hard-to-access stock could take much longer. Use your trial results rather than adopting those times as a standard.

If the workload does not fit, consider shorter, more frequent sessions, another trained counter or a smaller first phase. Avoid simply lowering the priority of troublesome parts to make the total look manageable. Leave some capacity for the differences you are counting to discover.

Spread the counts through the year

How often the team meets to count is separate from how often each part needs checking. A weekly session can contain a mixture of A, B and C parts without counting every A part every week.

Spread repeat counts reasonably evenly. On a monthly calendar, an A part counted quarterly could appear in February, May, August and November. A B part could appear in March and September. Distribute C parts across the year so they do not all become a December job.

Within that pattern, group nearby stock when it saves walking, and mix easy counts with difficult ones. Review total time across raw materials, work in progress and finished goods if the same person handles all of them. Use recent reliable count dates when setting the next due date, and keep overdue or never-counted items visible.

Make each session reliable

Agree how to handle stock moving during a count. You might briefly pause movement of the selected parts, or log and reconcile transactions that happen while counting. Count without the expected balance visible where practical, then compare the result with the record. These controls help avoid timing differences and counts influenced by the quantity someone expects to find. GAO's guide discusses both movement controls and blind counts.

When a difference appears, check the part, unit, locations and lots before changing the record. Recount consequential differences, preferably with another person. Investigate recent receipts, issues, returns and transfers, and have the appropriate person authorize any correction.

For example, six pieces found in receiving may belong to a receipt that has not yet been entered. Recording both a stock adjustment and that receipt could add the same material twice. Resolve the missing transaction through the normal process, then recheck the balance.

Keep a short record of the difference, likely cause, correction and person responsible for any remaining action. Repeated problems deserve a change to the receiving, issuing or storage process as well as another count.

Use the first month to settle the routine

In the first week, choose the initial area, assign provisional priorities and run a small trial with a mix of easy and difficult parts. Use the time taken to choose a session size and put the next sessions on the calendar.

During the next two weeks, run those sessions at the agreed time. Record what was completed, how long it took and which differences needed investigation. Carry unfinished work onto a visible list with a new date. If the same issue appears twice, follow it back to the transaction or handling step involved while the details are still fresh.

At the end of the month, compare the plan with what happened. Were the sessions small enough to finish? Did any part need checking sooner? Was investigation time crowding out the next count? Adjust the workload, priorities or reserved time, then extend the routine to the next area when the team has capacity.

The aim is a routine your team can sustain and learn from. Start with clear priorities, reserve enough time to investigate differences, and let the results guide how often each part needs attention.