If you don’t see this in your navigation, your administrator can switch the module on under Administration → Modules, or it may not be included in your plan.


Verification and My audits
Verification has two menu entries, one for each side of a count:
A round can be changed — edited, published, closed or abandoned, its scope and auditors changed —
only by whoever created it, or by somebody with Edit, publish and close every verification round,
not only your own. A line is recorded only by the auditor it was given to, or by anybody where it
was given to nobody.
My audits
My audits counts the rounds assigned to you and how many are overdue. Each row shows:
Until a round is published and you are sent to it, the list says Nothing to count.
How a round works
The list is fixed when the round is published and does not change afterwards. That is what makes
“not found” mean something: an asset is missing from a list everybody agreed on, not from one that
moved under the auditors’ feet.
Kinds of round
The register
Verification lists the rounds you created, or every round where you hold Edit, publish and close every verification round, not only your own.The header
The two warning figures are the ones nothing else in the product mentions: both kinds of round look
perfectly ordinary on a list sorted by date. Search rounds searches; Still running hides
closed and cancelled rounds.
Columns
Creating a round
New round opens the round form. Creating a round does not start it: the next screen is where the scope is written, and publishing is what turns it into a list.

The round
When it runs
Nothing can be recorded against a round, and it cannot be closed, before its start date — so a round
can be published a week early, to tell the auditors, without anything being counted under it before
the walk. A self-verification emails its custodians on the start date. Recording after the end date
is allowed, and is what makes the round overdue.
Repeats
Sampling
Shown for a Sample round. Set one of the two.What counts as having looked
Answers and what each one needs is a grid: one row for each answer an auditor can give — It is here, It is somewhere else, I cannot find it, It is damaged and Could not get to it — and a column for each thing that answer can ask for.
Photo, Remark and Condition each step through three states when you click them:
A dash means the answer cannot ask for that: nobody photographs or judges an asset nobody saw, and
nothing locates one nobody reached. By default every answer is offered, a remark is required with
I cannot find it and Could not get to it and optional with the rest, and nothing else is
asked.
So a round that wants a photograph only of what is damaged sets Photo to Required on It is
damaged alone, and It is here goes through without one. Each demand is enforced the moment an
outcome is recorded, not warned about afterwards. The grid is fixed when the round is published, so
every line is settled under the same rules; editing a running round shows it locked.
Fields to check
Not asked on a self-verification round. Pick the details of each asset the auditor reads back from the thing itself — its serial number off the plate, its model, a photograph of how it looks now. Add a field to check offers any field a form may set on an asset and your organisation’s own fields, but not its site, location or coordinates, which the walk already records. The arrows beside a field ask it earlier or later, and the cross stops checking it. With none chosen, the form says None. The auditor records only whether each asset is there. The auditor sees what the register says and either confirms it or records what is actually there. What they record is kept on the round beside what the register said, and the asset is not changed until somebody presses Update on the report. The list is fixed when the round is published.Rules of the walk
Not asked on a self-verification round.What to tell them
Inside a round


