Email Signature for Remote Workers — What to Include

What changes for remote workers

In an office, context is ambient. Everyone knows roughly where you are, what hours you keep, and how to reach you quickly. Remote work strips all of that away. Your email signature is one of the few places where you can restore some of that context automatically — without having to explain it in every email body.

The core additions for remote workers:

• Time zone — so recipients know when you're actually working
• Location — city-level, for cultural and scheduling context
• Video call link — to skip the scheduling back-and-forth
• Availability hours (when yours differ from standard)
• Async communication handle (Slack, Teams)

Not all of these belong in every remote worker’s signature — it depends on how distributed your team is and who you email externally. We’ll break each one down below, including when to skip it.

Time zone — the most important addition

If your team or clients span more than one time zone, your time zone is the single most useful addition to your remote signature. It answers “when can I expect a reply?” without anyone having to ask.

How to format it

Remember to update it when daylight saving time changes, if your offset shifts. GMT+1 (BST) in summer is not the same as GMT (GMT) in winter. A wrong time zone in your signature can cause scheduling errors — it’s worth a 30-second check every spring and autumn.

For fully co-located teams in the same time zone, skip this. It adds length without value if everyone is in the same city.

Location: city, not address

Including your location in a remote signature gives colleagues and clients useful context: cultural reference points, travel logistics, and a quick mental anchor for who you are. City-level is the right granularity.

A home address in an email signature is a privacy issue and provides no useful information beyond what the city already gives. Never include it.

For roles where your location is part of your professional identity — a consultant based in a specific market, for example — you might combine location and time zone: “Singapore | SGT (UTC+8)”.

Video call links and booking links

For anyone who takes regular video calls with external contacts, a meeting link in your signature is a genuine time saver. It converts the multi-email “when are you free?” process into a one-click action.

Two approaches

Don’t include both a scheduling link and a video room link — that’s two lines doing similar jobs. Pick the one that matches how you actually work.

If you rarely take calls, or if your calls are always ad hoc and internally initiated, skip this entirely. It adds a line that most recipients won’t use.

Availability hours

A working hours note is useful in two specific scenarios: when your hours are significantly different from the norm, or when you’re on a compressed schedule (four-day week, school hours, early starts).

When to include it

• You work a four-day week and want to set expectations about which day you're offline
• Your working hours are significantly shifted from standard office hours (e.g., 6am–2pm)
• You have a regular daily offline period (e.g., school pickup, 3–5pm)
• You're a contractor who works a fixed number of hours and wants to signal that

When to skip it

• Your hours are conventional and match your stated time zone
• You're in an 'always available' culture where listing hours would look odd
• Your availability changes week to week (update your calendar status instead)

Format: “Mon–Thu, 8am–4pm GMT” or “Mon–Fri, 9am–5pm CET (Fri off)”. Keep it to one line. Don’t elaborate on the reasons for your schedule — that’s not your signature’s job.

Slack and Teams handles

If your team uses Slack or Microsoft Teams heavily — and most distributed teams do — listing your handle in your signature is a small touch that removes a lookup step for new contacts.

This is most useful in email signatures sent to other people in the same organization, or to external contacts who are also in your Slack workspace. For purely external contacts who won’t have access to your workspace, a Slack handle is meaningless.

One line is enough. Don’t list both Slack and Teams unless you genuinely use both for different contact groups — that’s adding lines that most recipients won’t act on.

The “I might not reply instantly” debate

You’ve probably seen this line in remote workers’ signatures: “I work asynchronously and may not reply immediately. Please don’t expect an instant response.” Or variations like “I batch my email twice a day”.

The case for it

Setting explicit expectations reduces anxiety on both sides. If recipients know you batch your email, they won’t ping you on Slack an hour later wondering why you haven’t replied. In async-first teams (fully distributed companies that deliberately avoid real-time pressure), this line is common and culturally expected.

The case against it

To clients and external contacts outside your organization’s culture, a “don’t expect a fast reply” line reads as indifferent or defensive. It pre-justifies slow responses before they’ve even happened. If your SLA or professional norms require a response within 24 hours, the line is also misleading.

Signatures by remote worker type

Different remote setups have different signature needs. Here’s a tailored breakdown.

Multiple time zone display

Occasionally someone asks about showing two time zones — for example, an American working with European clients who wants to display both ET and CET. It’s possible, but it only works if both time zones are genuinely relevant to your contact’s daily experience.

Keep it to two time zones at most, and only include a second one if you genuinely straddle both in your daily work. Three or more time zones in a signature becomes unreadable and suggests you’re covering for an unrealistic schedule.

For more on what remote workers should and shouldn’t include, the what to include in an email signature guide covers every element in detail. The business email signature guide is also worth reading if you’re setting up signatures for a distributed team.

Frequently asked questions

Related reading