research

Measuring how often mailbox forwarding rules survive a departure

An audit that matches forwarding rules to departure records and measures how many remain active, where they send mail, and for how long.

Short answer

Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.

Research playbook

MeasureVolume and handling time
OwnerTechnical manager validates
Risk ruleName sensitive access
RefreshQuarterly benchmark review
On this pageJump to section

Key stats

Handover period30 daysStudy protocol
UnitDeparting mailboxStudy protocol
Destination split2 groupsStudy protocol

Key takeaways

When an employee leaves, the mailbox is usually disabled and the manager receives the work. The forwarding rule added during the handover is easy to forget, and it can keep sending mail to a personal or external address long after the handover ends. This study measures how many forwarding rules survive a departure and how long they remain active. It turns a quiet mail risk into a count the team can act on.

Question and scope

The study asks what share of departures in the period left at least one active mailbox forwarding rule after the account was disabled. The unit is one departing employee and one mailbox. The population is every departure recorded in the human resources or identity system during the study period. The result describes those departures, not every forwarding rule in the company.

Exclude departures where the mailbox was deleted on the same day and no forwarding was configured. Include contractors and temporary staff if they had a company mailbox. Record the exclusion rule and the count. A scope that includes every rule will mix old handovers with new departures and hide the trend.

Define a surviving rule

Treat a rule as surviving when it is still active after the account is disabled or after the documented handover period ends. Include mailbox-level forwarding and inbox rules that redirect or forward. A rule that copies mail to a shared team mailbox is still a rule, but record its destination type separately. The definition is about persistence, not intent.

Set the handover period from policy or from the manager's written plan, such as thirty days. If no period exists, use the date the account was disabled. Record the rule creation date and the last modification date. A rule created after the departure is a separate and more serious finding.

Build the departure frame

Export the departure list with the employee identifier, the last working day, the mailbox identifier, and the manager. Match the list to the identity system so the timing of the disable action is visible. Add the ticket that handled the handover. A departure frame built from the payroll list alone will miss contractors.

Note whether the mailbox was disabled, converted to a shared mailbox, or deleted. These outcomes change what a surviving rule means. Record the person who performed the handover and the date. The frame should let a reviewer find the mailbox and the owner without searching several systems.

Collect forwarding rules

Export the forwarding settings and inbox rules for each mailbox in the frame, including disabled mailboxes that still receive mail. Capture the destination, the scope, and the creation date where available. Keep the export with the review date. A rule that exists after the mailbox is disabled may still deliver mail if the platform keeps the forward active.

Check both the mailbox setting and the transport rule that may have been added by an administrator. Some platforms implement forwarding at the organisation level, outside the mailbox. Include any rule that names the departing mailbox as a source. The review should cover every path that can move the mail.

Match rules to departures

For each departure, compare the rule creation date with the last working day and the disable date. A rule created in the final two weeks deserves a direct question. Check whether the destination belongs to the manager, a team mailbox, or an external domain. The timing and the destination together separate a handover from a leak.

Record whether the manager approved the destination and whether the approval is in writing. If the rule points to a personal address, confirm the handover period and the expected end date. A personal destination without an end date is a finding even when the manager approved it informally. Record the approval note and the expected removal date in the study row.

Measure the share and age

Count the departures with at least one surviving rule and divide by the total departures in the frame. Report the count and the share, then split by destination type and by whether the rule was approved. A single percentage hides an external forward beside an internal team mailbox. The external group needs its own line.

Measure the age of each rule from the departure date to the review date. Report the median and the oldest case. Count the rules that survived beyond the documented handover period. The age shows whether the problem is a missed cleanup or a process that never sets an end date.

Compare with offboarding records

Check the offboarding checklist for a forwarding step, including who removes the rule and when. Compare the findings with that step rather than with a general expectation. If the checklist has no forwarding item, that gap explains most of the surviving rules. A checklist that ends at account disable is incomplete.

Look for departures where the manager asked for forwarding but no end date was recorded. Count the cases where the rule was removed on time. The successful cases show what the process looks like when it works. Use one of them as the template for the next handover.

Report and next use

Give the mailbox owner and the manager a list of surviving rules with the destination, the creation date, and the approval status. Ask for a decision to remove the rule or set an end date. Set a date to verify the change. Keep the report focused on the mailbox and the rule, not on the person who left.

For handovers that need forwarding, require an end date and a named person who will remove the rule. Prefer a shared mailbox over a personal destination. Add the removal to the offboarding checklist with an owner. Repeat the study after the checklist changes and compare the same departure groups.

