There is always a way to get around the system.
Reminds me of a system I designed for our electronics manufacturing factory many years ago. It would track product as it wound it's way through the build process, based on serial number, which we captured with scanners placed along conveyor belts. This would verify things like, "if a product fails a test, it must subsequently go to a repair station, and then retest successful". It would also capture things like what time a specific serial number went through a solder bath, and correlated that with the bath temperature, so we could yank suspect product from the line if something went wrong. And we could tie component batches to insertion machines to serial numbered product if we had gotten a bad batch of components. We could stop the conveyor belts too, if the system determined a need.
This all worked like a champ, until we had a fire in a solder bath because my software had stopped the conveyor while a product was being dunked. That shouldn't have happened, because from our scanners the software knew if there was product in the solder bath or not.
Well, ... someone had set work gloves over a couple of scanners because they were tired of us catching all their quality mistakes and they wanted to stealthily pass stuff through the system to meet their shipping goals - but obviously not their quality goals! They would have been caught at the end anyway - but they didn't realize that - since the software would have questioned the wisdom of shipping product that had not been soldered together yet.
There's always a way! I about near tied the rogue worker to the conveyor belt and sent HIM through the solder bath when I found out. The idiot was smart enough to use the gloves to bypass our system, but not smart enough to REMOVE the gloves before we came out to investigate!