Cybersecurity

Practical business guide

Make suspicious emails easy to report — before someone needs help

Build a simple reporting route, practise with a harmless example and check who responds when a colleague has already clicked.

AIT Technology · Published and checked

Two colleagues calmly reviewing a fictional suspicious email beside a secure reporting tray
AI-generated editorial illustration; fictional scene.

A colleague receives an unexpected delivery message. Something feels wrong, but the team is busy and nobody knows whether IT, a manager or the email provider should check it. A reporting process that exists only in a long policy is difficult to use at that moment.

The NCSC's guidance on defending an organisation against phishing recommends layered defences, a clear reporting process and a supportive culture. It warns against relying on employees to identify every malicious message. This article is a practical application of established guidance, not a new threat alert. The source page lists publication on 5 February 2018 and review on 13 February 2024; we checked it on 20 November 2026.

Write one instruction that someone can actually follow

AIT's suggested first step is to agree a short internal instruction with whoever supports your email. Identify the approved reporting button or route, the person responsible for triage and a fallback if email itself is unavailable. Confirm that the route works for office staff, remote workers and anyone using a phone.

A draft instruction might read: “If a message looks suspicious, do not interact with its links or attachments. Use our approved reporting route. If you have already clicked, entered information or approved a request, tell our support contact immediately and explain what happened.” Replace the generic route with your real, tested process before sharing this with staff.

Keep the first report short

For an internal process, the useful starting details are the recipient account, approximate time, where the message appeared and whether anything was opened, entered, downloaded or approved. Staff should not investigate a suspicious link to complete the report. Do not ask them to put passwords, recovery codes or payment-card details into a ticket.

Agree how the support team will preserve the original message and any relevant evidence using the email platform's supported tools. Avoid forwarding potentially harmful content around the company as an informal warning. A short notice prepared by the response owner can explain what staff should do without circulating a live malicious attachment.

Practise with a clearly labelled fictional message

You can check the reporting route without running a deceptive phishing campaign. Arrange a short exercise with the support owner and use a harmless message labelled “REPORTING EXERCISE — no action required”. Include no external links, executable files or requests for credentials.

  1. Ask a participant to locate the approved reporting route using their normal device.
  2. Submit the fictional example and confirm that it reaches the intended support queue.
  3. Check that someone can acknowledge it and tell the participant what happens next.
  4. Repeat the route check for an alternative device or an absent primary responder.
  5. Record any confusing instructions and correct them before wider rollout.

This checks the process, not whether employees can detect real attacks. Record the observed acknowledgement time; do not turn one exercise into an untested promise of round-the-clock response.

Separate reporting a message from responding to an incident

A suspicious message with no interaction and a possible account compromise need different handling. If someone has entered credentials, approved an unexpected sign-in or run a file, use your incident response process and contact qualified support promptly. Do not wait for a routine ticket response or assume that deleting the message resolves the issue.

The NCSC provides a separate public route for reporting suspected scam emails. That page explains forwarding suspicious emails to report@phishing.gov.uk. Check your organisation's handling rules before forwarding business material. Public reporting does not replace your internal escalation or incident response.

Make the next review practical

At the next team review, ask whether people can find the route, whether reports are acknowledged and whether repeated issues point to a process that needs redesign. A larger report count by itself does not show that attacks have increased or that staff performance has declined.

AIT Technology can help adapt a reporting procedure to your departments, email platform and support arrangements, and connect it with a wider cybersecurity operations manual. Any implementation scope and paid work are agreed first.

Sources checked 20 November 2026: NCSC organisational phishing guidance and NCSC scam-email reporting instructions. The sample wording and exercise above are AIT's suggestions, not an NCSC certification or guarantee.