Email signature policy: the template to get approved internally

An email signature policy exists to settle the questions nobody wants to arbitrate in a meeting, and to make the decision outlive whoever took it. It does not need to be long: two well-written pages beat a twenty-page document nobody will open.

What a policy has to cover — and what it must not

The distinction is simple. What is locked technically does not need repeating in the policy: if the employee cannot change the logo, forbidding them to do so is pointless.

The policy covers what the tool does not settle:

• questions of practice — photos, social accounts, sign-offs;
• deliberate special cases;
• the update procedure and the owner;
• the reasoning behind the rules, which saves re-explaining it at every arrival.

The seven-section outline

1. Purpose and scope. Who is concerned — employees, apprentices, contractors, functional mailboxes — and which sends are covered. Three lines are enough.

2. Mandatory elements. The list of what appears in every signature in the organisation: name, job title, entity, means of contact, logo, legal notices. Point to the template rather than describing the layout.

3. What stays in the employee’s hands. Be explicit and generous here: this is the section that determines acceptance. Generally the direct phone number and, optionally, a personal booking link.

4. What is forbidden. Short, and reasoned: no personal quotes, no off-brand font or colour, no image standing in for text, no personal social accounts without authorisation. One sentence of justification per prohibition heads off argument.

5. Special cases. Executive team, spokespeople, contractors, subsidiaries. If your organisation plans exceptions, write them down. A deliberate exception causes no problem; an exception tolerated in silence delegitimises the whole policy.

6. Banner campaigns. Who can launch one, over what scope, with what approval lead time. Without that section, either nobody dares or everybody starts — see the campaigns page.

7. Owner and updates. The name of a role — not of a person — responsible for the policy, and the review frequency. Once a year is enough.

The three points genuinely debated

Experience shows the discussion always concentrates on the same subjects. Better to prepare them.

The photo. It is defensible in jobs built on direct, sustained relationships — consulting, property, recruitment. It weighs down a general signature. If you allow one, impose an identical format and crop, otherwise you will get holiday snaps.

Personal social accounts. A salesperson wants to include their professional profile, which is legitimate; it becomes trickier to accept a personal account with non-professional content. The wording that works: company accounts by default, personal professional accounts with the manager’s approval.

Executive exceptions. Management often asks for a variant. Treat it as a documented variant of the template, not as an informal derogation.

Worth knowing: have the legal notices validated by your counsel rather than copying a template found online. The obligations depend on your legal form and your sector — the general framework is described in mandatory legal notices.

The approval circuit

Three participants, one arbiter. Communications defines the content and the styling. Legal validates the notices. IT confirms feasibility and carries the deployment.

The usual blocking point is not disagreement but the absence of an arbiter: each defers the decision to the other two and the project stalls. Name the owner at the first meeting.

A policy does not apply itself

That is the most useful finding on this subject. A policy circulated by email, with HTML to copy and paste, produces a compliance rate that degrades from the first week and never recovers.

What applies a policy is a mechanism: a locked template, applied by the service from the directory, with no action from the employee. The policy then becomes a reference document — useful, consulted occasionally — rather than an instruction whose execution has to be monitored.

The full framework, from governance to deployment, is in the guide to company email signature management.