Year-end offer: Get 2 months FREE with an annual contract.Claim my free months

Email governance: Why your policy doesn't count unless you can prove it works

Published

Key takeaway

  • Auditors start with your policy, then check whether employees follow it. Where a technical control exists, "we told people" is unlikely to satisfy a regulator.

  • Employees edit job titles, delete phone numbers and drop legal disclaimers, usually out of complacency.

  • Tamper Detection, an upcoming Exclaimer feature, warns or blocks senders who edit an email signature in Outlook before sending, and records every event.

  • This feature is in beta now and launches in early 2027 as part of Exclaimer's Pro plan.

A signed-off email policy doesn't count for much until you can show it's being followed. Where a technical control exists, regulators are unlikely to accept "we told people."

Exclaimer recently ran a webinar called "Email governance: Closing the gap between policy and practice." James Wayne, Senior Product Marketing Manager, and Ed Bodey, General Counsel, covered what auditors look for, where email policies break down, and a first look at Tamper Detection. The feature, which is in beta now and launches in early 2027, warns a sender when an Exclaimer-managed email signature is changed before an email goes out.

Here are the key takeaways.

Regulators check whether your policy works

Auditors start with the policy document. Then they check whether employees do what it says.

Ed used two security standards to explain how that works. ISO 27001 looks at whether you have a written policy and an information security management system. SOC 2 checks that the controls behind it are in place and working. That's how auditors tell a working control from "hot air," as Ed put it.

What your policy has to contain depends on where you operate and what industry you're in. Ed said business emails in the EU and UK generally need to carry corporate details such as company name, number and registered address. Some sectors add more. UK law firms may need an SRA number, and financial firms may need their FCA registration. If your policy says every email includes that information and some go out without it, an auditor will likely spot it.

Ed was direct about confidentiality wording too. It isn't necessarily fully binding, partly because it arrives after the email does, so he treats it more as a signal. Consistency still matters, because the one email where it counted shouldn't be the one missing it.

Unregulated companies carry risk as well, James said. A customer can request earlier emails and take issue with how they were presented.

What goes wrong when email signatures are left to employees

Most failures start as small edits that nobody notices until one costs the business something.

James listed what customers have reported. Employees drop "junior" from their job title, and customers end up believing they dealt with someone more senior. Others delete their phone number to avoid out-of-hours contact, and in some cases support suffered and the company lost important contracts. Among the most common problems is employees who don't realize they should include the legal disclaimer at all, which matters most in financial and legal services.

Ed named misrepresented seniority as the biggest legal risk. A recipient can argue they relied on the title, and the business can find itself caught by it.

James also shared two figures from Exclaimer's research. In customer interviews, 7 in 10 respondents said they only learned about a communication problem after the email had gone out, despite having archiving and analysis tools. And in Exclaimer's State of Business Email 2025 report, a Censuswide survey of 4,009 IT professionals, only 20% of organizations use a dedicated email signature management solution. The other 80% rely on patchwork processes, including IT-built scripts and employees managing their own.

James put most of it down to complacency rather than bad intent, and said generative AI makes that more prevalent because drafting an email now takes so little effort. Some cases are deliberate, such as a personal or political sign-off added to an email.

How Tamper Detection works

Email signatures applied server-side can't be edited by the sender. Email signatures deployed client-side can, and Tamper Detection catches the edits.

With server-side deployment, the email signature is added after the sender hits send, so the sender can't change it. With client-side, it appears in the Outlook compose window, and the sender can edit it before sending. Tamper Detection targets that second case.

In the demo, James changed a job title, deleted a phone number and removed the disclaimer. When he hit send, Tamper Detection caught all three and warned him, with the option to restore the standard email signature. It also catches changed images, added content and a removed email signature.

An admin's policy decides what happens next. A warning lets the sender go ahead anyway. Blocking, available in new Outlook, stops the email from sending. Policies apply by group, such as the sales team.

Every tamper event is recorded in the analytics section of the Exclaimer portal, showing who changed what. James said that record is what you'd show an auditor to prove you monitor for this. Tamper Detection is in beta now and launches in early 2027. It will be part of Exclaimer's Pro plan.

Start with warnings before you block anyone

Exclaimer recommends warning mode first. Move to blocking only where the data shows people still ignoring it.

Exclaimer's advice is to start in warning mode, which is what it did internally. Warnings show how much tampering is happening and who's doing it before anyone gets blocked, and going straight to blocking could upset a lot of people. Early adopters worried about false positives and about being seen as the team that blocks everything. In most cases, warnings alone were enough to change behavior, both internally and in the early adopter program. Blocking makes sense for people who keep making changes after being warned.

Exclaimer turned it on for itself and was surprised by what some employees were doing. Most of it came from complacency, and it started useful conversations about why the details need to stay in place. Ed, who has spent a decade in in-house legal and compliance teams, said not being seen as the team that blocks everything is a priority for those teams.

Where Tamper Detection doesn't work yet

Tamper Detection won't stop every edit, and it doesn't cover every setup yet.

The team was upfront about the limits on the call. If you only apply email signatures server-side, you don't need it, because the sender never gets the chance to edit anything. If you run server-side and client-side together, you do, because client-side email signatures take priority over server-side ones.

It's built for Microsoft 365 customers first. It doesn't work with Google Workspace today, and the team said it's on the roadmap to assess. On mobile, if someone sends from the Outlook app, Exclaimer can check after sending whether the email signature was changed, but it can't warn or block. That also only works if you route messages through Exclaimer using hybrid deployment.

It also won't guarantee that nobody ever edits an email signature. It tells you who's doing it so you can act. If a lot of people keep making the same change, the standard email signature may need updating instead.

Where to start this week

Talk to legal, settle who owns what, and test whether you can prove your disclaimer goes out.

James suggested three things you can do now, with or without Tamper Detection:

  1. Find out your requirements. Ask legal what your emails must contain. James said that conversation takes minutes.

  2. Settle the details. Decide who owns the disclaimer wording, which devices and employees the policy covers, and how you'll enforce it.

  3. Decide what happens when someone breaks the policy. Know who triages and what action follows.

On ownership, Ed said there's no single right answer. He's seen legal own the email signature and marketing own it, and legal and compliance still need a say either way. Legal tends to want it more prescriptive, and marketing wants it to fit the brand. At Exclaimer, marketing runs it day to day, IT supports, and the team works with legal on the disclaimer wording.

Ed's test is to ask whether you can prove your disclaimer goes out on every email and that nobody is changing your email signatures. If you don't know, or you only think so, start there.

How Exclaimer helps

Exclaimer's cloud solution manages email signatures centrally for more than 80,000 organizations.

Exclaimer's cloud solution applies brand and legal content to email signatures centrally for Microsoft 365 and Google Workspace. Tamper Detection adds a check for organizations that deploy client-side in Outlook. It also gives IT, legal and compliance one place to see every event, including warnings, blocks and mobile detections.

Watch the webinar on demand

The full session includes the live demo and audience questions on mobile, Google Workspace and who should own the email signature.

Watch the webinar on demand for the full conversation between James and Ed.