Running a phishing test on employees involves getting proper authorization, setting clear objectives, selecting a relevant scenario, configuring the simulation safely, testing it internally, launching the campaign, providing immediate feedback, and analyzing the results to improve security awareness. This 10-step playbook explains how to conduct an employee phishing test without punishing anyone.
In This Guide
Should You Run a Phishing Test?
What Is an Employee Phishing Test?
Why Run One?
The 10 Steps
Metrics to Measure
7 Common Mistakes
What to Do After the Test
How PhishTop Supports Testing
FAQ and Keep Reading

The three rules:
Always get authorization before running a test.
Never collect real passwords.
Use the results to educate employees, not blame them.
Should You Run a Phishing Test? Fears and Fixes
Conducting a phishing test can be challenging. If the simulation is too easy, it provides little value. If it is too realistic, it may create panic or damage employee trust. Poorly managed results can also turn into a way of punishing employees for clicking rather than helping them learn.
A successful phishing test requires a clear strategy, not just a simulation tool. When conducted properly, it provides valuable insights into an organization's human risk.
What Is an Employee Phishing Test?
An employee phishing test is a controlled security exercise in which simulated phishing emails are sent to employees to observe how they respond.
These emails imitate common phishing scenarios, including password reset requests, fake invoices, document-sharing invitations, delivery updates, HR notifications, IT support messages, and account verification requests.
The test evaluates whether employees open, click, attempt to submit information, report, or ignore the simulated message.
Comparison | Employee phishing test | Real phishing attack |
|---|---|---|
Purpose | Evaluate awareness and improve security | Steal information or compromise systems |
Authorization | Approved by the organization | Conducted without authorization |
Links | Lead to controlled simulation pages | May redirect to malicious websites |
Data collection | Limited and predefined | May collect credentials or sensitive information |
Outcome | Learning and risk assessment | Financial or operational damage |
Why Run One?
Employee phishing tests help organizations:
Identify employee phishing risk: Employees may recognize obvious spelling mistakes but struggle with realistic payment requests or document-sharing notifications.
Evaluate training effectiveness: Completing a training module does not necessarily mean employees can recognize phishing attempts.
Improve reporting behavior: Determine whether employees follow the established process for reporting suspicious emails.
Identify department-specific challenges: Finance teams may face invoice fraud, HR teams may encounter malicious CVs and record requests, IT teams may receive impersonated support and account requests, and management may be targeted with confidential document requests.
Build a continuous security program: NIST SP 800-50 Rev. 1 supports an ongoing cycle of exercises, evaluation, and improvement.
The 10 Steps
Step 1: Define Objectives
Determine what you want to learn before creating the simulation email.
Possible objectives include:
Measuring employee susceptibility to phishing.
Evaluating suspicious-email reporting behavior.
Assessing the effectiveness of recent training.
Identifying departments that need additional support.
Testing a particular phishing scenario.
Establishing a baseline for future campaigns.
Your objectives should determine the scenario, target audience, and metrics used to evaluate the campaign.
Step 2: Get Authorization
Even simulated phishing emails imitate suspicious activity, meaning employees or security systems may mistake them for genuine attacks.
Before launching a campaign, establish the following:
Management approval
IT or security team sign-off
Clearly defined objectives and scope
Campaign dates and duration
Approved target groups
Data collection and retention rules
An escalation procedure in case something goes wrong
Defined campaign operators and result-access permissions
Important: Never conduct phishing tests against employees, customers, or third parties without proper authorization.
Step 3: Identify the Audience
Determine who should participate in the simulation. Depending on your objectives, you may target:
The entire workforce.
A specific department.
Employees in particular roles.
Newly hired employees.
Privileged users.
A targeted approach often produces more meaningful results. For example, a simulated invoice is more relevant to the Finance department than to an unrelated team.
However, avoid using personal or sensitive information to manipulate individual employees.
Step 4: Choose a Relevant Scenario
Select a scenario that reflects the types of phishing attempts employees might encounter in their actual work.
Scenario | What it evaluates |
|---|---|
Password reset | Recognition of suspicious account-verification requests |
Fake invoice | Awareness of payment-related phishing |
Document sharing | Ability to identify suspicious file-sharing invitations |
HR notification | Recognition of impersonated internal messages |
Delivery update | Awareness of unexpected delivery notifications |
IT support request | Recognition of suspicious technical-support messages |
Avoid sensitive scenarios involving personal emergencies, medical conditions, or threats to someone's livelihood.
The objective is to improve security awareness, not exploit personal vulnerabilities.
Step 5: Prepare the Simulation Email
Consider the following elements when preparing your simulated phishing email:
Sender name and email address.
Subject line.
Message context.
Language and formatting.
Call to action.
Link destination.
The email should be realistic enough to evaluate employee awareness while remaining within the approved campaign scope.
Match the difficulty level to your objectives and employees' experience. The NIST Phish Scale can help evaluate how difficult a simulated phishing message is to identify.
Step 6: Configure the Simulation Safely
An improperly configured simulation can disrupt business operations or introduce unnecessary security concerns.
Before launching, verify the following:
Only approved recipients are included.
All links lead to controlled landing pages.
No real credentials are collected or stored.
No malware or harmful attachments are used.
Tracking is limited to approved campaign metrics.
Email security teams are aware of the authorized campaign scope.
Data handling follows the organization's privacy policy.
If the simulation includes a credential-entry page, record only the interaction event. Never collect or store the password an employee enters.
Also, establish a procedure for stopping the campaign if an unexpected issue occurs.
Step 7: Pilot Before Launch
Send the simulation to designated internal testers before distributing it to the wider audience.
Review the following:
Email formatting.
Sender information.
Link destinations.
Landing-page behavior.
Tracking accuracy.
Recipient targeting.
Reporting functionality.
Compatibility with the organization's email environment.
A small pilot campaign helps identify configuration issues before they affect the wider workforce.
Step 8: Launch
Distribute the simulation according to the approved campaign schedule.
Monitor:
Email delivery issues.
Unexpected employee responses.
Suspicious-email reporting activity.
Technical problems.
Confusion between simulated messages and genuine internal communications.
Avoid creating unnecessary pressure during the campaign.
If an employee reports the simulated email, recognize it as positive security behavior.
Step 9: Give Immediate Educational Feedback
When an employee interacts with the simulated message, direct them to a constructive feedback page.
Explain:
Which elements of the email deserved closer attention.
How to verify sender information.
Why the request was suspicious.
How to independently verify unexpected requests.
How to report similar messages in the future.
Do not publicly expose individual results or use the campaign to embarrass employees.
A supportive approach encourages employees to report suspicious activity rather than hide mistakes.
Step 10: Analyze Results and Plan Improvements
Evaluate the campaign results against your original objectives.
Consider the following questions:
How many employees clicked the simulated link?
How many reported the email?
Were there differences between departments?
Did anyone attempt to submit information?
How quickly were suspicious messages reported?
Did employees who received training demonstrate improvement?
Which scenarios were the most difficult to identify?
Conclude with actionable recommendations rather than presenting click percentages alone.
Metrics to Measure
Use relevant metrics to understand employee behavior and evaluate the effectiveness of your phishing simulation campaigns.
Metric | What it measures |
|---|---|
Click rate | Delivered simulation emails associated with link clicks, based on your defined calculation method |
Phish-prone percentage (PPP) | Unique employees who performed a defined risky action |
Reporting rate | Percentage of recipients who reported the email |
Credential-submission attempt rate | Percentage of recipients who attempted to submit information |
Time to report | How long employees take to report the simulated email |
Repeat interaction rate | Employees who repeatedly perform risky actions across campaigns |
Training completion rate | Percentage of assigned training that has been completed |
Example: A 250-Employee Campaign
Consider a phishing simulation conducted with 250 employees.
Result | Number |
|---|---|
Received | 250 |
Clicked | 45 |
Reported | 125 |
Attempted to submit information | 12 |
Did not interact | 80 |
Click-based PPP calculation:
(45 ÷ 250) × 100 = 18%
Use this result as the baseline for your next campaign.
Reporting rate calculation:
(125 ÷ 250) × 100 = 50%
Define the numerator, denominator, and measurement period for every metric, and count unique employees.
Note: These are separate activity counts, not mutually exclusive employee groups. An employee may click a link, attempt to submit information, and later report the same simulated email.
Learn more: Phish-Prone Percentage Explained.
7 Common Mistakes
Mistake | Better approach |
|---|---|
Testing without clear objectives | Define objectives before launching |
Using obviously fake emails | Vary the realism and difficulty of scenarios |
Making tests too difficult | Consider scenario difficulty when interpreting results |
Collecting real credentials | Record interaction events only |
Focusing only on click rates | Include reporting, submission attempts, repeat interactions, and reporting speed |
Punishing employees | Use results for coaching and training |
Ignoring the results | Review findings and implement improvements |
What to Do After the Test
A phishing test should not end when the campaign is complete. Use the findings to improve your organization's security awareness program.
1. Provide targeted training
Deliver training based on department-specific risks:
Finance: Invoice fraud.
HR: Suspicious attachments and impersonation.
IT: Credential theft and support impersonation.
Management: Executive impersonation and business email compromise (BEC).
2. Improve reporting procedures
Make sure employees understand:
Which channel to use for reporting.
What information to include.
Whether to delete or retain the suspicious message.
Whom to contact if they have already clicked a link.
3. Compare campaigns
Evaluate changes in:
Phish-Prone Percentage (PPP).
Reporting rate.
Information-submission attempts.
Repeat interactions.
Time to report.
Use consistent scenarios and metric definitions when comparing results.
4. Review technical controls
Evaluate email filtering, authentication, access management, endpoint protection, and incident response.
5. Repeat
Phishing techniques continue to evolve. Maintain a regular cycle of testing, training, and improvement.
How PhishTop Supports Employee Phishing Tests
Managing phishing campaigns manually involves creating emails, organizing recipient lists, monitoring clicks, tracking reports, and preparing performance reports.
PhishTop by Penough provides a structured approach to this process through controlled simulation campaigns, campaign analytics, employee reporting evaluation, awareness improvement, and campaign-to-campaign comparisons.
Its purpose is to identify weaknesses and improve employee behavior, not to catch people making mistakes.
Ready to run your first authorized test? Explore PhishTop.
Frequently Asked Questions
How do you run a phishing test on employees?
Start by defining objectives and obtaining authorization. Identify the target audience, select a realistic scenario, prepare and safely configure the simulation email, conduct an internal pilot, launch the campaign, provide immediate feedback, and analyze the results to identify improvements.
Is phishing simulation legal?
Phishing simulation can be a legitimate security awareness exercise when properly authorized and conducted in accordance with applicable laws, organizational policies, privacy requirements, and data protection obligations. Always define the scope and obtain approval before starting.
How often should we test?
There is no universal testing frequency. Consider your organization's risk level, workforce size, previous campaign results, and objectives. Regular exercises are generally more useful than conducting a single annual test.
Should employees know about simulations?
Organizations can choose different approaches to employee awareness. However, employees should understand that simulations may be part of the security awareness program. Leadership must authorize the exercises, and campaigns must comply with workplace policies and privacy requirements.
Can simulations collect passwords?
No. A properly designed phishing simulation should never collect or store employees' real passwords.
Can small businesses do this?
Yes. Small businesses can begin with clear objectives, a small authorized target group, safe simulation methods, and straightforward performance metrics.
Keep Reading
Guide | Why |
|---|---|
The pillar overview | |
Understand the concept | |
Interpret your results | |
Explore scenarios for targeted tests |
References: NIST SP 800-50 Rev. 1 · NIST Phish Scale