How is a device marked as verified in PeopleMuster?

Every asset register drifts. A machine gets swapped at a desk, a serial is typed with one digit wrong, a replacement arrives and inherits the old row.

None of that drift announces itself. A register that has never been checked looks exactly like one that was checked last week.

So verification is a field rather than an assumption. Marking a device verified is a claim someone made after looking at it. A row still awaiting a check says plainly that nobody has.

Keeping it apart from the health grade matters more than it sounds. Health describes the machine. Verification describes the record. A device can be in excellent condition and still have a row nobody has confirmed since it was created.

The filter is where the field pays off. Filter the register to rows awaiting a check and you get a work list. It shows the machines an audit would trip over, because nobody has looked yet.

A count sits above that list too. The register counts ready, under maintenance and retired machines. It also shows a utilisation rate and how many are free now.

Verification stays set until somebody changes it, so a rolling check is a schedule a company chooses. A recurring Slack reminder from the notification scheduler is an easy way to run it.

Filter to rows awaiting a check and work down the list before an audit rather than during one. The filters narrow by department and by holder as well, which turns one large job into a handful of short ones.