Email administration

A quarterly review of mailbox forwarding rules

A review routine that finds forwarding rules left behind by departures, personal accounts, and old projects before they leak mail.

Short answer

Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.

Delegation playbook

Best fitRepeatable IT admin
OwnerManager or IT lead
Risk ruleEscalate technical judgment
PilotTwo-week sample workflow
On this pageJump to section

Mailbox forwarding is a small setting with a long life. A rule created for a holiday cover or a departing employee can keep sending mail for years after the reason has gone. A quarterly review finds those rules, confirms the destination, and removes the ones nobody can justify. The review is quick when the admin centre export is part of the routine.

Pull every forwarding rule from the admin centre

Export the mailbox forwarding settings for every active account, including shared mailboxes and resource accounts. Capture the rule owner, the destination address, the creation date if the platform records it, and whether the rule forwards all mail or only a category. Keep the export with the review date. A review that reads the screen one mailbox at a time will miss the accounts nobody opens.

Check both the mailbox-level setting and any inbox rule that forwards or redirects. Some platforms treat these as different controls, and a rule can survive after the main setting is cleared. Include accounts that are disabled but not yet deleted. The export should cover the mailboxes that still receive mail, not only the ones people log in to.

Separate business rules from personal ones

Mark each rule with the business reason and the ticket that approved it. A shared inbox that forwards to a team queue is different from a personal mailbox that forwards to an outside address. Group the rules by destination type so the risky ones are easy to see. The review should not treat every rule as equally suspicious.

Ask the mailbox owner to confirm the reason for any rule without a ticket. If the owner has left, ask the manager who took over the work. A rule that nobody can explain is a finding even when the destination looks familiar. Record the answer rather than deleting on suspicion alone.

Check rules created around a departure

Compare the rule creation dates with the offboarding records for the same period. A forwarding rule added in the last weeks before someone leaves deserves a direct question. Check whether the destination belongs to the person, a colleague, or an unknown domain. Departure timing is one of the few signals that separates cover from exfiltration.

Review the rules that remained after the account was disabled. Some platforms keep forwarding active even when sign-in is blocked. Confirm the manager approved any handover address and that it belongs to the company. Remove rules that point to a personal account once the handover period ends.

Confirm the destination mailbox is legitimate

Resolve each external destination domain and check it against the vendor and partner list. Look for domains that imitate a known brand with a small spelling change. Do not open a link in the rule itself. Use a separate lookup and record what you found.

For internal destinations, confirm the mailbox still exists and belongs to the expected team. A forward to a deleted mailbox can bounce silently or land in a queue nobody reads. Ask the destination owner to confirm they expect the mail. A legitimate address that no longer wants the messages is still a rule to remove.

Remove rules that bypass the ticket trail

Delete rules that forward mail outside the company without an approval or a current business need. Remove duplicates that send the same message to several personal addresses. Keep a copy of the rule details in the review record before deletion. The record shows what was removed and why.

Tell the mailbox owner what changed and how to request a new rule. If the rule supported a live process, offer a shared mailbox as the replacement. A personal forward should not be the only path for work that the team depends on. The fix is usually a queue, not a stricter warning.

Record approvals for rules that stay

For each surviving rule, store the approver, the business reason, and the next review date. Put the rule identifier in the ticket so the next reviewer can find it. Set an expiry where the platform supports one. A rule with an expiry reviews itself.

Review the approval list with the mailbox owner once a year, or sooner when the role changes. Ask whether the destination still needs every message or only a category. Narrowing a rule is often better than removing it. The record should show a deliberate choice, not an inherited setting.

Handle shared mailboxes and role accounts

Treat a shared mailbox rule differently from a personal one, because several people may depend on the forward. Record the team that owns the mailbox and the queue that receives the mail. Ask the team lead to confirm the destination and the expected end date. Removing a shared rule without that check can stop a live support queue.

For role accounts, such as billing or support, keep the rule list with the account owner and the last review. Convert personal forwards into a shared mailbox where the platform allows it. That change keeps the mail inside the company and gives the team a record. The review should leave a cleaner path than the one it found.

Review again on a fixed calendar

Put the review on the same quarterly calendar as the access review so the exports can be compared. Run it after the offboarding list is final for the quarter. Assign one owner and one backup, and give them the export template. A recurring review with no owner becomes a document nobody updates.

Track the number of rules reviewed, removed, and approved, plus the number with no recorded reason. Compare the counts with the previous quarter and investigate a sudden rise. Update the template when a platform changes its settings. The measure of the review is fewer unexplained rules each time.

Sources and next step

Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the credential, endpoint, email, software, and remote meeting practices discussed in these guides. The NIST SP 800-63B digital identity guidance supports the password vault and recovery steps, and NIST SP 800-53 Rev. 5 supports the access, audit, and configuration records. Apply your own policies, contracts, and system documentation to the workflow. Compare this guide with the laptop recovery key register and the mailbox forwarding review before changing a live process.

Keep decisions, approvals, and evidence in systems the business already controls. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.

Operating brief

What this guide should help you decide

Delegate

Routine intake, status updates, records, screenshots, and documentation upkeep.

Keep ownership

Approvals, risky system changes, security decisions, and final technical judgment.

How to use this guide

Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.

Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.

Workflow

Recommended operating workflow

1

Define the request

Write what a quarterly review of mailbox forwarding rules means in your company, where requests enter, and what finished work looks like.

2

Limit the access

Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.

3

Run a pilot

Use a two-week sample period so the manager can review accuracy before expanding the workflow.

4

Review patterns

Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.

Decision rules

QuestionVA fit signalEscalate when
Is the work repeatable?The same request appears weekly and can be described in steps.The request changes business policy or system design.
Can quality be reviewed?The manager can inspect the output without redoing the work.Only a senior technical person can judge correctness.
Is access contained?The assistant can work with read-only or role-limited access.Admin rights, customer data, or security settings are involved.

Delegation checklist

  • Write the intake source, expected output, and manager review cadence.
  • Confirm the assistant has only the permissions needed for the workflow.
  • List the events that require escalation before work continues.
  • Track examples for two weeks before changing the workflow.
  • Save examples of good and bad outputs so the assistant has concrete references.
  • Review the workflow monthly and remove permissions that are no longer needed.

Example first-week agenda

Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.

What to review before delegating

Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.

What should an IT virtual assistant handle first?

Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.

Get free IT support review