Count evidence that still exists after the shift ends
A photo of a handheld on a settings screen rarely helps. Useful evidence is tied to a named count batch, a named user, and a named freeze.
Files we inherit from internal audit are often a procedure and a screenshot of cycle count “on.” That shows intent. It does not show that bin A-14 was counted on the Tuesday the variance posted.
For a Johor count window, useful evidence usually looks like this: the batch the application generated, the user who confirmed the count, the scanner or sheet image, the approval of any variance above the threshold, and the freeze timestamp on receiving and shipping. If those artefacts rotate out of the WMS after thirty days, the letter should say so before we arrive, because we cannot test what the application has already discarded.
PDPA and vendor retention rules sometimes limit how long user IDs in logs are kept. That is a constraint, not a reason to skip the test. We document the gap and test what remains. If you are preparing for us, export the count batch while the window is still open.