Why Does Your Monthly Report Still Take Three Days to Prepare?

It's Monday morning, and the monthly report is due on Wednesday.

The reporting officer opens last month's workbook, creates a new copy and starts sending reminders to colleagues for their latest figures. Some departments have already submitted their reports, while others are still finalising their numbers. One department has sent an updated file, but it's not immediately clear whether it replaces the version shared on Friday.

By lunchtime, several spreadsheets are open. The figures need checking, the missing information needs following up, and the charts from last month need updating.

Then a familiar problem appears.

The total reported by one department doesn't match the figure in the consolidated workbook. So an an email goes out asking for clarification. The explanation comes back a few hours later with feedback indicating, one team included records that another team excluded. 

The figures are eventually corrected, the calculations updated, and work continues. But then, on a fine Tuesday afternoon, another revised spreadsheet arrives, and the workbook figures have to be recalculated.

By Wednesday, the report is finally ready.

And next month, much of the same work will happen again.

This is a hypothetical example, but the reporting challenges it illustrates are common in organisations that depend heavily on spreadsheets and manual processes.

The interesting part is that the report itself hasn't changed very much. The organisation is still collecting much of the same information, calculating the same indicators and producing similar charts.

So why does the process require so much effort every month?

Much of the work happens before the reporting begins

When people think about preparing a report, they often picture tables, charts and a written explanation of the results. Yet a surprising amount of work needs to get done before anyone gets to that stage.

There are files to collect, figures to verify, missing information to follow up and different versions of spreadsheets to reconcile. Sometimes the problem is as simple as two departments using different date formats. Other times, it is more complicated.

For example, imagine an organisation reporting the number of customers served during the month. One department counts every transaction, including repeat visits. Another counts each customer once, regardless of how many transactions they made. Both teams submit their figures on time and have followed their usual processes.

But when the numbers are combined, they tell different stories.

The reporting officer now has to establish which definition should apply, explain the differences and correct the figures. That is time spent resolving a problem that could have been addressed before the reporting period began. And when these issues are left unresolved, they tend to recur every month.

A similar situation happens when different teams use slightly different reporting templates, or when nobody is quite sure which spreadsheet contains the latest approved information. 

Over time, employees become very good at working around these problems. They know which colleague to call when report figures look unusual, remember which formulas need correcting, and know which files to check before submitting the final report.

The report gets done, but a great deal of its success depends on people remembering how to work around an inconsistent process.

Three days every month adds up

Because reporting is a regular responsibility, the time spent preparing it often becomes part of the normal workload. But consider what that time represents across an entire year.

Suppose three employees collectively spend 36 hours each month collecting information, checking submissions, correcting errors and preparing a management report.

That amounts to 432 staff hours annually.

If we use an illustrative staff cost of K100 per hour, the organisation is spending the equivalent of K43,200 a year on that recurring process.

Of course, not all of that time is wasted. Good reporting requires data validation, professional judgment and review. However, the question is how much of the work genuinely requires human attention.

If employees are spending hours copying information between spreadsheets, rebuilding the same charts or following up on errors that could have been flagged earlier, there may be opportunities to improve the process.

There is also the question of what those employees could be doing with some of that time.

A programme officer might have more time to examine why certain activities are falling behind. A sales manager could investigate changes in customer demand. A finance team could spend more time analysing expenditure and identifying unusual patterns.

These activities are part of the reason organisations collect information in the first place. Yet they can receive less attention than the work required to prepare it.

Imagine if month-end worked  differently

Imagine the same organisation a few months after improving its reporting process.

Departments now submit information using agreed templates. Important fields are checked when data is entered, and reporting definitions are documented so that everyone understands what should be counted.

Throughout the month, the reporting team can identify missing submissions and unusual figures rather than discovering them a day before the deadline.

The different datasets follow a consistent structure, making them easier to consolidate. While, recurring calculations and charts are updated through a repeatable, efficient process.

When month-end arrives, the reporting officer still has work to do. They review exceptions, check the results and confirm that the information is ready for management. But they no longer have to rebuild the entire report from scratch.

Instead of spending most of the reporting period collecting and correcting information, there is more time to examine what the results mean.

• Why did sales decline in one region?
• Which departments are consistently missing their targets?
• Why has expenditure increased while activity levels have remained unchanged?
• What changed since the previous month?

These are the conversations that make reporting valuable. They become easier when the information is organised, consistent and available when it is needed.

Where should an organisation begin?

Improving reporting does not always require purchasing new software. Sometimes the biggest gains come from addressing relatively basic issues that have been overlooked for years.

A useful starting point is to follow one report from beginning to end and identify:

• Where the information comes from? 
• Who collects it? 
• How it is submitted? 
• What needs to happen before the figures can be used?

Pay particular attention to the tasks that repeat every month.

Perhaps several employees are manually copying data from individual files into one master spreadsheet. That may be a good candidate for a more structured consolidation process.

Perhaps reporting officers spend hours correcting missing fields. Introducing data validation at the collection stage could reduce some of that work.

Or perhaps the biggest delays come from disagreements about indicator definitions. In that case, the priority may be documenting the calculations and agreeing on which records should be included.

Once those foundations are in place, tools such as Excel Power Query, Power BI and other reporting technologies can help automate suitable steps.

It is tempting to begin by building a dashboard because dashboards make the results visible. But if the data behind the dashboard is inconsistent, the same reporting problems can continue, only with more attractive charts.

A good reporting system depends on the processes feeding it.

What could better reporting look like for your team?

For one organisation, the improvement might be reducing the number of spreadsheets that need to be combined every month.

For another, it might be having a consistent definition of every key performance indicator.

For a third, it could mean building a dashboard that managers can consult throughout the month rather than waiting for a manually prepared report.

The specific solution will depend on the reporting requirements, available tools and the way the organisation works. What matters is being able to produce reliable information without repeatedly going through unnecessary steps.

If your team prepares the same report every month, it is worth looking closely at the process. It is worth interrogating:

• How much time is spent collecting and correcting information? 
• Which tasks are repeated? 
• Where do delays occur? 
• And how much time is left to actually analyse the results?

The answers may reveal opportunities to make reporting easier, more consistent and more useful.

How reliable is your reporting process?

At Kithms Enterprise, we help organisations improve recurring reporting through better data structures, standardised processes, dashboards and practical automation.

If your team regularly spends days preparing monthly reports, you can start by checking where the difficulties may be coming from.

Try our free Reporting Reliability Check to explore potential gaps in your current process and identify areas worth improving.

Explore the free tool: Free Tools

For organisations that need hands-on support, our Reporting Reliability Sprint provides a more focused way to examine reporting challenges and implement practical improvements.

Explore Kithms services