Syntha Lab RU

Plan versus actual by store: pace, period forecast, required daily pace

Compares the actual to date with the plan for the whole period and with the pace-plan for the same number of days, forecasts the end of the period at the current pace and calculates how much must be sold a day to reach the plan. Shows which stores lag behind the pace and by how much.

Store sales and receipts: traffic, conversion, ticket For whom: Retail chain directors, regional managers and store managers.

Calculate on your data →

At a glance

What question does it answer?
Are stores on the plan pace, what is forecast for the end of the period and how much must be sold a day.
What data is needed?
Days in the period and days passed; by store the plan for the period and the actual to date; optionally last year’s actual.
How to read the result?
On the example of 4 stores 18 days into 30 the period plan is 13.5m, the actual 8.25m (61.1% of the plan), the pace-plan 8.1m: a deviation of +150,000 (101.9% of the pace). The forecast at the current pace is 13.75m. To reach exactly the plan 437,500 a day is needed against the current 458,333. Two of four stores are below the pace, the most “Mega” (−300,000). Against last year +0.6%. Example on the default values: Plan for the period: RUB 13.5 million; Actual to date: RUB 8.25 million · 61.1% of the period plan; Pace-plan to date: RUB 8.1 million; Deviation from the pace: RUB 150,000 · 101.9%. The figures are illustrative: enter your own to see your result.

Why and how to reason

In the middle of a period actual cannot be compared with the full plan: it will always be lower. So it is compared with the pace plan: plan × days elapsed ÷ days in the period. In the example the chain plan is 13.5 million for 30 days, 18 have passed, pace plan 13.5 × 18 ÷ 30 = 8.1 million, actual 8.25 million, so we are ahead by 150 thousand. Forecast for period end at the current pace: actual ÷ days elapsed × days in period = 8.25 ÷ 18 × 30 = 13.75 million. The needed daily pace to the end: (plan − actual) ÷ remaining days = 5.25 million ÷ 12 = 437.5 thousand a day. These three numbers answer three questions: where we are now, where we end up if nothing changes, and what to do to hit the plan. The chain as a whole does well, but two of four stores are below pace: “Mega” lags by 300 thousand.

When to use it

Use it every week during a period to react in time. It fits a chain and a single store. It does not fit when sales are sharply seasonal within the period (a sale at month end): the linear pace will mislead. Assumptions: sales are even across days (adjust manually for weekends and promotions); plan and actual exclude VAT; you set the tolerance for lag.

How to read the result

Start with “stores below pace” and “largest lag”: this is the list for conversations with store managers. Then compare “needed per day” with the current pace: if it must be 30% higher the plan is unrealistic without a promotion or a tolerance. Look at the forecast by store: the chain can finish in the green thanks to one strong store. Growth against last year shows whether a store lags behind itself or the plan is too high. Decisions: redistribute stock, strengthen staff, run a promotion in lagging stores or revise the plan. Repeat the calculation every week and record the decisions next to the figures.

Common mistakes

Taking elapsed days by calendar rather than store working days. Comparing cumulative actual with a plan split differently. Not updating actuals daily: the forecast gets stale. Another mistake: forgetting that a store plan may have been set without accounting for renovation, rearrangement or weekend closure.

What data is needed?

  • Days in the period and days passed; by store the plan for the period and the actual to date; optionally last year’s actual.

Inputs

FieldUnitValue in the exampleMeaning
Days in the perioddays30Calendar or trading days: count as the plan does.
Days passeddays18Not more than the days in the period.
Tolerance for lagging behind the pace%—Optional. A store below the pace by more than this percentage will be marked. There is no single standard in Russia: enter your own threshold from your own data.

How it is calculated

StepFormula
Pace-planperiod plan × days passed ÷ days in the period
Forecastactual ÷ days passed × days in the period
Needed per day(plan − actual) ÷ days left

Worked numbers

Default values from the app; in the interactive version you enter your own.

Plan for the period
13.5 m ₽
Actual to date
8.25 m ₽ · 61.1 % of the period plan
Pace-plan to date
8.1 m ₽
Deviation from the pace
150,000 ₽ · 101.9 %
Forecast for the end of the period at the current pace
13.8 m ₽ · 101.9 % of plan
Needed per day to the end of the period
437,500 ₽ · now 458,333 ₽
Stores below the pace
2 of 4
Below the pace beyond the tolerance
enter your own tolerance
Versus last year, % growth (minus is a fall; stores with data)
+0.6 %
Largest lag behind the pace
−300,000 ₽ · Mega

By store

StorePlanActualPace-planTo paceForecastTo planTo last year
Center5 m ₽3.3 m ₽3 m ₽110 %5.5 m ₽110 %10 %
Mega4 m ₽2.1 m ₽2.4 m ₽87.5 %3.5 m ₽87.5 %−16 %
North2.5 m ₽1.35 m ₽1.5 m ₽90 %2.25 m ₽90 %−15.6 %
South2 m ₽1.5 m ₽1.2 m ₽125 %2.5 m ₽125 %36.4 %

The forecast is linear: it ignores weekdays, holidays and the promotion calendar. For stores with sharp day-of-week seasonality compare with last year.

Nuances and limits

  • A linear forecast breaks down with strong daily and weekly swings: check against last year.
  • Comparing the actual to date with the plan for the whole period: the pace-plan for the same number of days is needed.

Terms used

Calculate on your data →