Choose the report in the Report type box on the left, or click on the report type in the heading of the report (left click for the next type, right click for the one before it).
Which report do you want?
Printed, in a PDF and in Excel the reports leave out the tips and the links that only do something on the screen.
Every point that was clocked between the two dates, one line each, with the time. Use Sort by to put the list in order of time, point name or point number. Click on a point name to rename it.
Next to each clocking is the time since the one before. The same point clocked again within two minutes, with no other point between, is marked duplicate; click "Leave out the duplicates" above the list to hide them ("Show them" brings them back). Under the list is a Summary: how many clockings, the duplicates, the first and last clocking, and the longest (with the two clockings it was between), shortest and average time between two. Then how often each point was clocked, in Advanced mode how many points each member of staff clocked, and the numbers of the patrols (see Site statistics below).
Use the Point box on the left to see one point only (also in the Overview), or choose Choose several points ... and tick the points to see.
In Advanced mode the lines can be coloured by the time since the one before: click "Colour the lines by the time since the one before" above the list. Under 2 minutes is green, 2 to 5 minutes no colour, 5 to 10 yellow, 10 to 20 black and over 20 red. Click "Change the times" to choose other times (four, from short to long), "No colours" to switch it off. The colours are kept in the PDF and in Excel.
The patrol point – whichever point was clocked first, ever, at the site, unless you chose another – is shown in bold with "(start/end of patrol)". To choose it, click "Choose another point" next to Patrols in the summary, or "(change)" after "patrols start and end at" next to the site's name in the Groups/Points report. Most rounds start and finish back at the same point (a guard station, an entry gate), so every time it is clocked again marks where one patrol ends and the next begins. See Site statistics below for the numbers this gives you.
A picture of the whole period. There is a row for each point and a column for each block of time, one hour by default. A green block means the point was clocked in that time (the times are shown), a red block means it was not. This is the quickest way to see if a patrol missed a point. For a long period there are a lot of columns, so a day or a night works best.
Change the block size with the round time box on the left, for example 15 minutes for a tighter patrol. Too fine a block over a long date range would need more columns than fit on a page, so a wider block is used instead and a note says so.
The blocks before the first clocking and after the last one are all red and say nothing. Click Leave out the columns before the first and after the last clocking above the report to hide them, and Show them to get them back. A line above the report then says from when to when there was no data, also on paper.
Each time a baton was downloaded: when, the baton's number and version, the date and time on the baton, how many points were downloaded, and how many baton events (see below). Click on the time to see what was in that download.
The Problems column says Yes when something went wrong during that download; click on it to see what. Use Sort by to put the list in order of time or of baton number.
The batons that clocked at the site chosen in the site box, or every baton with All sites: how many times each was downloaded, the first and last download, with All sites which site(s) its points have ended up at, and whether its clock was out of sync (more than a day off on one download – a normal few minutes' drift between visits is expected and not flagged). "Yes, it had stopped" means the baton's clock was not running at all at one of its downloads.
Warnings from the baton shows, in red, the last time the baton itself reported a low battery, a lost clock, moisture or tampering, a high temperature or physical abuse: a baton with a recent low battery needs a new battery. Click in the Name or Your notes column to give a baton a name of your own (who carries it, for example) or to write something down about it (where it is kept, when its battery was changed).
What was in one download, in the order the baton recorded it. It shows the download you last chose (in the Downloads report, or with a link at the top of this one), or else the latest download; it has no dates. The downloads just before and after it are listed at the top so you can step through them.
This report shows everything the baton held. If the baton was used at more than one site, there is a table for each site; in Advanced mode also one for each team (staff), collection (assets), and the points that are not known yet.
If something went wrong during the download, a list Problems with this download is shown above the table, see When a download has a problem. This is also the only report that shows records marked time not valid.
▶ Open the Groups/Points report
The points of the site chosen in the site box (or of every site with All sites), with how many times each was clocked, when it was last clocked, and the last baton that clocked it. Click on a name to rename a point. See Sites. In Advanced mode the teams and collections follow: for one site only the staff and assets that were clocked on a baton that was at that site.
A point that is not known yet (a new tag) is at the top. Click place it ... and choose the site it is at (in Advanced mode also a team or collection), then click on its name to give it a proper name. move / ignore ... next to any other point moves it, or ignores a stray or test tag. Until a new point is placed, the reports about a site leave it out; Detailed lists it as Unknown point, with a place it link.
Next to a site's name it says where its patrols start and end; click "(change)" to choose another point (see Detailed). Under each site, the Baton events the batons reported there: each once, with when it was last reported and how often, so that old trouble (water, a low battery) can still be seen.
In Advanced mode the check column marks a point that might be faulty, from the last 30 days of the site's clockings: one that is often clocked twice (it reads badly, so the guard touches it again), or often missed on patrols that cover the rest of the site (it may be broken, hard to reach, or skipped). Have a look at the point itself.
▶ Open the Site statistics report
Numbers for one site in the chosen dates: how many points were clocked, on how many days, how many downloads, and the first and last time. Below that, for each point how many times it was clocked and the average time between clockings.
Below that, a Patrols table. A patrol is everything between two consecutive clockings of the patrol point – whichever point was clocked first, ever, at the site, unless you chose another (see Detailed, above). This gives the quickest, average and longest patrol length, how many patrols happened in the chosen dates, and for each one whether every currently active point was clocked ("Complete", or "Missing: ..." if not). Only whole patrols are counted – a part-patrol at either end of the date range is left out rather than guessed at. The patrol point clocked twice with no other point between (touched twice, or the next round started from it later) is not a patrol: the patrol starts from the second touch.
Newer batons (version A005 and later) can have records loaded into them by a program, for example a test log. The baton marks such records. They are shown in Detailed and By Download with (loaded by a program, not a touch) after the time: they are in the baton, but nobody touched that point at that time.
Points that were deleted are left out of the reports. A message above the report tells you how many there are and lets you show them.
A baton sometimes records something about itself rather than a point being touched – a low battery, moisture, a poor touch, or it starting up. These show in their own Baton events table under the points table (in Detailed, By Download, Groups/Points and Site statistics), with what happened and when, never mixed in with the points and never offered for renaming as if one were a checkpoint.