Anatomy of a Signature: What to Include, What to Cut

Almost nobody builds a bad email signature by leaving things out.

Bad signatures are built by addition. Someone starts with a name and a title. Then the phone number goes in. Then marketing asks for the LinkedIn icon, and if LinkedIn is in then Twitter should be too, and Instagram, since we post there now. Someone adds a quote they like. Legal supplies a disclaimer. A certification badge arrives after an audit. A banner goes up for the webinar and never comes down.

Eighteen months later the signature is longer than most of the emails it appears in, and every element in it can be individually justified by whoever added it.

This post gives a verdict on each field, with the reasoning, so you can prune yours with something firmer than taste.

The governing principle

A signature is not a place to put information. It is a place to put the small number of things a recipient might need.

Those are different goals, and confusing them is the root of every bloated signature. The question is never "is this true about me?" — it's "would a recipient, in the half-second they spend looking at this, be helped by it?"

Three practical reasons restraint wins:

Attention is finite and short. Nobody reads a signature. They glance at it, and only when they need something from it. Eleven lines and two lines get the same half-second of attention — but in eleven lines, the phone number they were looking for is harder to find. Adding fields makes the useful ones less useful.

Mobile is unforgiving. A signature designed at 500px on a desktop monitor gets a fraction of that width on a phone. Wide signatures wrap. Multi-column layouts collapse into a vertical mess. Long signatures push the actual reply content off-screen in a thread. Since a large share of business email is now read on phones, mobile is the constraint that should govern the design — and mobile punishes length harder than anything else.

Reply chains multiply everything. Your signature doesn't appear once. It appears in every message in a thread. A six-line signature in a twelve-message thread is seventy-two lines of repeated boilerplate. It also contributes to Gmail clipping messages that exceed its size threshold, hiding the rest of the conversation behind "View entire message."

So the default answer for any new field is no, and the burden of proof sits with inclusion.

The test

When you're unsure about a field, three questions. It needs a yes to at least one.

1. Does the recipient need this to act? A phone number for someone who needs to call. A booking link for someone who needs to schedule.
2. Does it prevent a misunderstanding? A job title so a forwarded email makes sense. Support hours so nobody expects a reply at midnight.
3. Is it legally required? The statutory block, for Indian companies.

If it's none of the three, it's decoration — and decoration in a signature costs more than it looks like it does.

"It builds credibility" is not a fourth question. It's what people say about the field they want to keep for reasons they haven't examined.

Field by field

Full name — Include, always

The one non-negotiable field.

Write it as the person actually writes it. If someone's name is S. Venkatesh, that initial belongs at the front and is not a middle initial to be relocated to the end. If someone uses a single name, use it. Templates that mechanically render {first_name} {last_name} will produce wrong output for a meaningful portion of an Indian team, and being wrong about someone's name on every email they send is a bad look that compounds daily.

Ask people how they write their name. Use that.

Job title — Include, always

Not for status. For routing.

Business email gets forwarded constantly, and a title tells the second reader whether you're the right person to be talking to. Without it, a forwarded message arrives from a stranger with unknown authority.

Use the title on record with HR, not an inflated version. "Growth Ninja" is a cost, not a personality.

Company name — Include, always

The most commonly missed field in casual signatures, and the most damaging omission. A signature without a company name is a name and a phone number — it could be anyone.

Department or team — Conditional

Include if your company is large enough that departments are meaningfully different doors — if "Sales" and "Partnerships" would route to different people, say which one you are.

Below about twenty-five people, cut it. In a small company the title already carries the information, and the department line is redundant.

Pronouns — Optional, and the individual's choice

If someone wants them, they go on the same line as the title. If someone doesn't, that's equally fine.

The one thing not to do is mandate it in either direction. A company-wide requirement to include pronouns and a company-wide prohibition are both the same error — a personal disclosure decided by policy.

Professional credentials — Conditional, and stricter than you think

Include where the credential is a licence that governs the work: CA, CS, Advocate, CFA, MD. In these cases the credential tells the recipient what you're permitted to do, which is functional information.