The buttons below are offered to whoever created the round, or to somebody with Edit, publish and
close every verification round, not only your own, as well as the permission named.
Before the start date, a line under the header says when the round opens, in place of Walk it and
Close round. Where some lines were recorded as Could not get to it, a line says how many,
with Send them all back — see sending a line back.
Round details sets out when the round was created and by whom, its start and end dates, the
Auditor reminder (how many days before the start, or None), who closed or abandoned it and
when, and who it was assigned to (or, on a self-verification, sent to). The same block opens the
report.
What should be verified — the scope
The scope is a set of rules. Name assets adds individual assets — pick One asset, or Or paste asset numbers one to a line or separated by commas (numbers already on the list, at a site you cannot reach, or not recognised are reported). Add a rule opens New scope rule:
Each list field is a drop-down of tick boxes that stays open while you tick, and matches any of the
values ticked. Every field set on one rule has to match; rules are added together. A rule with nothing
set selects nothing, on purpose — the other reading would put every asset on the round.
Each rule is listed as a sentence, marked include. A rule written before the Include control
was removed keeps its setting, so an older exclusion still reads except and is taken away from
everything the other rules gathered. While the round is a draft, Edit changes a rule and Take it
off removes it; once the round is published its rules are fixed. While the round is a draft, the preview under the rules shows how many assets the
scope selects, broken down by site, refreshed after every change — “Pune 1,203, Chennai 637” is a
figure somebody can recognise as wrong at a glance.
On a self-verification round the scope keeps only the assets somebody is recorded as holding — a
custodian with an account, or a custodian’s email. An asset with nobody holding it, or with only a
custodian’s name, cannot be asked about, so it is left out, and the preview says how many matching
assets were left out and that setting a custodian or a custodian’s email brings them in. It also
warns about assets held by somebody whose account is no longer active and who has no email recorded:
they would be on the round with nobody able to answer for them. Naming an asset by hand that nobody
holds is refused in the same way, and a scope that matches only assets nobody holds cannot be
published.
Who is walking it
Auditors are chosen on the scope rule, under Auditor, where the places they would walk are already named. Only people who may record a count and who reach every place the rule names are offered — or, for a rule that names no place, people who share a place with you. Each place on the rule becomes one slice of the round for that auditor. Choosing the auditor needs Send auditors to walk a verification round. Who is walking it lists each auditor with their slice (or the whole round), progress and status. On a draft, progress shows the share publishing would hand them — 0/42, or 0/≤42 on a sample, because the draw has not happened yet. A line belongs to at most one auditor, so nothing is counted twice; lines nobody was given belong to whoever reaches them first, and a round published with no auditors is one anybody with the permission may walk.What was found on each asset
The round’s assets are listed once, on its Report tab — see the report, where an asset found somewhere else can be moved and a scan’s position pinned. Outcomes are:
A line settled when the round was closed says at closure. An auditor who names Where it
actually is keeps that place whatever answer they press: It is here with a place other than the
expected one is recorded as somewhere else, and a damaged asset found somewhere else stays damaged
but can still be moved.
To report every asset the round could not find as missing at once, use Report not found as
missing above the tabs. A single asset is reported missing, or marked found, from
its own screen.
Sending a line back
Could not get to it — a locked plant room, a site nobody could reach that day — no longer has to stand as the line’s last word. Send them all back on the banner above the round’s tabs puts every such line back on the list of whoever had it, to be walked again before the round closes. The first answer stays on the line until a second look replaces it, and it counts as still to walk. If nobody looks again, closing keeps could not get to it with a remark saying the second look never happened.Finds not in the register
On a round with Record assets not in the register on, Found, not in the register lists what auditors described that the register has no row for: the label on it (or no label), what it is, where it was, its photographs, and whether it is waiting, added or turned down. Somebody with Create assets decides each one:
Finds can be decided after the round has closed.
Change log
The Change log tab says what was changed about the round and by whom: its dates, its repeat, its rules and its auditors — an auditor put on, taken off, reminded or replaced — including rules and auditors since taken off. People with Read the audit trail also have an Audit trail tab with the field-by-field audit trail.Repeating rounds
A physical count is rarely a one-off: the annual verification comes back every year, the IT custody check every quarter. A round with Repeats set drafts the next one by itself, the number of days before it starts that Draft the next one (days before) says, copying the latest round’s settings, scope rules, auditors and named assets. Whoever runs the audit is notified. The next round is drafted, never published: publishing fixes the list and tells the auditors, and a scope that was right last quarter is exactly what a person should look over first. An auditor who has since been deactivated, or lost the right to record a count, is left off. On the round, a line says how it repeats and when the next round will be drafted, or links to the one already drafted from it. A drafted round says which round it was Drafted from. Stop repeating stops further rounds being drafted from this one; rounds already drafted or published are not touched. Deleting a drafted round also stops the series, and abandoning one skips that period.Walking a round
Walk it opens the auditor’s screen, designed for somebody standing up with a phone or a hand-held scanner.

