The short answer
A multi-site report is slow because of gathering, not writing. Each site records its day in its own way and its own systems, so someone chases every source, lines the numbers up and checks they agree. Automate that in three parts. Collect from every site at the same time, reconcile what was collected, then write the report with every figure linked to where it came from.
The order matters. Teams often start by asking a model to write the report, which is the part that was never slow, and end up with fluent text over unchecked numbers.
I built this for a field operations business whose daily report took about three days to compile, and the result is further down the page.
1. List every source, site by site
Write down where each number in the current report comes from, for every site. A system export, a spreadsheet, a form, an email from a supervisor, a paper log. Most teams find the report depends on more sources than anyone could name from memory, and on several that only one person knows how to read.
2. Collect from every site at the same time
Chasing sources one after another is what turns a morning's work into days. Give each site, or each kind of source, its own collector that fetches and reads the data on a schedule. They run in parallel, so the time to gather everything is the time of the slowest source, not the sum of all of them.
Each collector records what it fetched, from where and when, and says clearly when a source was missing or late. A missing figure reported as missing is fine. A missing figure filled with yesterday's number is how a report loses its readers.
3. Reconcile before anyone writes a word
Put all the collected data into one common shape and compare it. Totals that should match, counts that should add up, a site whose figures are far outside its usual range. A reconciler flags what does not agree and says which two sources disagree.
Disagreements are the most useful output of the whole system. They are usually real, a shift logged twice, a site using an old template, a system export cut short, and until now nobody had the time to find them.
4. Write the report with every figure traceable
Only now does a model write. Give it the reconciled data and the layout the managers already know, and have it produce the report end to end. Every figure carries a reference to the source it came from, so a manager who doubts a number can check it instead of taking it on trust.
Keep the judgement out of the writing step. If the report needs a view on why a site is behind, state the figures and let the manager draw the conclusion, or mark the comment clearly as a suggestion.
5. Deal with paper and spreadsheets honestly
Some sites will still use paper or a spreadsheet nobody else may edit. Read them as they are, a photographed log or an emailed sheet, and treat them as one more source with its own collector. Changing how every site records its day is a different project and should not block this one.
6. Run it beside the manual report first
For the first weeks produce both reports and compare them figure by figure. Where they differ, find out which is right. It is not always the manual one. When the differences are explained and rare, the automated report takes over and the manual one stops.
What changes for the people who compiled it
The chasing and the copying go. What stays is the part that needed them, following up the disagreements, talking to the site that is late and deciding what the numbers mean. The report also arrives while the day it describes still matters.
When this is the wrong project
If every site already reports into one system, you do not need collectors. You need a better report from that system, which is a much smaller job.
If the sites cannot agree what a figure means, automation will produce a fast report that nobody believes. Agree the definitions first, even if only for the handful of numbers that matter most.
The three parts
| Part | What it does | Why it comes in this order |
|---|---|---|
| Collectors | Fetch and read each site's sources in parallel | Gathering is where the days go |
| Reconciler | Merges the data and flags what disagrees | Numbers must be checked before they are written up |
| Reporter | Writes the report with a source for every figure | Writing is fast once the data is trusted |
Where to start
Start with the report that takes longest and matters most, and with three or four sites that cover the different ways of recording. Getting those right teaches you most of what the rest will need.
Measure the time from the end of the day to the report being read, before and after. That is the figure the business feels.