Check the handover message

Read the message the manager sent to clients and suppliers at the departure. It often names the forwarding address or asks people to use a personal contact. Compare that message with the approved handover plan. A public instruction to use an external address can create a rule that no checklist anticipated.

Ask the manager whether the forwarding was meant to be temporary and who would end it. Record the answer and the date. If the message promised a permanent contact, the team needs a shared mailbox rather than a personal forward. The communication is part of the forwarding record.

Account for shared mailbox conversions

Some teams convert a departing person's mailbox into a shared mailbox instead of forwarding it. Treat that conversion as a separate outcome and check who has access. A shared mailbox can outlive the departure without a rule, but it still needs an owner and a review. The study should not count it as clean simply because no forward exists.

Compare the access list on the shared mailbox with the team that needs the work. Remove former colleagues who were added during the handover. Record the conversion date and the owner. A mailbox that becomes a permanent shared resource needs the same review as any other shared account.

Use the result in the offboarding script

Add a forwarding check to the offboarding script with a named person and a removal date. Ask the manager to confirm the destination and the end date in writing. Put the check after the account disable step so it cannot be skipped when the mailbox changes. The script should close the handover, not only start it.

Review the script after any departure that leaves a rule behind and update the step that failed. Test it with a mock handover before the next real departure. Share the updated script with the managers who request forwarding. The measure should fall because the script changed, not because someone remembers to search mailboxes.

Limits and next use

The study measures rules visible in the mailbox and transport configuration during the review. It cannot see a rule that was removed before the export, or mail that was manually forwarded without a rule. It also depends on the departure list being complete. State these limits so the result is read as a surviving-rule measure, not a full data loss investigation.

Repeat the study each quarter and compare the share and the median age. If the share falls but the age rises, the team is catching new cases while old rules remain. Keep the method with the offboarding checklist. The measure is working when the oldest external rule disappears from the list.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the DNS change, recovery key, software trial, privileged account, and forwarding rule measures discussed here. The NIST SP 800-53 Rev. 5 supports the access and audit record checks, and the GAO data reliability guidance supports the sampling and verification approach used in these methods. Apply your own policies, contracts, and system documentation when adapting the method.

Compare this study with the privileged account age audit and the mailbox forwarding survival study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.

Benchmark brief

What this research page must produce

Working number

A practical estimate for volume, review time, escalation rate, and assistant capacity.

Operating boundary

A clear split between routine support, preparation work, and technical ownership.

What the measuring how often mailbox forwarding rules survive a departure data shows

Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.

The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.

Workflow

Recommended operating workflow

1

Collect a baseline

Pull the last 30 to 90 days of examples related to measuring how often mailbox forwarding rules survive a departure, including completed work and unresolved exceptions.

2

Classify the work

Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.

3

Set the operating number

Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.

4

Refresh the benchmark

Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.

Decision rules

MetricUse it to decideManager action
Weekly volumeWhether the workflow is worth assigning as recurring assistant work.Approve a weekly capacity target and backlog threshold.
Access sensitivityWhether the assistant can work directly or only prepare review notes.Set least-privilege permissions and removal dates.
Escalation rateWhether the workflow is stable enough to delegate.Rewrite the SOP when exceptions exceed the agreed threshold.

Consolidated statistics

StatisticFigureSource
Handover period30 daysStudy protocol
UnitDeparting mailboxStudy protocol
Destination split2 groupsStudy protocol

Sources

  1. CISA Cross-Sector Cybersecurity Performance GoalsIdentity and email security goals that frame forwarding as an access path.
  2. NIST Cybersecurity Framework 2.0Identity management and data protection outcomes for departed staff.
  3. NIST SP 800-53 Rev. 5, Security and Privacy ControlsAccess enforcement and audit record requirements behind the rule review.
  4. NIST Privacy FrameworkData handling context for mail that may contain personal information.

Measurement checklist

FieldWhat to captureOwner
VolumeWeekly request count, backlog age, and repeat issue patternsAssistant prepares, manager reviews
RiskAccess level, customer impact, security sensitivity, and approval needsTechnical owner
CadenceDaily, weekly, monthly, or quarterly review rhythmManager
EvidenceSample tickets, logs, screenshots, and before-after examplesAssistant collects, owner validates
EscalationTriggers, approval path, response time, and stop-work rulesTechnical owner

How to read the result

A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.

Source and refresh note

This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.

How should teams use this benchmark?

Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.

Get free benchmark review