Decide what a rule should do
The best candidates for rules are emails that arrive often, look the same every time and need no immediate reply: system alerts from your accounting software, delivery notifications, copies of invoices you send, marketing newsletters you read later. A rule that moves these into folders cuts the Inbox down to emails from people. Rules are much less useful for client correspondence, because sorting it into folders tends to hide things that need action. Write down the goal before building anything. A rule for move anything from the bank into a Bank folder is clear. A rule for sort everything from clients is not, and usually becomes twenty overlapping rules nobody understands six months later.
Server rules versus client-only rules
Outlook rules either run on the Microsoft 365 server, so they work even when your computer is off and apply on your phone too, or they run only inside the desktop app. Rules that play a sound, show a desktop alert, print or move items into a local data file are client-only. They work only while Outlook is open on that one computer, which explains why mail gets sorted at the office but not over the weekend. Where possible, build rules in Outlook on the web. Anything you can create there runs on the server. If a rule in desktop Outlook is marked client-only, consider whether you can simplify it to a server-friendly version.
Why rules stop working
The common causes are conflicting rules, a rule that stops processing further rules after it runs, a rules quota that has filled up, or a rule pointing to a folder that has been renamed or deleted. Rules run top to bottom in order, so a broad rule near the top can swallow emails before a more specific rule gets a chance. Reordering often fixes things. Mailboxes have a limit on how much space rules can take up. People who have built dozens of rules over the years, especially ones listing many individual addresses, can hit it. Combining rules, using domain names instead of individual addresses, and deleting old rules frees the space.
Rules as a security warning sign
When an attacker gets into a mailbox, one of the first things they often do is create a rule. A typical one deletes or hides any email containing words like invoice, payment or bank, or forwards copies to an outside address. The real owner stops seeing replies from suppliers while the attacker carries on a conversation about changing bank account details. This is a common pattern in invoice fraud cases reported to CERT NZ.
If you see a rule you did not create, especially one with an odd name like a single full stop, or one that moves mail to RSS Feeds or Archive, treat it as a possible compromise. Change the password, make sure multi-factor sign-in is on and ask whoever manages your Microsoft 365 to check the sign-in logs.
Alternatives to more rules
Focused Inbox, conditional formatting and Quick Steps can do some of the work without moving mail. Focused Inbox separates newsletters and automated messages from personal email. Conditional formatting colours emails from key clients so they stand out. Quick Steps let you file an email and mark it done with one click when it does need a person. For shared inboxes such as accounts or support, a ticketing tool or a shared mailbox with clear categories may work better than rules on one person's mailbox. Rules suit predictable sorting; they are a poor substitute for a team process.
A starter set for a small office
For most office staff, five or six rules are plenty. One moves automated notifications from your line-of-business software into a Notifications folder. One files newsletters you subscribed to into a Reading folder. One moves copies of your own sent invoices, if your accounting system copies you on them, into an Invoices Sent folder. One flags any email from your two or three most important clients so it cannot be missed. That covers most of the noise.
Avoid rules that forward email outside the organisation, even for good reasons like sending copies to a personal address while on holiday. Many Microsoft 365 setups block external forwarding by default, and for good reason. Review your rules once a year, delete anything that no longer matches a real need, and keep rule names descriptive so you and anyone helping you can tell what each one does. Test each new rule by sending yourself a matching email from another account before relying on it. A rule that quietly moves an important client's emails into the wrong folder can go unnoticed for weeks, so check the destination folders now and then during the first month.
In short
- Rules are best for predictable automated mail, not client correspondence.
- Build rules in Outlook on the web so they run on the server.
- Rule order and conflicting rules explain most failures.
- An unfamiliar rule can mean the mailbox has been compromised.
