HelloSiteWorks Websites. Branding. Beautiful details.Let’s talk Email us
Start a project
← Back to the journal
Mint paper fox comparing the same conceptual email signature in a desktop inbox and on a phone beside a checklist.
Original HelloSiteWorks concept illustration. Screen details are illustrative.
HELLOSITEWORKS FIELD NOTES · Email

Check your email signature where people read it.

Move the review from a polished layout into an ordinary message, then check the details people need to read and use.

4 min read · Practical ideas for a stronger first impression

The useful bits.

Review a received test email, not only a mockup.

Check the visible contact text and every link destination.

Repeat the check on a phone and after details change.

Start with a realistic message.

A signature can look finished in a design preview while still needing an ordinary inbox check. Put the proposed version beneath a short, realistic message and send a test to an account you control. Use the same signature setup you intend to use for everyday correspondence. A picture of the layout is a useful reference, but it is not the message someone will receive.

Begin with the recipient’s task. They may need to recognise who wrote, find the business website or choose a contact route without reading the whole conversation again. Keep the test focused on those details. Include a normal greeting and a few lines of message text, so the signature is judged as the end of an email rather than as a separate advertising panel.

Read the contact details before judging the decoration.

Check the name or shared-inbox identity, business name and intended contact information against the current approved source. Read every character rather than relying on how familiar the address looks. If the signature includes a title, telephone number or website, confirm that each belongs in this sender’s version. Leave out information that has not been supplied or agreed.

Then look at the hierarchy. Can you find the sender and contact route quickly? Does the signature feel like a considered sign-off beneath the message, or does it compete with the message itself? A fictional studio might need a name, role and website; a shared enquiries inbox might need the business identity and a clear reply route. The same arrangement does not have to answer both situations.

Follow the links in the received email.

Open the received test and use each intended link. Check that the website opens the expected page and that any linked email address is correct. A visible label can look right while its destination still needs attention. Review the address and what it opens together, particularly after replacing example details in a template.

Keep the links purposeful. A website link and a small set of relevant social destinations may be enough for the sender’s needs. If an old campaign link no longer belongs in everyday correspondence, remove it from the proposed version before treating the signature as ready. Write down a problem precisely: which link was used, what happened and what destination was expected. That gives the correction a clear task.

Check a phone and a reply as well.

Read the test in the inboxes and screen sizes the team actually uses. On a phone, look for awkward wrapping, tiny contact text or a layout that needs sideways scrolling. Check the space between the end of the message and the signature. Compare a new message with a short reply, where a large sign-off may feel different beneath only one sentence.

Review what remains understandable when an image is unavailable. Ask whether the important contact information is still present as readable text, rather than assuming that the logo or portrait will explain it. Treat this as a test of the actual received email, not a promise that one preview represents every recipient’s setup. Record the environments you checked and anything that still needs a separate test.

Keep one current version and retest changes.

Once the agreed checks are complete, keep the current signature source and a short setup note together. Record which mailbox or sender it belongs to, where its images come from and who can update its details. Separate the current version from older exports so someone setting up a second device can find the intended starting point.

A change to a website address, role, logo or contact route is a reason to repeat the relevant checks. Paste the revised signature into the intended editor, send another controlled test and follow the links again. The practical finish is a readable sign-off that behaves as expected in the tested workflow, with any untested environments clearly recorded. Keep the review modest enough that it is easy to repeat when the details change.

Keep a good idea going.

All field notes →
Websites · 4 min read

Choose website images with their placement in mind.

Review the picture inside its intended layout, with the real words and a phone view, before treating an attractive image as the right fit.

Read the field note
Design · 4 min read

Give each approved design variation a clear use.

Connect the variations in your identity set to real placements, then record where a new format still needs its own review.

Read the field note