What the evidence can show
A message can show what a sender says they need, but it does not by itself establish who sent it or whether every requested detail is necessary. A familiar logo, display name, email signature, or reference number can be copied or spoofed. Treat these as clues, not independent confirmation. A request’s timing may also matter: compare it with a transaction or interaction you can verify through an account or record you already trust.
Different evidence answers different questions. A known contact route can help confirm the sender; a clearly stated purpose can explain why a document is being requested; and a field-by-field explanation can show whether the request is limited to that purpose. None of these alone proves that disclosure is appropriate. For example, Hypothetical example: a message asks for a passport image but gives no reason and directs the recipient to reply to an unfamiliar address. The document request remains unverified even if the message uses a recognisable logo.
| Evidence to examine | What it may indicate | What it cannot establish alone |
|---|---|---|
| Confirmation through a previously known channel | The request is associated with a contact route you recognise | That every requested field is necessary |
| Written explanation of purpose and fields | How the sender says each detail will be used | That the explanation is complete or independently verified |
| Instructions for submitting the file | Where the sender expects information to go | That a link or destination is genuine just because it appears in a message |
Look for gaps and inconsistencies rather than relying on a single reassuring detail. A mismatch between the sender’s address and a previously verified contact, an unexpected change in instructions, or pressure to act immediately are reasons to pause and confirm. They are not proof of fraud, but they make independent checking more important.
How to check the details
Start from a channel you already know to be genuine, such as contact information saved before this request or an account page reached independently. Do not use a phone number, reply address, or submission link supplied only in the message you are checking. Ask the sender to confirm the request, its purpose, the exact fields needed, the permitted file format, and the intended submission route. Keep the question limited; do not send a document just to ask whether it is needed.
- Compare the sender’s name and address with prior verified correspondence, while remembering that familiar-looking details can be imitated.
- Ask what specific decision or process requires the document and why each requested field is relevant to it.
- Check whether a less revealing alternative is accepted, such as providing a particular detail separately rather than sending a full image. Do not assume an alternative will be accepted.
- Confirm the submission route independently and check that the instructions have not changed unexpectedly. If uncertain, pause rather than opening an unverified attachment or link.
- Before sending, review the image for unrelated information, including other documents, background details, and data on the reverse side. Ask whether any masking or redaction is allowed before altering a document.
Hypothetical example: a verified contact confirms that a request concerns a name-and-date match, but the message asks for a full, unredacted document and extra account details. Ask whether those additional fields are actually required and what approved method should be used. Do not infer that a document is safe to send merely because the original request has been confirmed.
Never post identity documents in public threads, shared comments, or open support discussions. If a request arrives in a public space, ask for a private, independently verified submission route without placing the document or its identifying details in the thread. Avoid sending copies through ordinary channels until you have checked the destination and instructions; a private message is not automatically a secure one.
Recording a useful conclusion
Keep a brief record of the checks, not an unnecessary duplicate of the document. Note when the request arrived, the channel used to verify it, the purpose given, the fields requested, any alternative discussed, and the reason for your decision. Record unresolved questions plainly. For instance, “sender confirmed through saved contact; purpose explained; need for address field not clarified; no document sent” is more useful than a vague note that the request seemed legitimate.
Separate observations from conclusions. “The verified contact confirmed the request” is an observation; “all requested data is necessary” is a stronger conclusion that may not be supported. If the sender cannot be confirmed, the purpose is unclear, or the submission route remains uncertain, record that uncertainty and wait for clarification. If you decide to provide information, retain only records that are appropriate for your needs and avoid circulating copies more widely than necessary. This process helps make the decision understandable later without treating a message, logo, or assurance as conclusive evidence.