A spot check compares physical observations with a recorded snapshot. It does not silently correct custody or prove that every movement between checks was recorded. Have the actual position and tools available before entering observations.
Prepare and open the check
Use Spot checks with the permitted Operator or Supervisor role. Inspect the named check and its snapshot before beginning. A Supervisor creates the check for its supported scope; operators record the actual observations on an available check.
Identify each tool by its exact code or choose the actual asset in the check. Confirm that the displayed selection matches what you see. An unknown or different code is a discrepancy to investigate, not permission to record the previously selected tool again.
Record what was observed
Choose the available observation that truthfully describes the finding. If you could not confirm the tool, retain that uncertainty rather than marking it present. Give the required reason and confirm the physical observation before submitting.
Read the server's recorded outcome after each entry. Do not treat a scan used for selection as the observation itself. Repeat only when the application permits a further meaningful observation and the original action is settled.
A discrepancy can create an incident or review task while preserving custody. Seeing an asset at a position does not by itself establish that the recorded loan was returned by its borrower. Ask the Supervisor to reconcile that fact through the supported custody workflow.
Close the review honestly
Before finishing the check, inspect outstanding or uncertain observations. The Supervisor uses the offered close control when the recorded scope has been reviewed. Tell them about missing tools, unexpected assets, disputed identities and actual physical containment.
In Loans, holds and review, the Supervisor reviews resulting tasks and incidents with the physical evidence. Clearing a task is not the same as returning or restowing the tool. Use the exact return or reconciliation action where appropriate.
If the page reports stale state, refresh and compare the current check before another command. If an answer is uncertain, reconcile the original request. Do not create a second check merely to remove an inconvenient discrepancy.
Use holds and discrepancies for corrective action and history and documents to preserve the observed sequence.