From reports to planning: budgets and forecasts from your system data
In the previous lesson we covered building reports and a dashboard you can trust. A report tells you what happened, but an owner's biggest decisions are about what will happen: how much do we buy next month, when do we hire, can we carry the payments on a new machine? In this lesson we move from reading the past to planning ahead using the same data already sitting in your system, with no extra tools and no guesswork.
Report, forecast, budget: three different things
These three words get mixed together and produce meetings that end without a decision. A report describes what actually happened. A forecast is an estimate of what is likely to happen based on a past pattern. A budget is a decision about what you intend to spend and collect, one you commit to and are held to. The practical difference is that a forecast changes whenever new data arrives, while a budget only changes by an explicit decision from whoever owns it. When a team blurs the three, you hear "the budget was wrong" — when usually the forecast moved and nobody met to revise the budget.
Start with one clean year
Planning needs consistent data more than it needs a lot of data. Pull at least one full year from your system for three things: sales by month and by item, purchases by supplier, and fixed versus variable expenses. Before you calculate anything, clean out what distorts the picture: cancelled invoices, the test transactions entered during implementation, and the one exceptional deal that will not repeat. A single large deal left in the base will lift your average and push you into buying stock that will not sell.
A concrete example: a spare parts warehouse
A business sells spare parts, and one item sold this over the last six months: 120, 140, 90, 130, 160, and 150 units. The monthly average is about 130 units. The supplier's lead time is three weeks, so roughly 100 units sell while you wait for the shipment. If you waited until stock ran out, sales would stop for three full weeks. So you set a reorder point at 130 units: 100 to cover the lead time, plus 30 as safety stock for a high month like month five. The arithmetic is simple, but it rests on your system's data rather than on the storekeeper's gut feel.
What you can plan straight from your system
| Decision | Data needed | Question it answers |
|---|---|---|
| Purchase quantity | Monthly sales rate and lead time | When do I reorder, and how much? |
| Cash flow | Customer collection dates and supplier payment dates | Will the balance cover next week? |
| Hiring | Orders per employee and turnaround time | Is the team past its capacity? |
| Pricing | Item cost and actual margin | Which items am I selling at a loss? |
Seasonality is not a detail
A single annual average hides large swings. The Saudi market has clear seasons — Ramadan, the two Eids, back-to-school, and the summer holiday — and every sector behaves differently across them. The practical method is to compare each month against the same month last year rather than against the month before it, because month-on-month comparison mixes the underlying trend with the season. Also note the known reason next to every unusual month, so you do not rebuild a forecast on an event that will not repeat.
Review monthly, change by decision
Make the plan review a short monthly meeting comparing three columns: what we planned, what happened, and why they differ. A variance is not always a mistake, but it is always information. If the same variance shows up three months running, the problem is in the plan's assumption, not in execution — and then you change the assumption by a written decision from whoever owns it, with the date recorded, so six months later you know why the numbers moved.
Checklist before approving next month's plan
- Have cancelled invoices and exceptional deals been removed from the base?
- Did you compare against the same month last year, not the previous month?
- Does every number in the plan have an owner who can act on it?
- Have you calculated lead time and safety stock for each fast-moving item?
- Does the cash plan come before the purchase plan, or after it?
- Is the monthly review date already in the calendar?