Demand Variability Calculator
The formula
What the demand variability (cv) tells you
Unit-free dispersion of demand — standard deviation scaled to the mean — projected over the lead time to the units that actually drive buffer stock.
Calculation: CV = σ ÷ μ; lead-time demand σ = σ_week × √weeks. Enter your inputs and every substitution is shown below the result.
Reading the result
Above CV 1 statistical formulas strain; the levers become pooling, replenishment frequency and sometimes accepting deliberate service shortfall on the tail.
Rules of thumb: CV<0.3 stable; 0.3–0.7 moderate; >1 intermittent/erratic
Limitations and best practice
Short windows flatter or punish: a promo week inflates CV for years if the base never drops; measure on a clean, representative window.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Does a high CV kill forecasts?
Square-root-of-time, really?
Source & methodology
Statistical inventory control (CV conventions).
Demand Variability: the number, the method and the caveats
You are here because you need a specific number, and you want to see how it was produced before you rely on it. There are plenty of pages about Demand Variability; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.
Most confusion about Demand Variability comes from mixing up the input you control with the input you merely observe. The formula treats them identically, but your decisions should not: one deserves measurement, the other deserves a defensible estimate.
What makes Demand Variability worth calculating is not precision but position: it tells you which side of a threshold you are on, and by how much. A rough figure that settles the direction beats an elaborate one that never commits.
Nothing below is stock text pasted around a number: the worked example computes coefficient of variation = 0.36 from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — Average weekly demand first, at ≈11.1 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
Every input in Demand Variability, and what it does to the answer
The engine implements a single stated model: CV = σ ÷ μ; lead-time demand σ = σ_week × √weeks. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Average weekly demand (example value 320) is a measured number in the unit named by the label; the formula does not convert for you. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Standard deviation of weekly demand (example value 114) is a quantity rather than a category — precision here is cheap and worth having. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Replenishment lead time (weeks) (example value 4) is a plain measured quantity — the unit shown in the label is the unit the formula expects. If the period is partial, decide whether you mean elapsed or planned time and keep that meaning across every field.
Demand Variability with real numbers, step by step
The tool prints its own working; this is the same arithmetic on the example values, reproduced so you can follow it by hand. Starting figures: Average weekly demand, Standard deviation of weekly demand, Replenishment lead time (weeks). Run to the end, the coefficient of variation resolves to 0.36 — Low variability — simple min/max will do on the bands this tool uses.
- CV = 114 ÷ 320 = 0.36
- σ over 4 weeks = 114 × √4 = 228.0
Lead-time demand std deviation — 228.0. Read next to the headline, this is the figure that shows the shape of the trade-off.
Safety stock at 95% service — 375.0 units. If your inputs change, this is usually the first companion figure to move.
Demand during lead (mean) — 1,280.0. If your inputs change, this is usually the first companion figure to move.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
Scenario table: Demand Variability at ±10 % and ±20 % of the key input
Single-point answers invite false confidence, so the same engine was run across a band around the input that matters most here. Each row is a full recalculation of Demand Variability, not an interpolation.
| Average weekly demand setting | Coefficient of variation |
|---|---|
| 80 % of the example value | 0.45 |
| 90 % of the example value | 0.40 |
| example inputs | 0.36 |
| 110 % of the example value | 0.32 |
| 120 % of the example value | 0.30 |
The corridor runs from 0.30 to 0.45 across that band — which is the range worth planning inside rather than the single 0.36 point estimate. Reproduce it in the form above by editing Average weekly demand alone; the substitution steps will follow your figures exactly.
The levers behind Demand Variability, ranked by effect
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the coefficient of variation recomputed, so the ranking below is measured rather than asserted. For Demand Variability the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Average weekly demand: ten percent up gives 0.32, ten percent down gives 0.40 — ≈11.1 % of the coefficient of variation either way
- Nudge Standard deviation of weekly demand by ±10 % and Demand Variability lands between 0.32 and 0.39 (sensitivity ≈10.0 %)
Average weekly demand is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 0.32 to 0.40. That is where a careless figure does the most damage, so check it against a source, and treat Standard deviation of weekly demand as the second priority (≈10.0 % per ten percent). The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
Reading the result: bands, zones and thresholds
A number on its own is trivia; a number against a range is intelligence. On the example inputs the band reads “Low variability — simple min/max will do”; your own figures place you on a different rung of the same ladder. How much of that band is luck? On Average weekly demand alone ten percent either way covers 0.32 to 0.40. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
In Business & Entrepreneurship, Demand Variability is one instrument in an orchestra: on its own it is a number, next to Lead-time demand std deviation and Safety stock at 95% service it becomes a diagnosis. The tools linked above exist so the headline never has to carry that weight alone.
Common mistakes with Demand Variability (and the fix)
Short windows flatter or punish: a promo week inflates CV for years if the base never drops; measure on a clean, representative window. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Treating the example inputs as a recommendation. They are a demonstration of the mechanism — a decision-grade Demand Variability begins the moment your own figures replace them.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Average weekly demand dominating — a careful figure there beats false precision everywhere else.
A final trap is presentation: reporting Demand Variability to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Six things to confirm before acting on Demand Variability
- Note the date and the inputs beside the number so the figure can be audited later.
- Confirm the example values are plausible for your own situation before replacing them.
- Re-verify Average weekly demand against a source document — ten percent of error there moves the headline by ≈11.1 %.
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Compare the result with one independent method or published benchmark.
- Run the ±10 % stress on the top two levers and check that your conclusion survives both.
Five steps from raw inputs to a figure you can defend
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — start from evidence. The inputs behind Demand Variability are average weekly demand, standard deviation of weekly demand, replenishment lead time (weeks). Write them down with their source next to each one; if you cannot name where a figure came from, that is the input most likely to be wrong. Write the figure down before moving on; memory flatters whichever number you saw last.
Step 2 — compute the version you would not be embarrassed by. If a stranger audited your inputs, which set would you hand over? Enter that set, read the result, and treat everything else as upside. Write the assumptions in the same file as the result, and future arguments take minutes instead of meetings.
Step 3 — measure what deserves measuring. The ranked levers above tell you where a careful figure pays off. Everything else can stay approximate, which is a licence to stop hunting for data you do not need. When two sources disagree, it is almost never the arithmetic that differs.
Step 4 — ask what would have to be true. Take the result you want and work backwards through the inputs until you find the assumption that produces it; then decide honestly whether that assumption is defensible. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 0.36, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. A figure nobody can reproduce is a figure nobody will act on twice.
Where Demand Variability matters in practice
Numbers earn their keep in conversations, and Demand Variability is no exception. In Business & Entrepreneurship discussions around Operations, this figure decides whether an option stays on the table: it converts an opinionated debate into an arithmetic one, and arithmetic is the only referee both sides accept. Note the assumption you are least sure about; that is where the real risk lives.
The companion outputs — Lead-time demand std deviation and Safety stock at 95% service — exist for the second stage of that screen: the headline sizes the prize, while the companions describe the trade-off you are accepting to get it. If the answer changes your behaviour, it deserves a second run with different assumptions.
Treat Demand Variability like a smoke alarm rather than a painting — its value is in being tested periodically, not in being admired once. Note the assumption you are least sure about; that is where the real risk lives.
Demand Variability — frequently asked questions
What affects Demand Variability the most?
Measured on this engine, Average weekly demand is the dominant lever: moving it ±10 % shifts the coefficient of variation across 0.32 to 0.40 — about 11.1 % of the headline, with Standard deviation of weekly demand next at ≈10.0 %. The ranked list in the sensitivity section is computed live, not asserted from a template.
Which matters more: standard deviation of weekly demand or average weekly demand?
For Demand Variability, Average weekly demand wins the head-to-head (≈11.1 % against ≈10.0 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical Demand Variability?
With the example inputs on this page the result is 0.36, labelled “Low variability — simple min/max will do”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate Demand Variability by hand?
Three steps: write the formula (CV = σ ÷ μ; lead-time demand σ = σ_week × √weeks), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Demand Variability than any number of calculator runs.
What happens to Demand Variability if average weekly demand changes by 10 %?
On these inputs a ±10 % change in average weekly demand takes Demand Variability to 0.32 against the 0.36 example — around 11.1 % of the headline. The same test on every other field is in the sensitivity section.
Is the Demand Variability result of 0.36 good or bad?
Neither, on its own — the label “Low variability — simple min/max will do” is the band this figure falls in for the example inputs, and your own inputs will place you elsewhere on the same ladder. Judge the number against your history and your alternatives, and remember that a ten-percent error in Average weekly demand alone moves it by ≈11.1 %.
Is Demand Variability accurate?
The arithmetic is exact: CV = σ ÷ μ; lead-time demand σ = σ_week × √weeks is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 0.36 result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Can Demand Variability be negative or empty?
Yes, and that is informative rather than broken: a negative Demand Variability usually means the inputs encode an outflow or a shortfall, and the verdict band above labels exactly that situation instead of hiding it.
Does a high CV kill forecasts?
It kills point forecasts — with CV above 1, order-up-to levels and forecast-value-of-information tests beat chasing MAPE.
Square-root-of-time, really?
Only for independent periods — autocorrelated demand (weather, campaigns) accumulates faster; the assumption is conservative exactly when it fails often.
Is my data private on this page?
Yes — computation happens locally in your browser, with no account, no tracking of your inputs and nothing sent to a server. The printed formula is the whole story of what happens to your figures.
What the labels on this page mean
- Lead-time demand std deviation
- 228.0 in the default Demand Variability calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Safety stock at 95% service
- 375.0 units on the example inputs — a companion figure printed beside the headline of Demand Variability so that no result is read in isolation.
- Demand during lead (mean)
- 1,280.0 for the Demand Variability worked case; it sits next to the main result because it carries context the headline leaves out.
- Coefficient of variation
- The primary output of this tool: 0.36 for the default inputs, computed exactly from CV = σ ÷ μ; lead-time demand σ = σ_week × √weeks.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The plain-language label — here “Low variability — simple min/max will do” — mapping the computed figure onto experience-based ranges for Business & Entrepreneurship.
- Sensitivity (±10 %)
- How far the Demand Variability moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
The provenance of this Demand Variability calculation
Everything above runs on one stated formula, applied without hidden coefficients: CV = σ ÷ μ; lead-time demand σ = σ_week × √weeks. Source of record: Statistical inventory control (CV conventions). Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.
What to do with your Demand Variability next
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
The audience here is people who need one trustworthy number before their next decision. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.