Give remote staff a clear route to pause a suspicious request and report it to an authorised owner using an independently verified channel. Specify what evidence to preserve and which actions they must not take while the request is unresolved. The person receiving the email should not have to invent an incident-response role to avoid acting on it.
A message can arrive during a busy handover and appear to come from a familiar manager or supplier. The practical pressure may be to respond quickly and keep the work moving. A defined reporting process gives the employee a way to explain why the affected action is waiting and who is deciding it.
An email can contain an instruction, a familiar signature and an urgent deadline without establishing that the sender is authorised. The team needs to follow the business's existing checks for the action requested, particularly when it concerns money, account details or sensitive information.
The Australian Signals Directorate's business-email-compromise guidance describes impersonation through similar or compromised accounts. It recommends clear verification and reporting processes and independent contact details when a message is suspicious. A familiar display name should therefore not replace the agreed verification route.
Keep the response proportionate to the role. An administrative employee can report a concern without deciding whether a security incident has occurred or attempting a technical investigation beyond their authority.
Imagine a remote administrator receives an email appearing to come from a team leader. It asks for a customer export to be uploaded to a new file-sharing destination before the end of the day. The request is outside the usual process and includes pressure to avoid delays. This is a fictional scenario rather than a reported incident.
The administrator holds the upload and uses the organisation's established reporting channel. The message itself does not become a trusted source for the destination, the supposed manager's telephone number or a new approval route.
The authorised owner reviews the request using an independent contact path and the business's information-sharing rules. Even if the sender is confirmed, that does not automatically approve the new destination or a broader export. Identity, purpose and permission for the proposed action remain separate checks.
Agree how staff can provide the original message or its reference through the approved process. Include the time received, the claimed sender, the requested action and whether anything has already been opened, sent or changed. Let the security or system owner specify the supported method for preserving the message.
Avoid spreading the content through unrelated inboxes or copying sensitive records into a broad chat. The report should give the authorised recipient enough information to investigate through the appropriate tools.
If the person has already interacted with the message, they should say exactly what occurred and use the urgent route defined by the business. Clear reporting of an action already taken is more useful than an uncertain statement that the message was handled. The responsible owner determines the next response under the actual incident process.
Name the reporting destination, its coverage and the fallback when the usual contact is unavailable. A colleague listed as backup needs the actual authority and availability to handle the decision. Do not leave the employee choosing between carrying out the suspicious request and waiting without a visible owner.
State which work remains held. In the fictional example, the customer export is not released while verification and destination approval are unresolved. Unrelated authorised administration can continue unless the responsible incident or system owner directs otherwise.
DCV's delegated-decision guide helps document that authority boundary. It does not replace the organisation's security procedures or grant permission to investigate accounts, delete evidence or contact external parties.
Use a fictional message to test the route with the team. Ask the employee to identify the held action, the report they would make and the independently established channel they would use. Then ask the receiving owner to explain what evidence is missing and how the employee will receive an update.
Include a request that comes from a genuine account but asks for an unusual action. That exercise keeps the focus on the business process as well as the sender's apparent identity. Record any unclear responsibility and resolve it through the existing authorised process.
For the narrower payroll example, DCV's bank-detail-change guide addresses verification before release. The broader reporting route should give every remote role a practical way to pause a questionable request and carry the evidence to someone who can decide what happens next.