How long does standardisation across 200 employees take?

The technical deployment is a matter of minutes. The real calendar spreads over two to three weeks: designing the template, cleaning the directory, a pilot week, then going wide in waves.

Should everything switch over on the same day?

Below fifty or so mailboxes, yes, it is simpler. Beyond two hundred, proceed in waves of organisational units a day or two apart: you will never have more than a handful of simultaneous tickets.

How do we handle internal resistance?

By separating what is negotiable from what is not, and explicitly leaving one or two fields in each person's hands — direct phone number, booking link. A total constraint triggers workarounds; a constraint with a space of one's own is accepted.

What about employees who do not use Outlook or Gmail?

An add-in only covers the client it runs in. For sends from a third-party client or a line-of-business application, only a server-side rule can step in. Identify those cases during the inventory: they are generally few and mostly concern automated sends.

Standardising signatures across 50, 200 or 1,000 employees

A six-step standardisation plan, with what changes by size: 50, 200 or 1,000 mailboxes do not pose the same change management problems.

Standardising an organisation’s signatures is a project whose difficulty almost never lies in the technology. Deploying an add-in takes a quarter of an hour, across fifty mailboxes or a thousand. What changes with size is change management.

Step 1 — Measure the real gap

Do not start from an exhaustive audit: it is expensive and teaches nothing a sample does not.

Ask twenty or so people, spread across departments and levels, to forward you a message they sent this week. Count: how many different layouts, how many versions of the logo, how many legal notices present, how many expired job titles.

That picture is your best budget argument. A decision-maker who sees six contradictory signatures from their own company no longer needs convincing.

Step 2 — Settle the locking before designing

This is the structuring decision, and it is political more than graphic. Field by field: what is locked, what stays free?

Our recommendation, which works in the vast majority of cases: lock the logo, the structure, the colours and the legal notices. Leave the direct phone number free and, optionally, a personal link — a booking page, a professional profile.

That tiny margin changes everything in acceptance. A total constraint triggers ingenious workarounds; a constraint with a space of one’s own passes without debate.

Step 3 — Clean the directory

This is the systematically underestimated task, and it conditions the result: what is missing in the directory will be missing in the signatures, and what is inconsistent there will become public.

Concentrate on four attributes: job title, department, phone, 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 makes empty lines disappear rather than showing an orphaned label. The detail is in synchronising signatures with the directory.

Step 4 — The pilot

Ten or so people, chosen for their diversity rather than their goodwill: someone from sales, someone from support, someone who writes mostly from their phone, someone from a subsidiary if you have one, and if possible someone known to be demanding.

One week, with three specific checks rather than a general opinion:

Does the signature appear on a new message and on a reply?
Are the personal details accurate?
Is the rendering clean for an external recipient? Have them send a message to a personal address.

Step 5 — Go wide, at a pace that depends on size

This is where size changes the method.

Up to 50 mailboxes. A single switch, an announcement message, and it is done. The volume of questions stays absorbable by one person.

From 50 to 200 mailboxes. Two or three waves, by department. Plan a named contact per wave, to whom questions go, rather than a generic support channel.

Beyond 200 mailboxes. Proceed by organisational unit, a day or two apart, starting with the simplest structures. You will never have more than a handful of tickets at once, and each wave benefits from the lessons of the last.

Beyond 1,000 mailboxes. Same logic, but coordination with local entities becomes the real subject: each subsidiary has its contact, its legal notices and sometimes its language — see multi-brand signatures.

Worth knowing: every wave has to come with the instruction to clear the old local signature, with a screenshot. Without that, the two blocks stack up. It is the number one incident in this kind of project, and it is trivial to avoid.

Step 6 — Lock in the gains

Once standardisation is done, two mechanisms prevent drift.

Life cycle automation. Arrivals, moves and departures have to be reflected with no intervention. If every change requires a manual action, the gap returns within months.

A short policy. Two pages, to settle what the tool does not: photos, personal social accounts, executive exceptions. The model is in email signature policy.

What the project delivers, beyond consistency

The visible benefit is graphic. The lasting benefits are elsewhere: the end of signature tickets for IT, the certainty that legal notices are present everywhere, and the opening of a usable communication channel with scheduled banners.

The full economic calculation — internal time against subscription cost — is detailed in what manual management costs.