Moving Average & Smoothing - Business Analytics

  1. What were the forecast and forecast error for the week in which actual demand was 106106 units?
    Answer: The forecast was 9494 units, and the error was 1212 units. When you see a moving average question, your first job is to identify which periods feed into the forecast. A trailing three-week moving average uses the three most recent weeks of actual demand to predict the next week. Here, the four weeks of demand (oldest to newest) are 82, 94, 88, and 100. To forecast the week when actual demand was 106, you use the three weeks immediately before that week — which are 94, 88, and 100 (not 82, since that data is now too old). The forecast is: 94+88+1003=2823=94 units\frac{94 + 88 + 100}{3} = \frac{282}{3} = 94 \text{ units} Forecast error is defined as actual minus forecast: 106−94=+12 units106 - 94 = +12 \text{ units} That confirms A is correct. B is wrong because it averages all four weeks — 82, 94, 88, and 100 — giving 3644=91\frac{364}{4} = 91. That's a four-week average, not three, and it misapplies the model. C uses the right forecast of 94 but flips the sign of the error, reporting −12-12 instead of +12+12. This would mean the forecast exceeded actual demand, which isn't the case here — the retailer under-forecast. D averages the wrong three weeks — 82, 94, and 88 — ignoring the most recent period (100). Always count from the most recent data backward. A useful habit: underline or list the data points in order and cross off any that fall outside the moving-average window before you calculate.
  2. What forecasts should the model produce for the three months?
    Answer: It should forecast 210210 for July, 210210 for August, and 210210 for September. When you see a question about simple exponential smoothing (SES), the key concept to anchor on is that SES produces a flat forecast: without a trend or seasonal component, every future period gets the same predicted value — the most recently smoothed level. Here's the core logic: the SES update formula produces a single number, the smoothed level, which becomes your best estimate of the future. Once you've incorporated June's actual sales, the model yields a smoothed level of 210210. Because the model has no mechanism to project growth, decline, or seasonal patterns, that 210210 is simply carried forward indefinitely. July forecast = 210210, August forecast = 210210, September forecast = 210210. The model doesn't "wait" for new data — it gives you its best guess right now, and that guess is the same flat value for all future horizons. D is correct. Answer A is wrong because SES doesn't leave future forecasts undefined — it always produces a value, even without new actuals. Leaving forecasts blank would make the model operationally useless for multi-period planning. Answer B reflects a misunderstanding: the smoothing constant α\alpha determines how quickly past observations are discounted in the update step, not how future forecasts decay period by period. Answer C confuses SES with trend-adjustment methods like Holt's exponential smoothing, where a trend component is explicitly updated using forecast errors — SES has no such mechanism. A useful study tip: whenever a question specifies "no trend or seasonal component," that's your signal that all multi-step-ahead forecasts collapse to a single flat value. Recognizing model assumptions is half the battle on forecasting questions.
  3. Which evaluation of the analyst's procedure is most accurate?
    Answer: It is invalid because realized June and July revenue would not have been available at the end of May. When evaluating any forecasting or smoothing procedure, the critical question is: what information was actually available at the time the forecast was supposedly made? This is the concept of data availability, and violating it produces what analysts call "look-ahead bias." Here, the analyst uses May, June, and July revenue to compute a centered three-month average, then claims this value represents a forecast available at the end of May. The fatal flaw is that June and July haven't happened yet at the end of May — those values exist only in hindsight. The procedure smuggles future data into a "past" forecast, making any backtest or historical evaluation artificially optimistic. Answer A correctly identifies this: the centered average is mathematically fine for smoothing historical data, but it cannot be relabeled as a real-time forecast without a fundamental logical error. Answer B is wrong because equal weighting has nothing to do with the problem. Whether weights are equal or unequal doesn't make unavailable data suddenly available. Answer C misidentifies the issue — the weighting scheme is irrelevant here. The flaw isn't how months are weighted but which months are included. A forecast using only heavier weights on May still wouldn't fix the July data problem. Answer D is wrong because stable seasonality and low variance don't retroactively make future data observable; those are conditions about the series' behavior, not about when data becomes known. Study tip: On any forecasting question, always trace the timeline — ask "what did the analyst know, and when?" If a model uses data from period t+1 to forecast period t, it's look-ahead bias regardless of how elegant the math looks.
  4. After incorporating both actual observations, what is the forecast for June?
    Answer: The June forecast is 130.8130.8 units. Simple exponential smoothing questions test your ability to apply a recursive formula — meaning each new forecast feeds into the next. The key insight is that you must update the forecast twice here: once using April's actual demand to get the May forecast, then again using May's actual demand to get the June forecast. Starting with what you're given: the April forecast is FApril=120F_{April} = 120 and actual April demand is AApril=150A_{April} = 150. Plug into the formula to find the May forecast: FMay=0.30(150)+0.70(120)=45+84=129.0F_{May} = 0.30(150) + 0.70(120) = 45 + 84 = 129.0 Now use the May forecast alongside actual May demand (AMay=135A_{May} = 135) to forecast June: FJune=0.30(135)+0.70(129.0)=40.5+90.3=130.8F_{June} = 0.30(135) + 0.70(129.0) = 40.5 + 90.3 = 130.8 That confirms B is correct. Choice A (129.0) is the May forecast, not June — a classic "stopped one step too early" trap. Choice C (135.0) simply uses actual May demand as the June forecast, ignoring the smoothing mechanism entirely. Choice D (139.5) likely results from mistakenly applying the weights in reverse — using (1−α)(1-\alpha) on the actual demand and α\alpha on the prior forecast, which swaps the formula's logic. A useful habit: whenever a problem says "after incorporating both observations," mentally count how many times you need to apply the formula. Write out each step sequentially so you don't confuse an intermediate result for the final answer.
  5. How does the weighted forecast compare with an unweighted three-month moving-average forecast?
    Answer: The weighted forecast is 172172 units, which is 1212 units above the unweighted forecast. Forecasting questions like this one require you to compute two different averages and compare them — don't stop after finding just one. The weighted moving average multiplies each period's value by its assigned weight, then sums the results. Using the given data (most recent to oldest: 200, 160, 120) with weights 0.50, 0.30, and 0.20: Weighted Forecast=(200×0.50)+(160×0.30)+(120×0.20)=100+48+24=172\text{Weighted Forecast} = (200 \times 0.50) + (160 \times 0.30) + (120 \times 0.20) = 100 + 48 + 24 = 172 The unweighted (simple) moving average treats all three months equally, dividing their sum by 3: Unweighted Forecast=200+160+1203=4803=160\text{Unweighted Forecast} = \frac{200 + 160 + 120}{3} = \frac{480}{3} = 160 The difference is 172−160=12172 - 160 = 12 units, confirming that C is correct — the weighted forecast exceeds the unweighted forecast by 12 units. A gets the direction backwards: 148 would result from weighting the oldest month most heavily (0.50 on 120), which inverts the weight assignment. B claims both forecasts are equal at 160, which is only true for the simple average — assigning heavier weight to the most recent (and highest) value must pull the forecast upward. D uses plausible-looking numbers but doesn't correspond to any standard calculation with the given weights; it likely results from a weight-application or arithmetic error. A useful study tip: when weights are ordered from most-recent to oldest, heavier recent weights always pull the forecast toward the most recent value. If the trend is rising, the weighted forecast will exceed the simple average — use that as a quick sanity check.
  6. Which assessment of the proposal is most appropriate?
    Answer: Both changes will likely increase lag; shorter windows and larger smoothing constants react faster, although neither method explicitly models trend. Whenever you see forecasting questions involving lag, focus on how quickly each method responds to recent changes. A forecast that consistently falls below rising actual values is exhibiting lag — the method is too slow to follow an upward trend. The fix is to make the model more responsive, not less. For a simple moving average, a shorter window increases responsiveness because fewer past observations dilute the influence of recent data. Extending the window does the opposite — it averages in more older, lower values, pulling the forecast further behind reality. For simple exponential smoothing, a larger smoothing constant (α\alpha closer to 1) places heavier weight on the most recent observation, reducing lag. A smaller α\alpha weights history more heavily, slowing the model's reaction. The manager proposes the exact opposite of both corrective actions — a longer window and a smaller α\alpha — which will each worsen the lag problem. Answer A correctly identifies this: both changes increase lag, and crucially, neither method inherently models trend regardless of parameter choice. Answer B is wrong because it reverses the logic entirely — longer windows and smaller smoothing constants do not emphasize recent observations more. Answer C is wrong because it correctly diagnoses the smoothing constant but incorrectly claims a larger window reduces lag, when it actually increases it. Answer D is wrong for the mirror reason — it correctly identifies that a larger window slows the moving average but incorrectly claims a smaller smoothing constant reduces lag. A reliable rule of thumb: more history = more lag. Longer windows and smaller α\alpha values both incorporate more historical data, always moving in the direction of slower response.
  7. After three forecast updates, by how much will their forecasts differ?
    Answer: Their forecasts will differ by 4.324.32 units. When you see a question about simple exponential smoothing (SES), remember the core update formula: Ft+1=α⋅At+(1−α)⋅FtF_{t+1} = \alpha \cdot A_t + (1-\alpha) \cdot F_t. The key insight is that any difference in initial forecasts shrinks geometrically with each update, because each new forecast retains only (1−α)(1-\alpha) of the previous forecast's influence. Here, α=0.40\alpha = 0.40, so (1−α)=0.60(1-\alpha) = 0.60. Both analysts observe identical actual values, meaning the only source of divergence is their differing starting forecasts. After each update, the gap between their forecasts is multiplied by 0.600.60. Starting with a difference of 2020 units, after three updates the gap becomes: 20×(0.60)3=20×0.216=4.32 units20 \times (0.60)^3 = 20 \times 0.216 = 4.32 \text{ units} That confirms B is correct. Now for the distractors: A (3.20 units) results from mistakenly multiplying by (1−α)3(1-\alpha)^3 using α\alpha itself — specifically, 20×(0.40)3=20×0.032×520 \times (0.40)^3 = 20 \times 0.032 \times 5... actually it reflects using only α\alpha once, like 20×0.40×(0.40)=3.2020 \times 0.40 \times (0.40) = 3.20, confusing which weight drives persistence. C (7.20 units) comes from applying the decay factor only twice instead of three times: 20×(0.60)2=7.2020 \times (0.60)^2 = 7.20. This is an off-by-one error — a very common trap when counting update periods. D (12.00 units) applies the factor only once: 20×0.60=12.0020 \times 0.60 = 12.00, as if only a single update occurred. Your study tip: always track how many updates have occurred — each update multiplies the initial difference by (1−α)(1-\alpha), so after nn updates, the gap is Δ0×(1−α)n\Delta_0 \times (1-\alpha)^n. Off-by-one errors on nn are the most common mistake here.
  8. After the post-promotion actual value of 100100 is incorporated, what will the two models forecast for the next week?
    Answer: The moving-average forecast will be about 126.67126.67, and the exponential-smoothing forecast will be 115115. When comparing forecasting models, always track how each one handles a temporary spike — they "forget" the anomaly at different speeds, which is exactly what this question tests. For the three-week moving average, after the post-promotion week you incorporate the actual value of 100. The three most recent observations are now: the promotion week (180), the post-promotion week (100), and one pre-promotion week (100). The forecast is 180+100+1003=3803≈126.67\frac{180 + 100 + 100}{3} = \frac{380}{3} \approx 126.67. The spike is still sitting in the window, so the model remains distorted. For exponential smoothing (α=0.25\alpha = 0.25), you apply the update formula twice. After the promotion week: Fpromo+1=0.25(180)+0.75(100)=45+75=120F_{\text{promo+1}} = 0.25(180) + 0.75(100) = 45 + 75 = 120. Then, after incorporating the post-promotion actual of 100: Fnext=0.25(100)+0.75(120)=25+90=115F_{\text{next}} = 0.25(100) + 0.75(120) = 25 + 90 = 115. The model has partially recovered but still carries residual memory of the spike. This confirms C as correct. Choice A is wrong because it gives the moving average as 100, as if the spike never happened — the 180 is still inside the three-week window. Choice B gets the moving average right but stops exponential smoothing one period too early, reporting 120 instead of applying the second update to get 115. Choice D swaps the two model results entirely, which would only make sense if you confused which formula belongs to which model. The key study tip: moving averages retain a distortion for exactly as many periods as the window length, while exponential smoothing dilutes it gradually. Know both update formulas cold, and always count how many times you need to apply each one.
  9. Which combination correctly identifies the smoothing constant and the forecast made after observing 105105 calls?
    Answer: The smoothing constant is 0.250.25, and the new forecast is 9090 calls. Whenever you see a simple exponential smoothing question, your first move should be to recover the smoothing constant α\alpha from the information given, then apply it forward. The exponential smoothing formula is: Ft+1=Ft+α(At−Ft)F_{t+1} = F_t + \alpha(A_t - F_t), where FtF_t is the prior forecast, AtA_t is actual demand, and α\alpha is the smoothing constant. Here, the forecast was 8080, actual was 100100, and the updated forecast became 8585. Plugging in: 85=80+α(100−80)85 = 80 + \alpha(100 - 80), so 5=20α5 = 20\alpha, giving α=0.25\alpha = 0.25. Now apply this to the next period: F=85+0.25(105−85)=85+0.25(20)=85+5=90F = 85 + 0.25(105 - 85) = 85 + 0.25(20) = 85 + 5 = 90. That confirms answer B — the smoothing constant is 0.250.25 and the new forecast is 9090 calls. Answer A uses α=0.20\alpha = 0.20, which doesn't satisfy the first equation: 80+0.20(20)=84≠8580 + 0.20(20) = 84 \neq 85. It's a plausible-looking round number, but it fails the back-check. Answer C claims α=0.75\alpha = 0.75, which would produce 80+0.75(20)=9580 + 0.75(20) = 95, far from 8585 — this reflects a misreading of how heavily the actual demand is weighted. Answer D uses α=0.80\alpha = 0.80, giving 80+0.80(20)=9680 + 0.80(20) = 96, also inconsistent with the given updated forecast of 8585. Your key study tip: always **solve for α\alpha first** using the given forecast update before doing any forward calculation. Questions like this often provide enough data to pin down α\alpha exactly — use it as your anchor, then the second calculation becomes straightforward.
  10. Which team's next forecast will show the largest immediate upward revision?
    Answer: Team 4, because exponential smoothing increases its forecast by exactly 2020 units. When comparing forecasting methods, the key question is: how much weight does each method place on the most recent observation? That single weight determines how aggressively a forecast reacts to new data. For a moving average, each period in the window receives equal weight of 1n\frac{1}{n}. Team 1's three-period average gives the new observation weight 13\frac{1}{3}, so its revision is 13×(140−100)=13.33\frac{1}{3} \times (140 - 100) = 13.33 units. Team 2's six-period average gives weight 16\frac{1}{6}, producing a revision of only 6.676.67 units. For exponential smoothing, the revision equals α×(actual−forecast)\alpha \times (\text{actual} - \text{forecast}). Team 3 revises by 0.20×40=80.20 \times 40 = 8 units, and Team 4 revises by 0.50×40=200.50 \times 40 = \mathbf{20} units. Team 4 shows the largest jump, confirming D is correct. Choice A is tempting because 13.3313.33 is larger than both exponential smoothing values and Team 2's revision — but it's not the largest overall. Choice B is the smallest revision of all four, not the largest. Choice C correctly calculates Team 3's revision but misidentifies it as the winner; 8<208 < 20. The trap in A and C is failing to compare all four methods before selecting an answer. Study tip: Always map each forecasting method to its "effective weight on the newest data point" — 1n\frac{1}{n} for moving averages and α\alpha for exponential smoothing. Whichever method has the highest effective weight will react most strongly to any surprise in demand.

Start this quiz