Evergreen inspection guide

When to Escalate an Identification Review

Use this guide as a broad starting point for when to escalate an identification review, then follow current law, official training and your organization's approved procedures.
Read the guide

Define escalation triggers

List the conditions staff cannot resolve within their role, such as missing references, unreadable required data or conflicting approved-tool results.

Create a safe handoff

Specify who receives the review, how to contact them and what limited observations may be shared without exposing unnecessary personal data.

Avoid unsupported conclusions

An escalation is a request for qualified review, not a declaration about authenticity, intent or the person presenting the document.

Use specific, observable triggers

Examples can include a missing current reference, a required field that cannot be read, a result outside the staff member’s training or a conflict between approved review steps. Define triggers in neutral language and avoid categories based on appearance or origin. Staff should be able to identify the trigger without first deciding that the document or person is suspicious.

Set expectations during the pause

Explain that an authorized reviewer is being consulted, keep the document secure and state what staff may do while waiting. Define reasonable operational timeouts and who decides the next step if help is unavailable. Clear expectations protect the customer experience and prevent a temporary escalation from becoming indefinite retention of a person’s document or personal information.

Review escalation quality

Periodically examine whether referrals include useful observations, protect privacy and reach the correct role. Look for repeated gaps in references, tools or training. Track resolution categories at a process level without storing unnecessary personal data. The objective is to reduce avoidable uncertainty while preserving escalation as a legitimate safeguard when frontline authority or information is limited.

Make escalation dependable

Publish observable triggers, the receiving role, contact method, privacy limits and what staff should communicate while waiting. Test coverage during every operating period and define an outage alternative. Review referral quality and recurring causes so resources improve. Preserve escalation as a neutral request for qualified review rather than a hidden accusation or automatic rejection.

All guides