Moving from individual Gmail signatures to centralised management

The starting point is almost always the same: everyone has configured their Gmail signature on their own, nobody knows how many variants are circulating, and the communications department has just asked for a unified brand. Here is how to run that switch without a crisis day.

Step 1 — Take an inventory, without spending three weeks on it

You do not need an exhaustive audit. A sample is enough to gauge the scale: ask twenty or so people, spread across departments, to forward you a message they recently sent.

What you are looking for comes down to four questions. How many different layouts? How many show a logo, and which one — old brand included? How many carry legal notices, and are they current? How many announce an expired job title?

The result is almost always worse than expected, and that is useful: that sample will justify the project to management far better than any pitch.

Step 2 — Design the template, and settle the locking

The template is designed once, in the editor, from the brand guidelines. Most of the work is not graphic: it is the decision, field by field, of what stays editable.

Our recommendation, tried and tested: lock the logo, the structure, the colours and the legal notices; leave the direct phone number free and, optionally, a personal booking link. That tiny margin changes everything in how the project is received — people take total constraint badly, and a constraint with a space of their own very well.

Decide the split by organisational unit at that point too, drawing on the OU structure.

Step 3 — Clean the directory

This is the step everyone underestimates. Dynamic fields draw on Google Directory: anything missing there will be missing in the signatures, and anything inconsistent there will become public.

Concentrate on four attributes: job title, department, phone and site. Normalise the titles — “Sales Mgr” and “Sales Manager” have to converge — and move the numbers to the international format.

Check too that your template does make empty lines disappear: an employee without a work mobile must not see “Mobile:” followed by nothing.

Step 4 — The pilot

Install the add-on domain-wide, but attach the templates to a single test organisational unit — or create a temporary one with about ten representative people: someone from sales, someone from support, someone who writes mostly from their phone, and someone from a foreign subsidiary if you have one.

Let it run for a week, asking for three specific checks rather than a general opinion:

1. Does the signature appear correctly on a new message and on a reply?
2. Are the personal details accurate? This is where directory gaps surface.
3. Is the rendering clean for an external recipient — send yourself a message at a personal address and look at the real result.

Worth knowing: explicitly ask the pilots to clear their old Gmail signature, and check the message does not end with two blocks. It is the number one migration incident, and it is trivial to avoid.

Step 5 — Go wide in waves

Do not switch the whole domain over on the same morning. Proceed unit by unit, starting with the simplest structures, a day or two apart.

Each wave comes with a short message: what changes, what stays editable, and the instruction to clear the old signature in the Gmail settings — with a screenshot, not a description. The completion rate doubles when you show the screen.

In three or four waves, the whole domain has moved, and you never had more than a handful of simultaneous tickets.

What changes once the switch is done

The immediate benefit is consistency: one brand, current everywhere, legal notices included. The lasting benefit is elsewhere: the signature stops being a topic.

A new joiner gets theirs as soon as their account is created, with no tutorial — see the onboarding article. A brand change deploys in a single template edit. And the channel becomes usable for communication, with scheduled banners the admin console could never handle.