Dashboards and reporting
Objective. Explain how dashboards, analytics and reports present the platform's numbers, so you can use them to drive decisions while keeping the interpretation discipline - a dashboard shows a number inside a boundary and definition, never a context-free truth.
Dashboards and reporting are the most visible surface of the platform and the easiest place to misread a number. This teaches what the reporting layer is, what is safe to say, and the discipline that every figure carries a denominator, a definition and a scope that must be read with it.
See it in the demo
What dashboards and reporting are in Time Champ terms
Dashboards, analytics and reports are how the platform presents the numbers it computes so people can decide and review. They appear everywhere: Time and Activity, Work Output, Capacity Planning and the Workforce Management apps all expose dashboards, analytics and reports; RCM Insights lets a business user ask a question, discover an answer, build dashboards and inspect the data and evidence behind them.
The honest framing is that the reporting layer makes the platform's work visible and decision-ready - but a dashboard is a PRESENTATION of numbers, and every number carries the things that give it meaning: a denominator, a definition, a configured rule and a scope (PLAT-02, PLAT-05, PLAT-12, F06). A dashboard read without those is not a faster decision; it is a faster wrong decision. The reporting layer's best feature in this respect is evidence inspection - the ability to see the data behind a figure rather than trust the figure alone.
What a Sales or CSM person can say confidently
Safe to say: 'Dashboards, analytics and reports present your numbers for decisions and reviews, and - this matters - you can inspect the evidence behind a figure, so a dashboard is a starting point for investigation, not a black box.'
Safe for CSM operating routines (C06, C08): translate dashboards into daily, weekly and monthly decisions and a QBR, always pairing a figure with its denominator, definition and scope so the review is defensible.
Safe as the core interpretation rule (F06): read every number with its context - an attendance percentage and a utilisation percentage answer different questions; an output number is only comparable after aligning work type, complexity, period, tenure and quality.
Do not assert exact report customisation, export formats, scheduling/distribution, or embedding for a specific customer - those are product and configuration facts.
What always escalates to security or product
Route to a specialist:
- Exact report and dashboard customisation, and whether a specific view or metric can be built.
- Export formats, scheduled distribution, and embedding into a customer's own tools.
- Access and scope applied to reports and exports (overlaps PLAT-03, PLAT-06) - who can see and extract what.
- Data freshness and the sources behind a specific report (overlaps PLAT-10).
- Any report containing sensitive data that leaves the platform (a security question).
The posture: that the platform presents decision-ready dashboards, analytics and reports with evidence inspection is demo-supported; the customisation, export, distribution and access specifics escalate.
The honest limit
Demo-supported: dashboards, analytics and reports across the suite, and - clearest in RCM Insights - asking a question, discovering an answer, building dashboards and inspecting the data and evidence behind them.
Confirm with product: specific report/dashboard customisation, export formats, scheduled distribution, embedding, and the access/scope applied to reports and exports.
Separate cleanly: 'the platform presents decision-ready numbers you can inspect the evidence behind' (safe) from 'it exports in this format, on this schedule, embedded in your tool, customised exactly this way' (confirm with product). And never drop the interpretation rule: a figure is meaningful only with its denominator, definition and scope.
Interpretation check
A dashboard presents a number inside a denominator, a definition, a configured rule and a scope; read without them it produces a faster wrong decision, not a faster right one. Evidence inspection is the antidote - see the data behind the figure.
In the field
In a KnackGlobal business review, dashboards only persuade when each figure is read with its denominator, definition, tenure and client scope and backed by inspectable evidence - so the CSM presents output-per-FTE and cost-per-claim with their context rather than as standalone headline numbers.
Practical task
Pick one dashboard figure in the RCM Insights or Time and Activity demo and write it up correctly: the number, its denominator, its definition, its scope, and the evidence you would inspect behind it. Then list the reporting questions (customisation, export, distribution, access) you would route to a specialist.
Self-check
Why is a dashboard not a context-free truth?
Every figure carries a denominator, a definition, a configured rule and a scope; without reading those, an authoritative-looking number can be misread - a dashboard is a starting point for investigation, not a black box.
What is the reporting layer's best feature for building trust?
Evidence inspection - the ability to see the data behind a figure (clearest in RCM Insights) rather than trust the figure alone, which turns a dashboard into a defensible starting point.
A customer asks for a specific export format, schedule and embedding. What do you do?
Confirm the platform presents decision-ready, inspectable dashboards and reports, then route exact customisation, export formats, distribution and embedding to a specialist.
Which reporting facts are safe and which escalate?
Safe: that dashboards/analytics/reports present decision-ready numbers with evidence inspection, plus the read-with-context interpretation rule. Escalate: specific customisation, export formats, scheduled distribution, embedding, and the access/scope applied to reports and exports.
Verified vs demo. Dashboards, analytics and reports across the suite, with question-and-answer and evidence inspection clearest in RCM Insights, are shown in the demos; specific customisation, export formats, scheduled distribution, embedding and report access/scope are product facts to confirm.