Why registration is not approval

Most visitor systems quietly equate a submitted form with permission to enter. That is a security gap disguised as convenience. A registration is a claim; approval is a decision.

Separate the two states

In QID Secure a visit starts in pending. A security supervisor reviews the identity images, the extracted values, the confirmed values and the visit context, then approves, rejects or returns it. Only approval produces a pass.

Record the decision

Every transition stores the actor, device and timestamp. The status lifecycle is pending → approved → inside → exited, with rejected and cancelled branches. The audit trail is append-only, so the decision can be reviewed later.

Keep OCR in its place

Extraction is an assistant. Fields arrive with confidence scores and the visitor confirms them. OCR alone never approves a visit, and the supervisor always sees how the values were produced.