Use feature categories carefully
Physical documents may combine printed, tactile, optical and material features. Review only features covered by current, trusted reference material.
Observe relationships, not just presence
Consider placement, alignment and interaction with the rest of the document rather than treating one visible feature as decisive.
Respect inspection limits
A feature can be misunderstood, worn or unfamiliar. Escalate when the available tools, lighting or training do not support a responsible review.
Organize reference material by observable category
A useful reference explains where a feature should appear, how it relates to nearby elements and what viewing conditions are appropriate. Keep optical, tactile, printed and material observations clearly separated so staff do not confuse one category with another. Use current jurisdiction-specific sources; broad examples can teach concepts but should not be treated as exact specifications for every document.
Avoid destructive or unsafe tests
Do not scratch, peel, bend, heat or chemically test a person’s document. Use only handling and tools permitted by policy and training. If the available environment cannot support a safe observation, record that limitation and escalate. Protecting the document and the person’s information is part of a responsible inspection, even when a feature remains uncertain.
Combine features with context
Review whether multiple observations are consistent with the document type, issue period, layout and condition. A feature can be present yet misunderstood, or appear different because of wear and production variation. The purpose of combining signals is to support a careful policy decision, not to convert a visual checklist into a promise that authenticity has been established.
Use feature knowledge responsibly
Treat feature education as support for a complete, jurisdiction-specific review. Keep sources current, provide safe viewing conditions and state which observations staff are trained to make. Prohibit destructive testing and unsupported claims. When a feature cannot be understood in context, the correct next step is the documented escalation path, not greater force or certainty.