Cut course certifications, vendor badges, and completion credentials. A recipient does not need to know which two-day workshop you attended, and a signature that lists four acronyms after a name reads as insecurity rather than authority.

Test: would the absence of this credential change what you're legally allowed to do? If not, cut it.

Phone number — Include, usually

For anyone client-facing, yes. Email is not always the right channel, and a recipient who has to reply and wait in order to get your number has been slowed down by your signature's omission.

Format for humans: +91 98765 43210. Label if you list more than one — M: and T: removes ambiguity instantly.

One number, not three. Mobile, landline, alternate mobile and WhatsApp is not four times as reachable; it's a decision the recipient now has to make. Pick the one you actually answer.

For roles with no external contact — backend engineering, internal finance — cut it. There's no benefit to publishing a phone number that nobody has a reason to call.

Email address — Include, usually

Yes, even though they're reading your email. It survives forwarding, printing, and screenshots, and it lets someone copy your address without digging through message headers.

The exception is a signature that's already tight and where the address is unambiguous from the sender field. This is the field to cut first if you're one line over.

Website — Include, usually

One URL. The homepage.

Not the homepage plus the careers page plus the blog plus the product page. If a recipient wants any of those, they'll find them from the first one.

Physical address — Conditional, and compliance-driven

For an Indian private limited company: the registered office address is part of the statutory block required by Section 12(3)(c) of the Companies Act, 2013, alongside the company name and CIN. That's not optional and it belongs in the footer.

Note this is the registered office, which is often not where you sit — startups incorporated at a CA's premises are a common case. If you also want to show your operating address, that's a separate line and a commercial choice.

For freelancers and sole proprietors, there's no equivalent obligation. City only, if anything. Don't publish a home address to every person you email.

Logo — Include, usually

This is the field that makes a signature branded rather than merely informative.

Rules: around 180px wide as a ceiling, hosted on a stable HTTPS URL, and with real alt text — alt="Meridian Labs", never alt="". Image blocking is routine and default in many clients, and alt text is the difference between your company name appearing as clean text and a broken-image icon appearing instead.

Cut it only if your brand has no usable logo mark, in which case set the company name in your brand colour and move on.

Headshot — Conditional

Include for roles where personal recognition does real work — sales, recruiting, client-facing consulting, real estate. A face helps someone remember which conversation you were.

Cut for everyone else. It's a second image, doubling the weight and the number of things that can break, for a benefit that's mostly aesthetic. And if you include it, be consistent across the team — a company where half the sales team has photos and half doesn't looks unmanaged.

Social media icons — Rarely, and fewer than you want

The most over-included element in signatures.

Ask what happens if someone clicks. For most companies the answer is: they leave a conversation with you to go look at a feed that was last updated in March. That's a downgrade.

Where it earns its place: LinkedIn for individuals in sales, recruiting, or business development, where the profile is genuinely part of establishing credibility. And portfolio platforms for creative businesses — Behance or Dribbble for a design studio, where the work is the pitch.

Cut Facebook, X, Instagram and YouTube from individual signatures unless the account is a real part of how you sell. Cut all of them from engineering, finance, and operations signatures.

And if you include icons: two maximum, as small monochrome marks, not a row of six brand-coloured squares that pulls the eye away from everything else.

Meeting or booking link — Conditional, for sales

Include for anyone whose job involves getting meetings scheduled. It removes an entire round-trip from every deal, which is the clearest ROI of any optional field.

Label it as an action — "Book a call" — rather than pasting a bare URL.

Cut for everyone else. A booking link in a support engineer's signature invites meetings nobody wants.

Campaign banner — Conditional, and marketing owns it

A banner is legitimate when there's an actual campaign — a webinar with a date, a hiring push, a product launch, a report worth downloading.

Two rules make banners work rather than annoy. It must expire: a banner promoting a March webinar still running in August tells recipients you don't look at your own emails. And one owner: marketing decides what's in the slot, or you end up with each department promoting something different and the signature becoming a noticeboard.

