Set a Rule for Capitalization and Punctuation in Email Addresses

Separate address formatting from address selection

A naming convention decides how an address is formed—for example, whether it uses a person's name or a team name. A formatting policy decides how the chosen address is displayed and recorded. Keep those decisions separate. If your current convention already determines the address, this policy should standardize its written form rather than create a second formula.

This distinction matters when someone spots a difference such as capital letters or a missing dot. The formatting rule can tell them how to record an address, but it cannot establish that two spellings deliver to the same mailbox. Treat the actual address assigned to the person or team as authoritative.

Use lowercase as the written standard

Adopt lowercase letters for email addresses in your directory, internal documents, contact lists, and new correspondence. Lowercase is easy to read consistently and avoids making capitalization look like a meaningful distinction. When staff copy an address from an existing record, they should use the approved lowercase version.

Do not rely on a mail provider to treat differently capitalized versions as interchangeable. Systems and address handling can vary, and the record should match the address your organization actually uses. If an address was originally created with uppercase characters, confirm the correct address with an administrator or the mailbox owner before editing records. Lowercasing a written copy is not permission to rename an account.

Make punctuation deliberate

Specify that punctuation is included only when it is part of the assigned address. Do not add or remove dots, hyphens, underscores, or other characters to make an address look neater. Do not assume that a punctuation change is merely a formatting variant: it may identify a different address, or it may not work at all.

When entering an address into a form or contact record, compare it with an authoritative source, such as the mailbox owner's confirmed address or an approved directory. If a system rejects an address, check for a typing error rather than trying punctuation alternatives. Keep the exact assigned spelling in the record, even when your organization displays names in a separate, more reader-friendly format.

Define a small, controlled exception process

Some records may need to preserve a legacy address, a previously published contact, or another address that cannot be changed immediately. Handle these as explicit exceptions, not as permission for each person to choose their preferred capitalization or punctuation. Record the exact address, why it must remain, who confirmed it, and who should review the exception.

Do not create exceptions for visual preference alone. If an address appears to be wrong, ask its owner or the authorized administrator to confirm it before updating shared records. Changes to mailbox addresses, account access, or domain settings should be made only by someone with the appropriate role and permissions. This policy governs how staff document addresses; it does not grant authority to alter accounts.

Apply the rule without rewriting your naming convention

Tell staff to preserve the established address itself while using lowercase in records and keeping every required punctuation mark. For existing entries, correct only clear presentation inconsistencies after checking the authoritative address. Avoid bulk changes based on assumptions, especially where an address is used in forms, customer records, or saved contacts.

For example, if the confirmed address is [jane.doe@example.com], record it in lowercase exactly that way. Do not change it to [janedoe@example.com] or [jane-doe@example.com] because those versions look simpler. If a system or old document shows [Jane.Doe@example.com], verify the assigned address before standardizing the record.

Policy note
Write addresses in lowercase. Preserve punctuation exactly as assigned. Do not assume alternate spellings reach the same mailbox. For a legacy or otherwise necessary exception, record the confirmed address and the reason it remains in use.

Confirmed address: [jane.doe@example.com]
Use in records: [jane.doe@example.com]
Do not substitute: [janedoe@example.com]

Check that the policy is working

A short review can reveal whether the rule is understandable. Ask a colleague to compare a few records with their authoritative source and identify any capitalization or punctuation mismatch. Check that exceptions are labeled and that staff know whom to ask when an address is uncertain. Correct confirmed record errors, then share the standard with people who create or maintain contact data.

Use this checklist when adding or reviewing an address:

• Is the written address lowercase?
• Does every punctuation mark match the confirmed address?
• Was the address checked rather than inferred from a similar one?
• If it differs from the standard, is the exception documented?
• Did the record save the intended address without an unintended edit?