GUIDE · ENDPOINTS AND EMAIL

Reporting phishing: how to set up a procedure employees actually use

By the end you will be able to build a procedure for reporting suspicious messages that employees actually use: a single channel, short steps, a clear owner and a simple way to check that it works. The result is a page that anyone in the organisation can follow without asking anyone for help.

Updated october 2026
7 min read
Altovar Technical Editorial Team

1. Why a written procedure is needed

An employee who receives a suspicious message has three options: ignore it, delete it or report it. If the route to reporting is unclear, many choose the first or the second, and the organisation never learns that an attack is under way. An ignored message may be part of a campaign hitting other colleagues at the same moment, and nobody knows.

That is why a written procedure is needed, short and well known. It does not need to be a manual: it must say what to do, whom to contact and what not to do, in words anyone understands at first reading. The procedure also serves the owner, because it turns a report made verbally into recorded data that can be analysed and improved. Without data, every discussion remains an opinion.

2. Prerequisites: channel, owner and rules

Before writing the steps, decide three things. The reporting channel: a dedicated address or form, but only one. The owner who receives and assesses reports, with a deputy for absences. And the basic rules: do not click, do not forward to colleagues, do not reply to the sender and do not enter credentials on pages linked from the message, even if the page looks legitimate.

If the channel does not yet exist, create it before communicating the procedure. A procedure that asks people to report to an unmonitored address produces frustration and abandonment. Also check that whoever receives the report can see the original message, with its technical headers, without having to ask the sender for it. The person receiving the report must have everything they need to assess it immediately.

3. The steps of the procedure

The steps must stay in this order and in this tone. The first is the most important: do nothing that increases the risk. The second prevents the message from circulating among colleagues. The last closes the loop, because an employee who never receives a response stops reporting, and the procedure loses its value precisely when it would be needed most.

  1. Do not open attachments, do not click links and do not enter credentials.
  2. Use the designated reporting button or form, without forwarding the message to colleagues.
  3. If the message concerns a payment or a change of bank details, also alert the person who handles those payments, using a separate channel.
  4. If you have already clicked or entered data, report it immediately, without fear, and follow the owner's instructions.
  5. Wait for confirmation of receipt and do not take independent action on the message.
  6. The owner assesses the message, blocks it for other recipients if it is malicious and communicates the outcome.

4. Common mistakes

The first mistake is requesting reports as a gesture of goodwill, without explaining what happens afterwards. The second is punishing the colleague who clicked, which leads people to hide their mistakes. The third is having a long procedure or one spread across several documents. Someone with a doubt at the wrong moment does not look for the right document: they follow their instinct, and the instinct is often to click.

Another mistake is leaving reporting to the initiative of whoever already handles it. When the owner is absent and no deputy is named, reports pile up without a response. Write down who does what, including when the person is on leave or away, and check that the email out-of-office reply points to the correct channel. An out-of-office message that does not indicate the channel is a common error.

5. How to check the procedure works

A procedure must be tested. You can periodically send harmless simulated messages to check how many employees report them, how long they take and whether they follow the steps. The results should be read as opportunities to improve, not as rankings of blame: the aim is to understand where the procedure breaks down and to fix the weak point, not the individual colleague. A well-designed test should not embarrass anyone.

Also check the operational data: how many reports arrive, how many are genuinely malicious and how much time passes between receipt and response. If nobody ever reports anything, that is not a good sign: it often means the route is not known or that someone is afraid of getting it wrong. In that case, the message to convey is that reporting is part of the job, not a fault.

6. What to do after a report

The owner must follow a short protocol: verify the message, block it for other recipients if it is malicious, find out who has already opened or clicked it and update the procedure if a weak point emerges. If a report reveals a possible incident, assess with your supplier or a consultant whether notification obligations apply, such as those set out under the GDPR or the NIS2 Directive, where applicable to your case.

Always reply to the employee who reported, even just to confirm receipt and the outcome. Feedback reinforces correct behaviour and helps establish whether the message was a simulation or a real attack, which makes the next report even more useful. An employee who knows how things turned out is more careful next time, and learns the method.

7. How to start

This week, write the procedure on a single page, with channel, owner, deputy and steps. Share it with whoever manages email and ask them to check it by reading it as if they knew nothing about the subject. If you find a step that is unclear, rewrite it before circulating it, because an ambiguous sentence in a moment of pressure becomes an error. Once the procedure is clear, even a new colleague's first day is enough to follow it.

Then communicate the procedure with a short message, explaining why and which channel to use, and run a trial with a small group. Only after that extend it to everyone. For the wider context, the guide on endpoint security describes how this procedure fits into the overall controls. Read it after this one, to place the channel within the general framework of controls.

Frequently Asked Questions

What should someone do if they have already clicked a link?

They must report it immediately, without waiting until they are certain. Time matters: the longer a malicious page stays open, the more likely it has already collected data or installed something. The owner assesses what to do, for example changing the password, isolating the device or checking the account's activity. Prompt reporting protects both the organisation and the person who made the mistake.

Should I punish someone who clicks the wrong message?

No. A punitive culture leads people to hide their mistakes, which is the worst outcome for security. The message must be clear: mistakes happen, reporting early is the right thing to do, and the procedure exists to limit the consequences. Any training measures should be tailored to the individual case and not turned into an automatic sanction.

Who should receive reports?

One responsible person, with a deputy, who has the time and authority to block a message. It may be an internal contact or an external supplier, if the contract includes the service. What matters is that reports are not lost: a shared address that several people share but nobody monitors is worse than a well-run channel managed by a single person.

How do I handle a report that turns out to be unfounded?

Thank the employee and close the report with a note. An unfounded report is a good sign: it means the procedure is known and used. However, if unfounded reports become frequent, consider whether the legitimate message has features that cause confusion, and improve internal communication, for example about the suppliers with whom invoices are exchanged.

Does the procedure also apply to messages received on a phone?

Yes, but it must be adapted. On a phone it is easier to click without realising it, and the report button may not be available in every email app. The procedure must provide an alternative, for example forwarding the message, without opening attachments, only to the reporting address, and clearly state how to do this on the devices in use.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →