Reports assembled from records
The monthly client report and the internal overdue view, both built from the work as it was recorded rather than written from memory.
- Starting point
- The last report you issued, traced section by section
- First live report
- Two to four weeks, depending on source systems
- Honesty rule
- A section with no source record is shown as having none
- Delivery
- Scheduled email, portal view, or both
Reporting is an assembly problem before it is a charting problem. We trace every section of the report you already issue back to the record that should produce it, build the sections that have a source, and tell you plainly which sections have none. A person approves the client report before it goes.
- 01 Enquiry
- 02 Systems audit
- 03 Specification
- 04 Build
- 05 Pilot
- 06 Deploy
- 07 Handover
- 08 Support
Reports assembled from records sits at step 4 of the build cycle. You receive a working increment you can use.
A dashboard cannot invent data nobody captured
Most reporting projects are sold as visualisation and fail as data capture.
We start by taking the report you issue today and drawing a line from each section back to where its numbers come from. Some lines land on a system. Some land on a spreadsheet one person maintains. And two or three land nowhere at all, because that section has always been written by somebody who was there.
Those last sections are the whole project. You can either start capturing that information, which means changing what somebody does on site, or you can accept the section stays manual and stop pretending otherwise. Both are fine. What does not work is a dashboard with a beautifully rendered number nobody can trace.
The same applies to targets. A percentage against an SLA means nothing until somebody has agreed what counts as met, what counts as excluded and who decides a dispute. On time against the requested date or the promised date? Does a job paused for a client's decision count against you? We ask those questions early, they are usually more uncomfortable than the technical ones, and the answers go into a definitions sheet kept as a controlled document.
What a reporting layer covers
| Output | What it does |
|---|---|
| The client report | Your monthly document, in your format, assembled from the period's records with the evidence attached. It waits for the account or contract manager's approval, and the approval is logged with the report. |
| The overdue view | One page of what is late, how late and with whom, across every workflow. The least popular and most used page we build. |
| Operational dashboard | Live status for the people doing the work: today's queue, this week's due dates, what is blocked and why. |
| Management digest | A short scheduled email, written for somebody who will read it on a phone, with a link into the detail. |
| Trend views | The same measure over time and across sites, which is where a recurring problem stops looking like bad luck. |
| Data export | Everything behind every chart, downloadable, because sooner or later somebody needs to check a number themselves. |
What lands in the inbox
The source map
Every section of your report traced to the record that produces it, with the gaps marked. Produced first, kept by you.
The definitions sheet
What each measure counts, what it excludes and who owns the rule. This is the document that stops two managers arguing about the same number.
The assembled report
Issued on schedule in your format, with the underlying records linked rather than summarised away.
The overdue register
Live, filterable, and exportable to the meeting where it will be discussed.
A scheduled digest
Short, on a fixed day, with the three things that changed since the last one.
The data export
Everything behind every chart, in a file your own team can open and check.
Three days of report writing, traced
A third-party logistics operator in Dammam reports monthly to a shipper on on-time dispatch, inventory accuracy, damage and an HSE section. Its account manager spends three days building the report.
The source map shows dispatch data in the warehouse system, inventory accuracy in a cycle-count spreadsheet, damage reports scattered across emails and the HSE section written from memory.
The definitions sheet is agreed with the shipper first, including what on time is measured against. Dispatch and inventory are read directly. Damage reports move to a short capture form with a photograph. The HSE section stays manual and is marked as written by the HSE officer.
The report assembles in the first week of the month and waits for the account manager's approval. The operator holds the source map, the agreed definitions sheet, the report template and an overdue register its supervisors see every morning.
Two audiences, two different pages
The most common reporting mistake is building one screen for both. They want opposite things.
Evidence, in their format, on a date
A client report is a contractual artifact. It is read by somebody checking whether you did what you said, and it is filed. What matters is that the evidence is attached, the format does not drift month to month, and it arrives on the day it is due.
- The format matched to the report you already issue, not to our template
- Evidence linked from the report rather than described in it
- A person approves before issue, every time
- Issued on a schedule, with the assembly starting early enough that gaps can still be filled
What is late and who has it
Internally the report is a work list, not a document. It should be uncomfortable, current, and specific enough that nobody has to ask a follow-up question before acting.
- Named owners on every overdue line, because a team is not an owner
- Age of the delay, not just its existence
- Filters that match how the work is actually divided
- No vanity measures, because they crowd out the ones that change behaviour
About dashboards and monthly reports
Can you build this on top of the systems we already have?
Usually yes, and it is the first option we look at. Where your data lives in a product with a usable interface we read from it directly. Where it lives in a spreadsheet one person maintains, we will say plainly that the spreadsheet is now a production system and ask what happens when that person is on leave.
What if some of the data does not exist?
Then the source map says so, and you decide. Either somebody starts capturing it, which is a change to how work is done and should be costed as one, or the section stays manual and is marked as manually written. A gap stays visible as a gap on the report, rather than covered by an estimate and a confident-looking chart.
Do you use a BI tool or build it?
Whichever is cheaper for you to keep running. If your data lands cleanly in a warehouse and your team already has a BI licence, using it is the right answer and we will set it up rather than sell you a build. Custom reporting earns its place when the output is a formatted client document rather than a chart, which in this market it usually is.
What drives the cost?
The number of source systems, how clean their identifiers are, how many report formats you have to produce, and whether measures are already defined or need agreeing with your team. One source system and one report format is quick. Five sources that disagree about what a site is called is where the time goes.
How do we stop the report drifting over time?
The definitions sheet, and a review of it whenever a measure changes. Reporting rots quietly: somebody adds an exclusion, somebody else changes a category, and a year later the trend line means two different things at either end. Keeping the definitions as a controlled document is the only fix we have seen work.
Feeds off
Document and report generation
When the report is a formatted document rather than a screen.
Read moreDigitalAudit and inspection apps
The capture layer that produces most of what a monthly report contains.
Read moreDigitalSystems integration
Getting the numbers out of the systems that already hold them.
Read moreDigitalWorkflow automation
The overdue view is only useful if something escalates off the back of it.
Read morePart of one system
Every division keeps records to the same standard, so the second one you need works the way the first one did.
Bring last month's report
The fastest way to scope this is the document you already issue. We trace it back section by section and hand you the source map.