I want to flag submissions where the document does not appear to be a passport so they can be handled separately.

This feature flags submissions where the uploaded document does not appear to be a passport so they can be routed for separate handling. It helps teams quickly identify out-of-scope documents and apply the appropriate process without slowing down standard passport review.

This feature identifies and flags submissions in which the provided document does not appear to be a passport, enabling them to be handled separately from standard passport workflows. When a submission is received, it can be marked as “not a passport” (or equivalent) so downstream reviewers and systems can recognize it as requiring a different process. The primary purpose is to prevent non-passport documents from entering the normal passport review queue and consuming unnecessary reviewer time. By separating these submissions, teams can apply alternative policies such as requesting the correct document, rerouting to a different verification flow, or conducting additional checks. This improves operational efficiency by reducing noise in the passport pipeline and making queues more predictable. It also improves user outcomes by ensuring submissions are handled according to the correct document type requirements. The feature is especially useful in high-volume intake scenarios where manual sorting is costly and error-prone. It can support compliance and audit needs by clearly distinguishing submissions that do not meet passport requirements. Overall, it provides a simple mechanism to isolate and manage non-passport submissions without changing the core passport review process.