Email Signature Rollout and Rebrand Playbook: Phased Deployment for IT and Marketing (2026)
A project playbook for IT and Marketing: who does what, the decisions to take before setup, data and template preparation, a pilot test matrix, phased deployment with exit criteria, a rebrand-day countdown, employee communication, monitoring and rollback.
Sophie Grant
Email Signature Specialist, Scribe
On this page
- Who needs to be involved, and how long does a rollout take?
- What should you decide before changing any setting?
- How do you prepare data, templates and the domain?
- How do you run the pilot?
- How do you go from pilot to company-wide?
- How do you switch every signature on rebrand day?
- What should you tell employees?
- What should you monitor after launch?
- How do you roll back if something goes wrong?
- Where does Scribe fit?
- Frequently asked questions
- How long does a company-wide email signature rollout take?
- How big should a signature pilot group be?
- Should we install all signatures at once or department by department?
- How do we switch every signature on rebrand day?
- Do employees need to do anything during the rollout?
- How do we know the rollout worked?
- What happens to signatures when the free trial ends?
- How do we roll back a signature deployment?
- Related Handbook guides
TL;DR: A company-wide signature rollout is a two-team project: IT connects the email provider and directory once (Scribe estimates about 10 minutes of hands-on work), and Marketing designs, assigns and deploys (15 to 20 minutes). The calendar time comes from data cleanup, sign-off and provider propagation, not the tool. Run it in four phases: prepare, pilot with 10 to 30 people, roll out by department, then go company-wide with auto-assign for new hires. For a rebrand, prepare the new design as an unpublished draft, check it in preview, and publish on the day: published changes push to every assigned teammate automatically.
Last reviewed: October 2026. Covers Microsoft 365, Google Workspace and Zoho Mail deployments managed from Scribe. Platform-specific steps are in the Microsoft 365 and Google Workspace guides.
This playbook is for the IT lead and the marketing or brand lead who have been asked to "get everyone on the new signature". It covers who does what, the decisions to make before touching any setting, a phased deployment plan with exit criteria, how to run a rebrand day, what to tell employees, and how to monitor and roll back. Platform mechanics are in the Microsoft 365 and Google Workspace guides; this one is about running the project.
Who needs to be involved, and how long does a rollout take?
Scribe's own guidance splits the work by company size. Under about 50 employees, one person with admin access to the email provider usually does everything. From 50 to 5,000+ employees, it is split between IT and Marketing, with Security and Legal sometimes reviewing data handling, SSO and compliance (Which departments are involved).
| Team | Owns | Hands-on time (Scribe estimate) |
|---|---|---|
| IT | Connect the email provider, install the integration, configure the custom sending domain; directory scope; server-side routing if used | About 10 minutes |
| Marketing / Brand | Design templates, assign them to teammates, deploy; banners afterwards | About 15 to 20 minutes |
| Legal / Compliance | Disclaimer text, regulated-entity wording, which variants must keep it | Review only |
| Security | Vendor review: permissions, data stored, SOC 2 report, SSO | Review only |
| HR / People Ops | Accuracy of titles, departments and phones if the HRIS is a data source | Data cleanup |
Time estimates are from How long does it take to set up Scribe?, which also says most teams deploy their first signatures in under 30 minutes. Plan the calendar around the slow parts instead: security review, legal sign-off on disclaimers, fixing directory data, and provider propagation. Microsoft says admin-deployed Office add-ins can take 24 to 72 hours to appear (Microsoft Learn); Scribe notes Gmail installs can also take up to 72 hours (Installation statuses). As a planning assumption (not a Scribe figure), allow two to four weeks from kickoff to company-wide for a few hundred to a few thousand mailboxes, most of it waiting on reviews and data fixes.
Get started with Scribe
Roll out signatures to your whole organization
Free 14-day trial — no credit card.
What should you decide before changing any setting?
Rollouts usually stall on a decision nobody owned, not on configuration. Take these in the kickoff meeting:
- Deployment method. Client-side (signature visible while composing) or server-side (added in transit, covers every device and app), or both. The trade-offs are in client-side vs server-side. When both are connected in Microsoft 365, Scribe defaults to the add-in and server-side covers what it can't reach (Integrations overview).
- Data owner per field. Directory, HRIS, phone system or the employee. See HRIS as the source of truth.
- Template set. How many designs: one per brand, region or department? Fewer is easier to govern. Folders in Scribe can group them by team, brand or country (Signatures overview).
- Variants. Whether replies and internal emails get lighter versions. See replies, internal emails, aliases and shared mailboxes.
- Legal text. Which disclaimer, on which templates and variants. See email disclaimers.
- Rules. Who may edit templates (Scribe roles: Owner, Admin, Member) and what employees may change themselves. Write it into an email signature policy.
- Pilot group and success criteria. Named people and measurable exit criteria, set before anything is installed.
How do you prepare data, templates and the domain?
Preparation is where the quality of the rollout is decided. Four steps:
1. Connect and scope the directory. Sync only real senders. In Entra ID or Google Workspace you can select people, units or groups, and import aliases and (in Microsoft 365) shared mailboxes (Connect Entra ID, Google Workspace directory). Details are in the Entra ID guide.
2. Close data gaps. The Smart Fields page shows how complete each field is across teammates. Mark only the fields your templates use as required, then fill gaps at the source, by CSV, or by inviting teammates to fill their own (Smart Fields). Empty fields don't break the design (the block is dropped), but they do send signatures without a title or phone number. Aim for under 5% missing on required fields before the pilot.
3. Build and check templates. Preview shows every assigned teammate's real signature side by side, with Primary, Reply and Internal tabs and a light and dark mode toggle (Preview signatures). The per-teammate preview adds Outlook, Gmail and Apple Mail mockups, device sizes and Send test email (Teammates overview). Look for long titles that wrap, logos that disappear on dark backgrounds, and people whose signature is missing lines. Image weight and dimensions are covered in the image size guide; for Gmail, keep in mind its 10,000-character limit (Gmail signature too long).
4. Set the custom sending domain before launch. By default, Scribe signature asset and tracking URLs use sendassets.io. A custom sending domain (two CNAME records) makes them use your own domain, and once validated every signature switches automatically (Configure your sending domain). Doing it before launch means the links in mail already sent never change domain later. It doesn't affect SPF or DKIM.
Then assign. Use Smart Field conditions such as "Department is Sales" rather than hand-picked lists, and enable auto-assign this signature to all future teammates so new hires are covered without a ticket (Assign teammates).
How do you run the pilot?
Microsoft's recommended rollout for Office add-ins is the same shape as any good pilot: a small set of business stakeholders and IT first, then more people, then everyone (Microsoft Learn). Build the pilot group to cover variety, not seniority:
- 10 to 30 people from at least three departments, including one high-volume external sender (Sales or Support).
- Every client you support: new and classic Outlook for Windows, Outlook for Mac, Outlook on the web, Gmail on the web, iPhone and Android, plus Gmail for Android and Apple Mail if you route server-side (client-side installation doesn't reach them).
- At least one alias user, one shared address (a Microsoft 365 shared mailbox, or on Google Workspace a team address added as an alias), one person with an empty mobile number and one with a very long title.
- Someone from Legal, so the disclaimer is checked in real mail.
In Microsoft 365, deploy the add-in to a pilot group rather than the entire organization at first (the Integrated Apps step lets you pick). In Scribe, install the pilot's signature one at a time from its overview page (Install signatures). Then test from the recipient's side:
| Test | Pass when |
|---|---|
| New message on each client | Primary signature present, layout intact, images load |
| Reply and forward | Reply variant used, if activated (Outlook add-in or server-side only) |
| Email to a colleague | Internal variant used, if activated (Outlook add-in or server-side only) |
| Send from an alias and a shared mailbox | The signature assigned to that address |
| Dark mode on desktop and phone | Logo and text readable |
| External recipient in a different mail system | No broken images; DKIM and DMARC pass if server-side is on |
| Teammate edits their own signature locally | Approved signature returns on the next compose (Scribe docs) |
Exit criteria for the pilot: every row passes on every client, no deliverability change, and no open data issues for pilot users.
How do you go from pilot to company-wide?
| Phase | Scope | Actions | Exit criteria |
|---|---|---|---|
| 0. Prepare | None | Decisions signed off, directory scoped, data gaps under 5%, sending domain validated, templates previewed | Sign-off from Marketing, Legal and IT |
| 1. Pilot | 10-30 people | Install per signature; run the test table | All tests pass |
| 2. First departments | The heaviest external senders, often Sales and Support | Install their signatures; tick "Notify teammates" | Installed above 95% for those teams; help-desk tickets near zero |
| 3. Company-wide | Everyone | Add-in to the entire organization; install all signatures at once | Assigned teammates equals team size; installed close to assigned |
| 4. Steady state | New hires | Auto-assign on; quarterly data audit; Marketing runs banners | No manual work per hire |
Scribe supports both styles of install: Install Signatures on the Signatures page deploys selected signatures at once, and each signature's overview page installs that one only, which is the progressive option (Install signatures). Enterprise customers can stage by department or deploy in one step (Scribe for enterprise).
Expect Pending statuses after each install. For Microsoft 365, the signature installs when the person next composes an email, so it stays Pending until then; Gmail can take up to 72 hours; Zoho Mail installs at once (Installation statuses). Don't chase Pending on day one.
One commercial check before phase 3: if you are still on Scribe's 14-day trial, upgrade before it ends. When a trial ends or a plan can't cover the active signatures, Scribe turns off all active signatures and removes them from email, not only the ones over the limit; they are reinstalled automatically once resolved (Plan limits and changes).
How do you switch every signature on rebrand day?
A rebrand is the best test of a central signature setup: a new logo, colors, legal entity name or domain must appear everywhere at the same moment. The mechanics in Scribe that make this work:
- A signature with unpublished changes is a Draft; teammates keep the last published version until you publish (Signature status).
- After the first install, any design change you publish is pushed to assigned teammates automatically, without reinstalling (Install signatures).
- Banners can be scheduled with a start and end date, time and time zone, and can either replace or combine with existing marketing blocks (Marketing campaign).
Scribe's docs describe scheduling for campaigns, not for publishing a signature design, so plan the design switch as a manual publish by a named person at a set time. A countdown that works:
| When | Action | Owner |
|---|---|---|
| T-14 days | Duplicate each live signature as a backup copy (Scribe documents a Duplicate action but not version history); upload new logos to the image library | Marketing |
| T-10 | Edit the live signatures as drafts with the new design; do not publish | Marketing |
| T-7 | Preview every teammate in light and dark mode; send test emails; Legal checks entity names and disclaimers | Marketing, Legal |
| T-3 | Schedule the launch banner campaign to start at launch time; set the old campaign to end | Marketing |
| T-1 | If the email domain changes, confirm new addresses and aliases are synced and the sending domain is validated | IT |
| T-0 | Publish all drafts; spot-check five people on different clients | Marketing, IT |
| T+1 | Check installation counters and failures; fix stragglers | IT |
Two rebrand traps. If the company domain changes, signatures are tied to mailboxes, so the new primary addresses must exist in the directory before the switch; aliases on the old domain can keep their own signatures (Aliases). And with server-side routing in Microsoft 365, the copy in Sent Items doesn't show the signature, so check from a recipient's mailbox, not your own (Scribe: Microsoft 365 server side).
What should you tell employees?
Less than you think, because they don't have to do anything. With automated integrations, teammates take no action to install or update signatures (Do teammates need to install their signature?). Scribe's install modal has a Notify teammates via email about their new signature option: the email shows a preview of the new signature, who deployed it, which email client it applies to, and that no action is needed (Install signatures). Campaigns have a similar optional notification when they start (Marketing campaign).
Add one short internal announcement of your own, because people will otherwise ask why their personal signature "disappeared". A template:
Subject: Your email signature is now managed centrally
From today, everyone's email signature is generated from our company
directory, so your name, title and phone number are always up to date.
You don't need to do anything. If a detail is wrong, update it in
[HR system / IT request form] and it will appear within a day.
Personal edits to your signature will be replaced automatically.
Questions: [channel or contact].The last line matters: Scribe re-applies the approved signature each time someone composes, so local edits only last for one email (Scribe docs). Tell people where to fix data instead.
What should you monitor after launch?
Use the counters first. The Signatures page shows how many teammates are assigned out of your team size and how many signatures are installed out of those assigned; a gap in either is your to-do list (Signature status). Then work through statuses:
| Status | Meaning | Action |
|---|---|---|
| Pending | Waiting on the provider (Microsoft: until next compose; Gmail: up to 72 hours) | Wait |
| Not activated | Installation not turned on for this signature | Click Install signatures on the signature's overview |
| Failed: user not found | Address doesn't match a mailbox, often an alias not set up as "Send mail as" in Gmail | Fix the address or alias, then reinstall |
| Failed: forbidden | Scribe isn't authorized for that mailbox | Reconnect the integration with the right permissions |
| Failed: signature too long | Over Gmail's 10,000-character limit | Simplify the template |
| Not supported | The integration installs one signature per email; only the highest priority one was installed | Expected; adjust signature priority if the wrong one won |
| Access lost | Connection to the integration lost; admins are emailed | Reconnect |
Statuses and causes are from Signature installation statuses and errors. Filters on the Teammates page combine installation status with missing information, so "failed and missing data" is one view (Teammates overview).
For larger tenants, automate it. The signature.installation.failed webhook fires once per failure transition with an error code such as user_not_found or signature_too_long (Webhook events); route it to your help desk. The API lists per-email installation state (API reference), and the MCP server can answer "audit install and compliance status" from an AI assistant (Scribe AI agents). More in the API and webhooks guide and managing signatures with AI.
How do you roll back if something goes wrong?
- One signature: uninstall it from the Install Signatures modal with the ✕ next to it (Install signatures).
- A bad design change: re-apply the backup copy you duplicated before editing, and publish.
- Server-side routing in Microsoft 365: disable the mail flow rule; mail leaves Exchange Online directly again and the connectors can stay in place unused (Scribe docs).
- A bad banner: pause the campaign; its marketing elements are removed immediately and replaced with the previous ones (Marketing campaign).
Write the rollback steps into the launch plan before T-0, with the person who will run each one.
Where does Scribe fit?
Scribe covers the full rollout loop in one place: directory and HRIS data, templates and variants, progressive or all-at-once install, employee notification, status monitoring, and scheduled banners, on Microsoft 365, Google Workspace and Zoho Mail. For larger organizations Scribe says enterprise customers get dedicated onboarding and support (Scribe for enterprise; see also the enterprise page), and the IT page covers handing day-to-day changes to Marketing. Pricing is per user with a 14-day trial (pricing).
Frequently asked questions
How long does a company-wide email signature rollout take?
The hands-on setup is short: Scribe estimates about 10 minutes for IT and 15 to 20 minutes for Marketing, and most teams deploy first signatures in under 30 minutes. Calendar time comes from security review, legal sign-off, directory cleanup and provider propagation; Microsoft says admin-deployed add-ins can take 24 to 72 hours to appear, and Gmail installs can take up to 72 hours.
How big should a signature pilot group be?
Large enough to cover variety, not seniority: 10 to 30 people across at least three departments, every email client you support, at least one alias user, one shared mailbox, someone with missing data and someone from Legal. Microsoft's recommended add-in rollout follows the same pattern: stakeholders and IT first, then a wider group, then everyone.
Should we install all signatures at once or department by department?
Pilot first, then deploy to the heaviest external senders, then everyone. Scribe supports both: Install Signatures on the Signatures page deploys selected signatures at once, and each signature's overview page installs only that signature for a progressive rollout.
How do we switch every signature on rebrand day?
Prepare the new design as unpublished drafts, check every teammate in preview, and publish at a set time. In Scribe, teammates keep the last published version while a signature is in draft, and published changes are pushed to assigned teammates automatically without reinstalling. Banners can be scheduled with start and end times; the design publish itself is a manual step.
Do employees need to do anything during the rollout?
No, with automated integrations teammates take no action. Scribe can email each person a preview of their new signature with a note that no action is needed. Tell people where to fix wrong data instead, because local edits are replaced the next time they compose.
How do we know the rollout worked?
Compare assigned teammates with team size and installed signatures with assigned teammates, then work through statuses: Pending, Not activated, Failed, Not supported and Access lost. Larger tenants can route the signature.installation.failed webhook to the help desk and read per-email install state from the API.
What happens to signatures when the free trial ends?
If the workspace moves to the free plan or a plan can no longer cover the active signatures, Scribe turns off all active signatures and removes them from email, not only those over the limit. They are reinstalled automatically once you upgrade, so upgrade before the trial ends if you are mid-rollout.
How do we roll back a signature deployment?
Uninstall the signature from the Install Signatures modal, re-publish a backup copy you duplicated before editing, pause a problematic banner campaign, or, for Microsoft 365 server-side routing, disable the mail flow rule so mail leaves Exchange Online directly again.
Related Handbook guides
Get started with Scribe
Roll out signatures to your whole organization
Free 14-day trial — no credit card.
