Reading Days of Cover in Production Planning

Days of cover is how many days current stock will last at the average daily demand rate, calculated as on-hand divided by average daily demand, so 600 units against 30 a day reads as 20 days of cover. In EDGEBIC by User Solutions days of cover is one of the headline metrics above the inventory calendar, and it is deliberately a blunt one: a fast coverage read for a gut check across many parts, distinct from the precise, timing-aware picture the projected balance gives. This post explains what the number measures, where it helps, and where you should stop trusting it and read the projection instead.

Days of cover is one metric among several in the replenishment picture. For the full loop of demand, buffers, and suggestions, read forecasting and replenishment explained. This post stays on the single metric and how to read it well. Inventory features vary by installation, so check which planning capabilities your build exposes.

What the Number Measures

Days of cover answers one question: at the average rate of consumption, how long does current stock last. The math is simple. Take on-hand, divide by average daily demand, and you get a count of days. A part with 900 units on hand burning 45 a day has 20 days of cover. A part with the same 900 units burning 90 a day has 10.

That simplicity is the point. Across a catalog of parts, days of cover gives you one comparable number each, so you can scan a list and see at a glance which parts are thin and which are deep. It is a coverage read, not a plan: it does not know about a big order landing next Tuesday or a receipt already inbound. It knows on-hand and an average burn, and it turns those into a single, easy-to-compare figure.

Because it uses today's on-hand rather than a future balance, days of cover is a present-tense metric. It tells you how long what you have right now would last if nothing changed and demand ran at its typical rate. Neither of those conditions holds exactly, which is why the number is a starting point rather than a verdict.

Days of Cover Versus the Projected Balance

The projected available balance and days of cover answer related questions with very different precision, and knowing the difference keeps you from over-trusting the simpler one.

The projected available balance nets actual forecast and firm demand against incoming supply, bucket by bucket, across the horizon. It captures lumps (a large order in one week), timing (a receipt that lands before or after a demand spike), and future supply that has not arrived yet. It is the number a purchase decision reads from, because it says exactly when the plan breaches a buffer and in which period.

Days of cover captures none of that. It flattens demand to an average and ignores supply timing entirely. So the two disagree precisely when timing matters. A part with 30 days of cover on average can breach its buffer next week if a big firm order lands early, and the projected balance would show that red bucket while days of cover still reads a comfortable 30. Conversely, a part with only 8 days of cover can be perfectly safe if a receipt is inbound in 5 days, which the projected balance nets in and days of cover never sees.

Read days of cover to decide where to look. Read the projected balance and the below-safety buckets to decide what to do.

When Days of Cover Earns Its Keep

The metric is genuinely useful in the right role. Its strength is speed and comparability across many parts at once.

• Triage across a catalog. Scanning hundreds of parts, days of cover ranks them by coverage in one column, so you know which handful to open on the projection first.
• A sanity check on a single part. After setting a buffer or a reorder point, a glance at days of cover confirms the part is not wildly over- or under-stocked relative to its burn.
• A shared shorthand. "That part is down to five days of cover" is a fast way to communicate urgency to a buyer or a manager without opening a projection.

In each case, days of cover is doing what a gut check should: pointing attention, not making the final call. It pairs naturally with the below-safety count, which flags how many buckets breach the buffer, so together they tell you both roughly how long you have and precisely when the plan crosses the line.

A Worked Example: Two Parts, Same Cover, Different Risk

Two purchased parts each show 20 days of cover. Part A has 600 units burning 30 a day; Part B has 400 units burning 20 a day. On the coverage metric they look identical, and a quick scan would treat them the same.

Open the projections and the similarity breaks. Part A's demand is steady at about 30 a day with no large orders, and no supply is inbound. Its projected balance walks smoothly down, first breaching its 150-unit safety level around day 15, close to what the 20-day cover implied. For Part A, days of cover was a fair proxy.

Part B carries a single firm order for 250 units due on day 6. The average of 20 a day hides that lump entirely. Its projected balance drops from 400 to 150 the day that order ships, then keeps falling, breaching its safety level around day 4 instead of day 20. Days of cover said 20; the projection said 4. Same headline number, very different risk, and only the projected balance caught it because it nets the actual dated demand rather than a smoothed average.

The lesson is not that days of cover is wrong. It did its job, ranking both parts as worth a look. The projection did the job days of cover cannot: it read the timing.

Reading It Well

Treat days of cover as the fast first read and the projected balance as the decision. Use the metric to rank and triage, to sanity-check a buffer, and to communicate urgency quickly. Then, for any part where timing matters (lumpy demand, a large order in the horizon, a receipt in flight), open the projection and read the below-safety buckets and the projected stockout date before you commit to buy or build.

That two-speed habit, blunt metric to point, precise projection to decide, is what keeps planning fast without letting the average hide a real breach. For where these metrics sit in the wider workflow, start from the EDGEBIC planning guide, and to see how the projected balance turns into an actual order, read how projected balance drives a purchase decision.