The board meeting is halfway through the month. On the table is the management report on the previous month, compiled in the first week of this one. The figures describe a period that is already weeks behind us, and the decisions being taken today, on purchasing, staffing and a campaign, are about the coming week.
That is the mechanism behind deciding on outdated figures. It is not unwillingness and rarely a lack of data. It is a rhythm problem: the report appears monthly and takes days to compile, while some decisions are taken weekly or daily. In those places, the board steers on a reality that no longer exists.
The report describes a month that is over
A management report is nearly always put together by hand. Someone exports figures from the ERP, combines them with the pipeline from the CRM and the results from the accounts, and turns it all into an overview. That takes days, and every day makes the figures older. By the time the report is presented, it describes a snapshot from a few weeks back.
So the delay sits in two places: in the rhythm (once a month) and in the compiling (days of manual work). Why the compiling takes so long and what can be done about it is covered in a slow month-end close starts on the first of the month. This article is about the other side: what the board does with that delay.
Not every decision needs current figures, but some do
The reflex is to want everything current. That is neither necessary nor wise; an annual plan, an investment decision or a price change rests perfectly well on monthly figures, and a board that looks at revenue daily ends up steering on noise. The question is which decisions run faster than the report.
So put two things next to each recurring decision: how often it is taken, and how old the figures are that it rests on. Purchasing and stock, the staffing of a team, the cash position, adjusting a running campaign: these are decisions that are often taken weekly or more often. If they rest on a monthly report, that is where it hurts. A pricing policy or an annual budget can safely stay on the same monthly figures. Such an overview takes an afternoon and points precisely to which figures deserve a direct connection to the source, and which do not.
What outdated figures do
Steering on old figures makes a board reactive. A sales team on course for a strong month still gets a correction, because the report still shows the disappointing start. Purchasing reorders while last week’s clearance sale should already have worked through into the stock. A campaign gets budget for a product line that has already been scaled down internally.
The damage goes beyond those individual misses. Managers who know the report lags start keeping their own lists. Those shadow administrations fragment the figures further, and within a few months every meeting ends up on the question whose version is right. That is the moment outdated figures turn into contradictory ones; what that does to decision-making is described in the risks of deciding on inconsistent data.
Excel is a calculator, not a reporting source
Many organisations try to speed up the rhythm with Excel: a report that is updated more often. That moves the problem. Every update again needs someone to fetch, copy, check and format the data, so the report remains manual work and keeps lagging, just more often. Excel has no live connection to the systems where the figures arise, and a file with several tabs and formulas breaks silently: one wrong cell makes the report unreliable without anyone noticing. The risks of that copying work are in copy-paste between Excel and your business software.
For a small team with one or two systems, Excel can be enough for a long time. Once the board decides weekly on figures from three or four sources, it is too slow and too fragile to carry the primary reporting.
A dashboard on live sources changes the rhythm
A dashboard connected directly to the ERP, the CRM and the accounts fetches the figures as they arise. There is no compiling moment anymore, so no delay either; the board sees today’s position, not the one from three weeks ago. Just as important is the consistency: everyone looks at the same figures from the same sources, so the shadow administrations lose their reason to exist.
Two caveats belong here. A dashboard shows what is in the sources; if those do not agree with each other, it only shows the contradiction more sharply. And a dashboard that is not trusted or does not connect to a decision is no longer opened after a few months. How to prevent that is in trust in a dashboard disappears quietly.
Custom-built or a standard tool
Tools like Power BI go a long way, certainly when the figures come from one or two systems and standard connectors exist for them. Custom-built becomes the better choice when several systems need to be combined that cannot be connected out of the box, when the board needs composite KPIs or its own calculations, or when the dashboard has to live inside an existing customer portal or internal application rather than in a separate tool.
So the choice depends on the number of sources and the place where the dashboard has to live, not on what looks nicer. Often the integration of the sources is the real work, and the screen afterwards the smallest part.
Do you recognise the meeting where the figures are older than the decision? Start with the rhythm test: which decisions run faster than the report. For those figures we set up dashboards and reports that read directly from the source systems, so the board decides on today’s position.