Records and analytics
A description of your own practice — not a score
Which version of a procedure was performed, by whom, in what order, and how long each step took. Enough to find where a procedure loses time, and enough to answer somebody who asks what was done.
The rule these numbers are built on
Every timing figure is calculated from your own organisation's recent runs of the same step, and it means “usually about this long here”. It is not a norm, a standard, a target, a limit or a violation, in any language the product speaks — and it is never compared against an outside benchmark.
The reason is not modesty. A step can be dangerously slow — clinically, or for a pressure test, or for a lifting plan — and perfectly typical for the organisation doing it. This data cannot tell those apart, so calling a statistical baseline a standard would be a claim about safety that the numbers do not support.
Six things the records give you
Time per step
How long each step took, on each run. Median and 90th percentile per step, calculated from your own organisation’s recent history
Where a procedure loses time
The steps that consistently take longest here, so you can look at the step rather than at the person
A filterable history
Past runs, narrowed by procedure, period, performer or outcome
Weekly and monthly summaries
Generated automatically and stored in the console, in each organisation’s own timezone. Nothing is e-mailed to anybody
CSV export
Of whatever the current filters select. There is no report builder, no saved report definition and no PDF
Scanned or typed, recorded as such
The record says which, and passes no judgement: typing a code in has legitimate causes, and only somebody who knows the work can weigh them
Four honest uses
Finding the step that costs the time
A procedure that takes twice as long as expected usually does so at one or two steps. The per-step figures point at them, which is a question about the procedure rather than about whoever ran it.
Seeing a run that has stalled
The live board shows who is on which step and how long they have been there. It polls every few seconds and the client reports in about once a minute, so a step change can be up to a minute old — a good supervisor’s view, and a poor claim to real-time tracking.
Answering an incident review
Which version of a procedure was performed, when, in what order, which steps were skipped and which were returned to. It is evidence that a procedure was followed. It is not an audit and not proof of compliance on its own.
Watching a procedure settle after a change
When a procedure is rewritten, its own timings move. Comparing a version against the versions before it is a comparison inside your organisation and against nothing outside it.
A word about “real time”
The board of runs in progress refreshes every few seconds, and the app on a phone reports in about once a minute, so what you are looking at can be up to a minute old. And a device sending a heartbeat is not proof that somebody is standing at it. We say “refreshes every few seconds” rather than “real-time tracking of staff activities”, which is what this page used to say.
Questions about the numbers
Mostly about what they do not mean.
Do the timings say whether somebody is working fast enough?
No, and nothing in the product will claim they do. They answer "how long does this step usually take here", drawn from your own organisation’s recent runs. They are not a norm, a target, a limit or a violation, they are never compared with an outside standard, and a step can be entirely typical here and still be too slow for the work. Only somebody who knows the work can judge that.
Is there a leaderboard of employees?
No. There is a per-performer breakdown, which is a different thing from a ranking, and an earlier version of this page illustrated a "Top Employees" chart that does not exist in the product.
Are reports e-mailed to managers?
No. Weekly and monthly summaries are generated automatically and stored in the console for somebody to open. Earlier versions of this site said they were sent to an inbox; they are not.
Can I get the data out?
As CSV, exporting whatever the filters currently select. Ask us and we will also export your organisation’s procedures and records in a machine-readable form.
Run something and see what it records
The demonstration records nothing and sends nothing anywhere — but it shows you the shape of what a real run produces.