Recurring reports
The same report every week or every month, assembled from two or three systems that exchange nothing with each other.
How it goes now
Someone exports from one system, runs a report in the other, and puts the two side by side in a sheet. Columns in the right place, totals reconciled, formatting restored. The work is not difficult. It is the same every time, and it has to be done before the meeting starts.
How it goes afterwards
We record the assembly once: where each figure comes from, how it is combined, and what shape the report has to come out in. After that the assembly runs at the agreed moment. The report is there in the shape it always had, and every run records which sources were read and what they showed at the time.
Where you decide
During setup we agree with you what counts as a normal movement. A figure that shifts further than that does not pass unnoticed. The system sets that line aside, with the source and the previous value beside it, and asks whether it is right. You approve or reject; after that the report is final.
What it does not do
It does not explain the figures. It draws no connections, writes no commentary and reaches no conclusions. What is there is what the systems say; what it means stays the work of whoever presents the report. If a source system changes substantially the assembly has to be updated. The system watches the structure of the pages itself: if it sees a different layout on two separate jobs, it flags that page, so we usually see it before a job runs aground. Either way that is our work, not yours.
Tell us which reports you prepare, how often and where the data comes from. Together we can see whether we can take on this work.
Discuss your reports