If there's no current campaign, the slot is empty. An empty slot is fine.

Confidentiality disclaimer — Short, if at all

No Indian statute requires one. It's weak as a unilateral contractual instrument, since it appends to a message the recipient has already read. Its value is mostly evidentiary and organisational.

Two lines maximum. The 200-word version that dwarfs the actual message is cargo cult compliance, and it does no more work than the short one. Regulated sectors — banking, insurance, securities, healthcare — may have specific requirements from sectoral regulators, and those are real.

Statutory compliance block — Mandatory for Indian companies

Company legal name as registered, CIN, registered office address. Section 12(8) prices non-compliance at ₹1,000 per day, up to ₹1,00,000, applying to the company and to each officer in default separately.

Set it at 10–11px in a muted grey, below a visual break. It isn't there to be read; it's there to be present.

GSTIN is not required in email — GST law asks for it on tax invoices and on the name board at your place of business. Include it if your B2B customers keep asking for it, and leave it out otherwise. If you hold registrations in multiple states, a single hard-coded GSTIN in a company-wide template will be wrong for part of your team.

Inspirational quote — Cut

There is no version of this that helps. It's the clearest example of a field that answers "is this true about me?" rather than "does the recipient need this?"

"Please consider the environment before printing" — Cut

Nobody was going to print it. The line adds weight to every email you send in order to discourage a behaviour that has largely stopped happening.

"Sent from my iPhone" — Cut

The default device signature undoes your branding on exactly the emails most likely to be quick, informal, and sent to people mid-conversation. Replace it with a short text version of your real signature — name, company, phone.

Mobile is configured separately from desktop in every major email client, which is why this survives in companies that otherwise have their signatures in order.

Award badges and certification logos — Rarely

One, if it's a meaningful trust signal in your industry — ISO certification for a manufacturer, a security certification for a SaaS vendor selling to enterprises.

Three or more, and you've built a trophy cabinet. Each badge is another image that can break, and the marginal credibility of the third one is close to zero.

The summary table

The subtraction exercise

If you already have a signature, the fastest way to improve it is not to redesign it. It's this.

Open it. Delete every line. Then add back only the fields that pass the three-question test, in this order:

1. Name
2. Title and company
3. One phone number
4. Website
5. Logo
6. Statutory block

Stop. Look at it. That's a complete, professional, compliant signature and it's six lines.

Now add back anything else you actually miss. In our experience the honest answer is one item, usually a booking link for sales roles — and the rest of what you deleted was accumulated rather than chosen.

A working length target: four to six lines above the statutory footer. Above eight, you're costing your reader more than you're giving them.

Where variation belongs

Restraint doesn't mean one identical signature for everyone. It means each variation is deliberate.

The pattern that works: a fixed core — name, title, company, logo, statutory block — that nobody may alter, plus a small set of approved role additions. Sales gets a booking link. Support gets a helpdesk address and published hours with the timezone stated. Recruiting gets a careers link.

What you're avoiding is the third state, where everyone improvises. That's how you end up with forty signatures that share no common element and where the compliance footer appears on about half of them.

The part that makes this hard

Pruning one signature takes ten minutes. Keeping forty pruned is a different problem.

Signature bloat isn't a one-time failure — it's an accretion process. Fields get added by well-meaning people, one at a time, each with a reason, and nobody is watching the total. The person who adds the Instagram icon isn't wrong; they're just the fourth person to add something this year. And because you never see your own team's outbound email, the drift is invisible until someone forwards you a screenshot.

The structural fix is a locked core. When the fixed fields are deployed centrally and can't be edited locally, additions happen in the approved slots or not at all — and a decision about what belongs in a signature is made once, by whoever owns the brand, rather than forty times by whoever last got a request.

That's what we've built Signforus to do: one template across the team, with the core locked and role variations defined, at flat pricing rather than per seat, for Indian teams of five to fifty. We're in early access now.

But do the subtraction exercise first, on your own signature, today. It costs ten minutes and it'll tell you more about what your team's signatures should look like than any template gallery.