Automated Status Reports & Weekly Metrics
Every Monday at seven the same report sits in the same inboxes: the figures of the week, the change against the previous week and the source behind every single number. If a system does not answer, the gap stays in the report – nothing is estimated.
Sending the report is not the work, collecting it is
The Monday report is usually built on Monday morning: an export from the ERP, a list from the CRM, a column from time recording, plus the spreadsheet somebody has been maintaining on the side for years. Two hours later the numbers sit in a slide or an email. The work is not hard, it just cannot wait: the meeting starts at nine.
The difficulty sits one level below. Most metrics are not defined, they are habitual. What counts as order intake: the date on the order confirmation or the booking in the ERP? Are cancelled orders included? Do installation hours cover the Friday shift that two fitters only book on Monday? As long as a person builds the report, they answer those questions afresh every week – in their head, without noticing, and usually correctly.
Those silent decisions are the actual project. Automation decides nothing new; it repeats on time what was settled once. So the first job is to write down, metric by metric, which system is authoritative, which filter applies, when it is read and what happens when a source stays silent. After that the report writes itself – and a comment can state what has changed without pretending to know why.
Which reports are worth automating
We start with the report that is written every week anyway and has the most recipients. Further reports later draw on the same definitions.
Weekly report for the management team
The most common starting point: six to ten metrics, Monday morning, always the same order and the same definition. Anything missing stays visibly empty.
Sales report with pipeline
Quotes, closed deals and stalled opportunities from the CRM – including the quotes that have gone two weeks without an answer.
Project and site status
Hours, materials, dates and variations per project. Site management receives the full version, the client a shorter one.
Figures for finance and cash flow
Outstanding invoices by due date, incoming payments, items already chased – daily instead of at month end.
Reports to clients
Agencies and service providers report outwards each month: the same data, a different level of detail, without internal metrics.
An alert instead of a report
Not every figure needs a weekly rhythm. When a value crosses its threshold, a short alert goes to one person straight away – and the figure still appears in the weekly report.
What a report page looks like
A weekly report from a trades business: five metrics, the comparison with last week and, under every value, the source it came from.
| Metric and source | This week | Last week | Change |
|---|---|---|---|
| Quotes sent CRM · status sent · read Mon 06:05source read | 34 | 29 | +5 |
| Order intake ERP · booked orders, cancellations excluded · read Mon 06:05source read | €96,400 | €118,200 | −€21,800 |
| Quotes without an answer > 14 days CRM · quote date, status open · read Mon 06:05source read | 11 | 8 | +3 |
| Installation hours Time recording · as of Fri 18:00, two fitters without a Friday entryentry to confirm | 412 h | 431 h | −19 h |
| Open complaints Ticket system · unreachable at 06:05value missing | — | 3 | no figure |
The small line under each metric is the real difference: it says which system the value came from and when it was read. Without it, every follow-up question starts with a search.
The colours judge the source, not the figure. A drop in order intake is not an error, incomplete time recording is. That is why the missing complaints figure appears as a gap in the report rather than as a zero.
From the definition to the delivered report
-
Pin down the metrics
For each figure we record the authoritative system, the filter, the period, the read time and the role that answers for it. This step takes the most discussion and decides everything that follows.
-
Connect the sources
ERP, CRM, time recording, spreadsheets or a database are read through an interface, a query or a scheduled export. Every read is time-stamped, and that stamp later appears in the report.
-
Check rather than smooth
Before the report is built, plausibility rules run: missing values, unexpected zeros and jumps beyond an agreed limit. Anything odd is flagged, not quietly corrected.
-
Generate report and comment
The checked values become the report page with the previous-week comparison and the source line. The comment turns the changes into sentences – drawn only from figures that are in the report.
-
Distribute and archive
Delivery by email, into a Teams channel or as a SharePoint page, at the level of detail agreed per recipient group. Every version is archived with its date, so it stays traceable what was known on Monday.
What changes day to day
Today
- Two hours of gathering numbers every Monday
- Someone decides afresh each week what counts
- A question about a figure starts with a search
- Missing values are quietly filled in from memory
- When the responsible person is away, no report goes out
With an automated report
- The report is in the inbox before the meeting
- Every metric has a definition written down
- Under each figure: system, filter and read time
- Missing values appear as a gap in the report
- The report runs regardless of who is in the office
What an automated report will not do
We settle these four points before quoting. On the third one we regularly advise against the project:
- A report is no substitute for a definition. If sales and finance mean different things by order intake, automation makes that difference visible but not smaller. We can build in only one definition, and deciding which one is your call – before the project, not in the first meeting after go-live.
- The comment describes, it does not explain. It states changes, outliers and missing values in full sentences. Why order intake collapsed it does not know, and we do not let it guess. Anyone expecting a management assessment inside the report will not get one from this product.
- With a single source it is not worth it. A report somebody pulls out of one spreadsheet in ten minutes does not justify €1,290. The effort – and the benefit – only appears with several systems, competing definitions and a fixed distribution list. With one spreadsheet and three recipients we recommend a pivot table that refreshes on opening.
- Poor data quality becomes visible, not better. If orders are only entered in the ERP on Fridays, the Monday report shows exactly that. The first automated report is therefore usually uncomfortable: it exposes gaps somebody used to fill from memory while assembling the figures. That is intended, but it takes a few weeks of getting used to.
Fits your data sources
Scope and price
The entry price covers one report with up to eight metrics from up to three sources, including the comment, the distribution list and filing.
- Up to eight metrics with a documented definition
- Connection of up to three data sources (interface or export)
- Report layout in your visual identity, as email and PDF
- Comparison with the previous period and a source per figure
- Automatically generated comment following your wording rules
- Schedule, distribution list and filing in SharePoint or a file store
- Documentation, handover session and 30 days of support
What increases the price
- More than three source systems, or sources without an interface
- Several recipient groups with different levels of detail
- Metrics that have to be calculated first, such as margin per order
- Twelve months of history instead of a previous-week comparison
- An additional dashboard alongside the delivered report
Several recipient groups, calculated metrics or sources without an interface typically land in the range of our Workflow Advanced package from €2,490. We quote the binding fixed price after the intro call.
All prices excl. VAT · operation and further development optionally via a support package
What you get
-
Metric definition sheet
Per figure: definition, authoritative system, filter, read time and accountable role – the document that makes the report auditable later
-
Live report delivery
Schedule, distribution list and filing set up and signed off with two complete test runs
-
Rules for exceptions
What happens on a missing source, an empty value or an implausible jump, and who gets notified
-
Training for your team
How to add a metric, change a definition and take on a new recipient
Frequently asked questions about automated status reports
These solutions fit alongside
Automated Weekly Team Digest
The same mechanics one level down: built from tasks and open items rather than metrics.
Automated Spreadsheet Data Sync
For the metric that comes from a spreadsheet which has to be current itself first.
API Integration
When a source system has no ready-made interface and access has to be built.
Customer Feedback & NPS
A metric that exists in no system and has to be collected before it can be reported.
How long does your Monday report take?
In the free intro call we walk through your last report line by line: which figure comes from which system, who collects it today and what definition sits behind it. Afterwards you know whether automating it pays off – or whether two metrics fewer would be the better starting point.
Book a free intro callWhere automated status reports creates value in everyday work
Status data from projects and systems is consolidated on schedule, checked for exceptions and distributed to the right audience in Microsoft 365.
Three concrete operating scenarios to compare with your own process.Consolidate project status
Tasks, risks, budget and milestones flow into one consistent report.
Highlight exceptions
Only relevant changes and missing data are flagged for review.
Tailor distribution
Teams, leadership and customers receive suitable detail instead of the same file.
A strong fit when …
Microsoft 365 is already the main workplace and information should move reliably between Teams, SharePoint, Outlook and Planner.
- You handle recurring reports using repeatable rules.
- The intake, target system and accountable business role can be named clearly.
- Exceptions are allowed to remain visible and move to people deliberately.
Deliberate automation boundary
Interpretation, forecasting, prioritisation and management statements are not generated autonomously from incomplete data.
Explore the technical approach and platformsEstimate time savings with your own volume
The calculator uses 45 minutes today and 10 minutes after automation as fixed example assumptions. It does not replace process analysis.
Illustrative estimate based on the visible assumptions — not a guarantee.
Order intake is €21,800 below the previous week, with five more quotes sent. Eleven quotes are older than 14 days, three more than last week. Installation hours do not yet include the Friday shift of two fitters. No figure is available for complaints; the ticket system did not answer at 06:05.
infoThe comment only states what the figures say. Cause and judgement are added by the sales lead in two sentences underneath.