The Operations dashboard
The Operations dashboard is the screen from which you read how the organisation is working. It is reached from Dashboard in the CheckBiz side menu and requires no configuration: it feeds on the data the platform accumulates through daily use.
Its subtitle sums up the intention: *how each site works and who it depends on*. It is not an activity dashboard —how many people clocked in, how much it cost— but a reading of the environment and the capacity of the operation.
How to read it
The dashboard is read from top to bottom, not tab by tab. At the top are the three indices that sum up the situation; below, where to look; at the end, the detail.
The period
The whole dashboard is calculated over a monthly period, chosen at the top. When the month selected is the one under way, the dashboard warns that it is showing data up to yesterday: the day in progress is not closed and mixing it in would distort the comparison.
Each index also shows its variation against the previous period, which is usually more informative than the absolute value.
The three indices
| Index | What it measures |
|---|---|
| Reliability | The quality of the behaviour observed, separated from how long it has been measured |
| Site effect | Compares each person with themselves across different sites, to isolate the effect of the place from individual talent |
| Dependency | How much of the operation rests on a few people |
The site effect is CheckBiz360's most distinctive indicator and is worth dwelling on: it answers the question of whether the problem is the person or the place. It is translated into plain language in five readings:
- *Brings out the best in its people*
- *Somewhat above what would be expected*
- *Makes no difference*
- *They perform somewhat worse here*
- *Wears down those who pass through it*
Dependency reads just as directly: *half the operation depends on 1 person*, *depends on 2 people* or *healthy distribution*.
When there is not yet enough data
An index never invents a conclusion with insufficient data. Instead it shows its maturity state:
| State | Meaning |
|---|---|
| Gathering data | There is activity, but not yet enough to conclude |
| Partial evidence | It can be read with reservations |
| Not enough data | There is no basis for a judgement |
When volume is lacking, the dashboard indicates how many records are needed and how many there are. Absence of evidence is never presented as negative evidence: a new site does not appear as problematic simply for being new.
The three tabs
Below the indices, the detail is organised into three views that share the same data: switching tab does not request the information again.
Branches
How each site is evolving and what it costs to operate. The Sites needing attention table orders sites by need for attention —not by size or by cost— with their effect, their dependency and their reliability.
Each site flagged indicates why it is: the site is making its people worse, everything depends on one person, one person covers more than half, low punctuality, many badly closed workdays, among the worst sites.
Opening a site reveals two blocks:
- Who holds this site up: the site's people with their position, their weight in the operation, how much the site affects them and their responsibility.
- Who covers if someone is missing?: for each position, who carries it out, who is qualified and whether there is cover. The reading is direct —*nobody else covers it*, *1 more person can cover it*, *several people can cover it*— and answers a very specific question: if the person holding this position is absent tomorrow, is there anybody who can cover it?
Employees
Who is meeting expectations, who is leaving no record and who is being affected by their site.
Analysis
The patterns that belong neither to one site nor to one person in particular: where and when clocking fails, and the cross-reference between the two axes. It is read from least to most pointed: first what belongs to the process and the configuration, and only at the end the people.
Data status
The dashboard includes a data status block reporting the coverage available by area. It is the way to know whether an index is low because operations are going badly or because configuration is missing —rates left blank, schedules undefined— which prevents it being calculated properly.
The AI assistant's narrative
Each tab can be accompanied by the AI assistant's narrative, which narrates and prioritises what the screen shows: what to look at first and why.
The assistant works on the same figures already on view, not on data of its own, so its reading cannot contradict the dashboard. If there is nothing to narrate, no narrative is generated.
Role note
The Operations dashboard is available to Owner and Manager. The data each user sees is limited to the branches assigned to them.