A report can be in the right folder, with the right name, and still be wrong. It might contain yesterday’s figures. It might have stopped halfway through. Someone might have downloaded it twice and refreshed the spreadsheet with the older copy.
That is the awkward part of automating morning reporting. The clicks are easy to count. The confidence people place in the finished report is harder to see.
The job began before the working day really could
In one business, an accounts assistant started the day collecting more than 20 reports from different systems. Those files fed spreadsheets used by other teams. The assistant’s work was repetitive, but the reports themselves mattered: people were waiting on them before they could use the numbers.
We moved the collection and refresh work overnight. Some systems could be reached through an API; others needed controlled browser steps. That freed up the morning, but it also changed the question. With a person doing the job, a failed download is usually obvious to that person. When the job runs at midnight, who notices?
A green tick needs to mean something
A successful run should mean more than ‘the script reached the end’. We needed to know that each expected file arrived, that it belonged to the current run and that a duplicate or failed export had not quietly been passed on. If a source changed, the team needed a failure they could act on, not a reassuring-looking folder full of files.
That distinction is easy to lose when an automation demo shows only the happy path. A missing report is inconvenient. A stale report that looks current can be worse, because nobody knows to question the decision made from it.
What we would ask before doing this again
We would ask which report somebody would miss first, who uses it, and how they currently check it. Then we would ask what happens if it does not arrive. Those answers tell us what the overnight job has to prove and who should hear about a failure.
The related case study sets out the time returned for this business. The lesson we took from the build is less about a number: moving work out of someone’s morning is only useful if they can still tell whether the result is safe to use.