We spent three months talking to supply chain planners at mid-market manufacturing and distribution companies about their Monday morning routine. Not what their planning process was supposed to look like. What it actually looks like. Fourteen interviews, ranging from a single planner at a 60-person specialty distributor to a four-person planning team at a $400M manufacturer.
The pattern was depressingly consistent. In almost every case, the planner described the first two to three hours of Monday as rebuilding context that the previous week's work had already generated - then been lost over the weekend because there was no persistent, automatically-updated planning state to return to.
The Monday Protocol
Here is what Monday morning looks like for a typical mid-market distributor planner. We are using a composite to protect the identity of interviewees, but every step below was reported by at least eight of the fourteen planners we spoke with.
7:30 AM: Export last week's sales data from the ERP into a spreadsheet. The ERP has a reporting module, but the standard reports do not show the right columns at the right level of detail, so the export gets manipulated in Excel. This takes 35-45 minutes.
8:15 AM: Compare against the prior week's forecast. The forecast is in a separate spreadsheet maintained manually. Pull it up, paste in the actuals, calculate variances. Update the running MAPE column. Notice that SKU-042 at the Cincinnati DC missed by 40% for the third week in a row. Flag it.
9:00 AM: Update the replenishment order worksheet. Check current inventory levels from a separate ERP export or a WMS report. Calculate projected coverage in days based on last week's demand rate. Identify items below the reorder point. This takes another 45-60 minutes if done carefully.
10:00 AM: Morning standup with the operations team. The planner shares a summary of what needs to be reordered this week. A few items get added based on feedback from the sales team about customer conversations. A few get deprioritized due to cash flow constraints.
10:30 AM: Begin placing purchase orders. By this point, it is late morning on Monday. Any supplier with a noon cutoff for Tuesday delivery has a tight window.
This is the core Monday cycle. Two to three hours of manual data assembly before any actual planning work can happen. The planners we interviewed were not doing this because they enjoyed it. They were doing it because the tools they had did not do it for them.
What Gets Lost Over the Weekend
The underlying problem is that planning state is not persistent. Everything the planner knew at the end of Friday - the forecast accuracy trend for every SKU, the current inventory coverage calculation, the items that were approaching the reorder threshold - exists only in the spreadsheet they closed when they left. Over the weekend, new orders came in. Inventory moved. Demand patterns continued to evolve. None of that updated the spreadsheet.
So Monday morning is not actually a planning session. It is a data recovery session. The planner spends the first third of the week reconstructing a current view of the world before they can make any decisions based on it.
Three of the planners we interviewed described a related phenomenon: the forecast they updated on Monday was already partially stale by Wednesday. Demand continued arriving. The ERP continued recording transactions. But the planner's working document - the spreadsheet - was a Monday snapshot that nobody updated mid-week. By Thursday, the coverage calculations were off, and any purchase order decisions made on Wednesday's numbers were based on information that was already four days old.
The Accumulation of Small Errors
One planner, at a food-service manufacturer, described what happens to forecast quality over time under this model. When she started the job, the spreadsheet was reasonably accurate. It had been carefully maintained by her predecessor. Over 18 months, it drifted. Items were added without being properly integrated into the seasonality logic. An ERP upgrade changed some field names, and the export formula was patched rather than rebuilt. A new product line was added with a simple average demand rate because there was no demand history to work with.
By the time we spoke to her, she estimated that roughly 25% of the items in the spreadsheet had some kind of data quality issue - a wrong formula, a stale coefficient, a category assumption that no longer applied. She knew this. She did not have time to fix it. Every Monday was spent trying to get the current week's numbers out, not auditing the methodology. The spreadsheet degraded incrementally, and each individual degradation was too small to notice until the cumulative error was substantial.
This is the compounding cost of manual planning cycles. The direct cost is the hours. The indirect cost is the quality erosion that nobody tracks because there is no baseline to compare against.
What Would Have to Change
The planners we interviewed were clear-eyed about what they wanted. Not a more powerful spreadsheet. Not a more complex model. They wanted Monday morning to start with a current view already assembled.
What that looks like in practice: the ERP transaction data from the prior week has already been ingested. The forecast has already been updated against those actuals. The coverage calculations have already been rerun. The planner opens a dashboard and sees the items that need attention this week - sorted by urgency, with the relevant context (current stock, forecasted demand, days of coverage, supplier lead time) already visible.
The goal is not to replace the planner's judgment. Twelve of the fourteen planners we spoke with said explicitly that they want to review recommendations and make the final call. What they do not want is to spend the first two hours of their week manually reconstructing the data necessary to make any recommendations at all.
The technology to automate the data assembly piece exists. It requires an integration between the ERP and a forecasting layer that runs automatically, not one that the planner initiates manually on Monday morning. The barrier at most mid-market companies is not capability. It is prioritization. Data assembly feels like planning work because it has always been bundled with planning work. Unbundled, it becomes visible as an overhead cost - and one that compounds quietly every week until someone measures it.
A Note on Measurement
Before recommending any change to a planning process, we suggest actually measuring the current one. Time how long Monday morning takes. Track the number of purchase order corrections made during the week because Monday's data was wrong by Wednesday. Measure the variance between Monday's forecast and Friday's actuals for the top 50 SKUs. These numbers, once visible, make the case for change in terms that a CFO or operations director can evaluate. The abstract argument for better forecasting rarely persuades. The concrete number - 2.5 hours per planner per week, every week - tends to.
