Create one reviewed observation tag
Capture an exact code, describe an informal observation and deliberately review one tag.
For operators
Read these instructions on any device. Watch or practise a chapter on a desktop or laptop, with a desktop or mobile application layout. Demonstrations use sample data and simulated scanners.
Create one reviewed observation tag
- Make an informal observation tag
Make an informal observation tag.
This lesson uses a synthetic item. A reviewed tag records an observation only; it never holds stock, isolates equipment or grants approval.
- Keep the exact item code
Keep the exact item code.
Enter 000017. Scanning only fills the code; it creates no tag until you deliberately review the note.
- A repeated scan creates no extra tag
A repeated scan creates no extra tag.
Enter the same code again. You remain in the capture step; a repeated reading never creates a new tag.
- Describe what needs attention
Describe what needs attention.
Continue to the observation. The identifier remains exact, including its leading zeroes.
- Choose an observation reason
Choose an observation reason.
Review storage asks someone to look at the item; it is not a stock or safety decision.
- Record what you saw
Record what you saw.
Keep the note factual and clear. It is a local claim, not an authenticated audit.
- Add a readable description
Add a readable description.
The description helps someone read the tag; it never changes the exact captured identifier.
- Declare the observed location
Declare the observed location.
This location is the writer’s claim, not live inventory or proof of where the item is now.
- Create one reviewed tag
Create one reviewed tag.
The genuine domain code freezes revision 1. Review its exact identifier and wording before downloading.