Smaller production batches: calculate the changeover cost before changing the schedule

Reducing a production batch can release cash tied up in finished goods and make the next customer request easier to accommodate. It can also add changeovers, startup scrap and line occupation. Compare the current and proposed schedules over the same period, using actual customer demand and the same opening inventory. A lower batch quantity alone does not establish that the new schedule costs less.

The useful question is how often each product must run to deliver the required service without producing unnecessary stock. Start with a product family that shares equipment and has a reasonably clear demand pattern. A pilot on one line gives operations a chance to observe the changeovers and shortages before the company commits to a new factory-wide planning rule.

NIST MEP defines setup reduction around the interval between the last good unit of one run and the first good unit of the next. That boundary is helpful here: measure the whole interruption, including adjustments and first-piece approval, rather than only the operator's visible tool change.

For each proposed run, record starting inventory, demand due before the next run, planned quantity, expected usable yield, setup time and available production hours. Put deliveries on their actual promised days. Weekly totals can hide a stockout on Tuesday followed by excess stock on Friday. Identify material availability and inspection release dates that limit when the batch can start or ship.

Use opening and closing units to reconcile the calendar: opening units plus usable production less shipments equals closing units. Track rejected or quarantined quantities separately. Those units may occupy space and consume cash without being available for customers. A spreadsheet that combines them with sellable inventory will make the smaller-batch option appear safer than it is.

Avoid assuming every changeover is identical. A color change, allergen change, material switch or tooling adjustment can require different work. Let the production team group changes into meaningful categories and estimate each from observed records. The finance comparison should reflect those operational differences without prescribing shortcuts to quality or safety procedures.

Assume a hypothetical manufacturer makes 4,000 units of one product every four weeks and sells 1,000 per week. For a deliberately simplified illustration with steady shipments and immediate production, average cycle stock is about half the batch, or 2,000 units. Moving to a weekly batch of 1,000 brings that approximation to 500 units. The reduction is 1,500 units.

At $18 of cash cost committed per unit, the reduction represents $27,000 less cash in cycle stock once the transition is complete. It is a release of working capital, not $27,000 of recurring monthly profit. The smaller schedule adds three setups every four weeks. If each additional setup costs $240 and occupies two hours, the new schedule adds $720 of recurring setup cost and consumes six additional line hours over that period.

The comparison is incomplete until those six hours are located in the production calendar. If the line has idle time, the cash setup cost may be the main issue. If the line is full, the review must also identify what output those hours displace. Any claimed reduction in damage, obsolescence or storage spending needs a separate, supportable assumption.

If finance wants to show a funding benefit, apply an explicitly chosen financing rate to the average cash released and the relevant time period. For example, an assumed 10% annual funding cost on $27,000 is $2,700 per year, before fees and differences in actual borrowing. It cannot be compared with a four-week setup cost without converting both to a common period.

Some businesses will release cash but not reduce an interest bill because they do not repay borrowing. In that case, describe the benefit as additional available cash, or show the approved alternative use. Storage savings also require an avoidable expense. Emptying a few shelves inside a lease that continues unchanged does not automatically reduce rent.

There may still be a sound reason to adopt smaller batches. Less exposure to a customer design revision, faster replenishment of a popular variant or fewer urgent substitutions can justify the change. Name the benefit and the evidence needed to measure it. Avoid making the inventory-carrying percentage absorb every operational improvement that has not been calculated separately.

The half-batch average is an approximation for a simple flow. Replace it with day-by-day inventory when demand is concentrated, production takes several days, or a customer orders in large irregular lots. A weekly run that appears sufficient on average can fail when two large orders arrive together. Build at least one scenario using an observed busy period and another with a supplier delay.

For each scenario, report missed commitments, emergency freight, extra setups and maximum inventory. Keep the service objective explicit. If management accepts a longer promised lead time, that is a commercial change to assess with customers, not a hidden assumption inside the production spreadsheet.

NIST's supply-chain material discusses identifying alternative suppliers and appropriate inventory responses to risk. In this decision, compare a smaller finished-goods batch with targeted protection at the actual source of uncertainty. Carrying a critical material may support several finished variants more flexibly than keeping a large quantity of every finished product, provided the remaining production lead time meets customer needs.

Choose a pilot period long enough to include the intended sequence of runs. Retain the previous schedule as a comparator and record the new method's actual setup intervals, usable output, shipments and stock levels. Establish who may authorize an emergency run and how its cost will be recorded. Otherwise, the pilot can appear successful only because extra work happens outside its records.

Agree in advance what would require changing the pilot: repeated delivery misses, unexpected quality holds, unavailable trained operators or a setup duration beyond the capacity plan. These are operating conditions, not reasons to conceal poor results. A failed cadence can still reveal a worthwhile setup-reduction project.

Release the new schedule only after operations and finance reconcile its service performance and cost. Keep the approved batch sizes, review date and demand assumptions together. When customer demand or the production route changes, revisit the cadence using the same calendar method rather than carrying the pilot's conclusion forward indefinitely.