A reporting portal has to support a conversation across time. Someone reads the report, asks why a result changed, receives an explanation and agrees an action. Later, they need to find that discussion without relying on the memory of whoever attended the meeting.
Our client reporting and action review project connects the report, its underlying records, management commentary and follow-up. The useful part is the relationship between them. A collection of attractive charts would leave much of that work in email.
Keep the reporting period separate from the action status
The sample report concerns September. Its action review is current to 30 October. Those dates describe different things: when the financial result occurred and when the team last reviewed the follow-up.
If a portal uses one prominent ?last updated? date for both, a reader may assume the reported figures have changed when only an action note has been added. Give the period, report review and action status their own meaning.
The same distinction matters when a previous month's report remains available. A customer should be able to return to the period they discussed without accidentally opening the current month in its place.
Explain the variance before asking for a decision
The report's operating profit is AUD 50,000 against a budget of AUD 65,000. The variance view reconciles the AUD 15,000 difference through a gross-profit gap of AUD 12,000 and AUD 3,000 of additional operating expenses.
It then names the cost lines: payroll is AUD 2,000 above budget and software is AUD 1,000 above. Premises and administration travel match the plan. The reader can move from a headline difference to a specific question.
Let the client trace the reported difference
The arithmetic is sample data from the project. It is valuable here because the explanation is reproducible. A customer can inspect the contributing records rather than having to accept an unexplained total.
Keep management's interpretation visible as an interpretation
The commentary links the project-revenue gap to two deliverables moving beyond the reporting cut-off. It does not turn that explanation into a promise about the following month.
The action is to obtain revised milestone dates before revisiting the forecast. This keeps a useful separation between a recorded result, an explanation and something that still needs confirmation.
A reporting portal should preserve those distinctions in the language. ?Management expects?? and ?recorded revenue is?? make different claims. Combining them in a dashboard headline can remove the uncertainty that the reader needs to understand.
An action needs an outcome, not just a tick
The project includes a completed payroll-coding review. The result was that no reclassification was recorded, so the budget variance remains in the report. Completion does not mean the number was corrected or the difference disappeared.
Another action asks for the software seat register, with unused seats separated from required service accounts before changes are proposed. That is a more useful instruction than ?reduce software costs?: it describes the review needed before making a decision.
Figure to follow-up
- 01UnderstandDefine the figure, period and comparison.
- 02QuestionKeep the discussion attached to its report context.
- 03ActRecord the owner and next step.
Our recommendations and action tracker addresses a similar transition from recommendation to work. The report should lead to an owner, a next step and a record of what was learned.
Decide what the client should be able to inspect
Some supporting records may be appropriate to share; others may contain internal notes or information outside the engagement. Plan those boundaries before treating a drill-down link as a simple convenience.
Within the permitted view, retain the context of a question. A comment about software expenditure should identify the period and relevant report section. If the report is revised, an earlier discussion should not silently appear to concern a different figure.
Our portal features guide covers that customer-facing scope. The dashboard article focuses on the route from summary to investigation.
Preserve what the follow-up actually concluded
When we build client reporting portals, a useful review task is to trace one figure through to its explanation and then find the agreed follow-up. If the team later wants to claim that reporting saves time, measure preparation, review and correction effort against a baseline. Our ROI worksheet explains how to distinguish released capacity from cash savings. The presence of a portal does not establish either result by itself.
Sources and calculation notes
The sample September report is in AUD, excluding GST. Budget operating profit 65,000 - gross-profit gap 12,000 - extra operating costs 3,000 = actual operating profit 50,000. Payroll accounts for 2,000 and software for 1,000 of the cost difference. Report period and action-status date are separate fields. These are authored reporting records.
- Our client reporting and action review project. The project page includes the design account, delivered scope and screenshots discussed in this article.
- Our recommendations and action tracker project. The project page includes the design account, delivered scope and screenshots discussed in this article.
External references checked on 31 October 2026.