- Scan, or type an asset number or tag into the box and press Find it, or press Camera to read a QR code or barcode. Where your phone or tablet lets the browser switch its light, the camera picture has a light button. A hand-held scanner types straight into the box, and the box takes focus again after every answer.
- The asset appears, with where the register says it is. If the code is not an asset, or the asset is not on this round, the screen says so — and records it as an unexpected find if the round accepts them. On a round that records assets not in the register, a code that matches nothing offers It is not in the register — describe it, and Found something with no label at all? offers Describe it. See describing a find.
- Add what the round asks for: Evidence photographs, the Condition (from your organisation’s list), Where it actually is, and Remarks. Where the round has fields to check, Read off the asset lists them with how many are answered — see reading the asset back. A field appears only where an answer the round offers asks for it; one that only some answers need says Needed with those answers.
- Choose what you found from the answers the round offers: It is here, It is somewhere else, I cannot find it, It is damaged or Could not get to it.
The demands that hold any of the buttons are also said once in words under them. A photograph is
attached through the line’s Evidence panel, so a round that requires one says so if the photograph
is missing when you record the outcome.
Reading the asset back
Each field the round checks says The register says: and its value. Answer it with:
You can read the fields before pressing an outcome, which is the order most people work in. Nothing
you record changes the asset; it is kept on the round for somebody to accept from the report.
The time recorded against each line is when the asset was scanned, not when the answer reached the
server — so a count made on a phone with no signal keeps the time it was made.
Describing a find
Describe it opens a short form for something the register has never heard of: What it is, the Label on it (empty if it carries none) and its Kind of label, its Category, Where it is, its Condition, Remarks and photographs, as the round asks of It is here. It is Recorded as a find for somebody to add to the register — nothing joins the register from the walk. See finds not in the register.Self-verification
A self-verification round sends nobody. When it is published, each custodian is emailed a link covering the assets recorded against them. Custodians do not need an account — a contractor, a new joiner or somebody at a hire company can answer, as long as the asset records their name and email.

What the custodian sees
The link opens Confirm what you are holding, which greets them by name and lists each item recorded against them, with Our records say where it should be. For each item they choose:
Only the answers the round offers are shown, and each card shows the item’s full location path. Where
any offered answer asks for a photograph, Take a photograph appears; where only some answers need
one, the card says A photograph is needed with those answers, and an item cannot be confirmed with
one of them without it. The chosen picture appears on the card straight away, faded under
Uploading… while it is sent, and Photograph saved confirms it once it has arrived — so a
custodian on a weak signal can see whether it went. A failed upload takes the picture away again. Anything else we should know at the foot takes a free-text note — “I
also have a docking station that is not on this list”. Every answer saves as it is given, so a
custodian with forty laptops can do them in three sittings. Send my answers sends them and closes
the link: Thank you — that is all we needed.
A link that has expired, been replaced or already been used shows This link no longer works,
and suggests asking whoever sent it for another.


Closing a round
Close round asks what should happen to lines nobody settled.

Close it closes the round and fixes the report. Only the round’s own list is settled this way:
an unexpected find is kept as seen by whoever scanned it, never turned into a “not found”. Where the
round recounts missing assets and some lines were never looked for a second time, the dialog says how
many: closing keeps them as not found and says on each that the second look never happened. Lines
sent back because nobody could get to them, and never walked again, are counted separately and keep
could not get to it.
The report
Report is the round’s result, ready to print.

Exceptions and Every asset on the list carry the corrections that can be made straight from a
line. They are left off the printed page.
Print opens the report on a page of its own, without the round around it, ready to print.
Details that differ from the register
What the auditor read off each asset, beside what the register said when they looked: Asset, Field, Register said, Found and Recorded by. The register is not changed until somebody with Edit assets presses Update on a row, or Update all N. The asset then says what was found — or, where changing it needs approval, the change is sent for approval. The update is recorded against the round, and a new photograph is added after the asset’s existing ones. A row says Updated by whom once it has been applied, and The asset has been changed since. Check it by hand. where somebody has corrected the asset since the auditor looked, so an older reading never overwrites a newer one.Verification scans across rounds
A round’s report answers for one round. To see every label anybody scanned on any round — which assets were physically seen this month, by whom, how, and where they were standing — open Audit in the menu and its Verification scans tab. The tab is offered to people who can read the audit trail, and only while the verification module is switched on. It only reads what the rounds recorded, on the web and in the field app; nothing on it changes anything. A round you cannot see contributes nothing to it. The header counts the scans shown, the assets and people among them, and how many did not match the asset they were scanned against.
The list shows 200 scans at a time; Show 200 more reads further back.
Who can do what
See roles for the defaults.

