Email marketing management

Management is the calendar plus the brakes

Email marketing management is the boring system that keeps a program from depending on whoever remembers. It is a calendar of what sends when, a list of who may approve, a QA pass that happens even when the campaign is 'just a GIF,' and a written path for what you do after a bad send. Tools do not provide this. A shared doc and a stubborn habit do. A hub such as HubSpot can hold the calendar. It will not invent the habit.

Without it, two teams book the same Friday, sales pastes a file into a blast, and nobody notices the footer still has last year's address. With it, you still make mistakes. You make fewer public ones.

A week that can repeat

Pick a planning day. Look at launches, shipping promises, webinars, and billing dates so email does not collide with a downtime notice. Slot campaigns. Protect transactional mail from promotional creative. Write freeze windows (for example, no experiments during a site migration). Put owner names on each send, not a team name.

Mid-week is for building and testing. Send day is for the checklist, not for rewriting the offer. After send, someone watches bounces and replies for an hour. If that person is on holiday, the send does not go. 'We will monitor it from the airport' is how incidents start.

QA that is written down

Click every link in a preview that is not your own laptop. Send tests to Gmail, Outlook, and Apple Mail. Check dark mode. Check the from-name and reply-to. Check that the audience excluded unsubscribes, recent complainers, and the segment that already got a similar mail. Check that merge fields have fallbacks so nobody sees *|FNAME|*.

Legal looks at claims and required footer lines. Someone who did not write the email reads the first screen out loud. If they cannot tell what to do, it is not ready. Screenshots of the approved version go in the ticket so a last-minute 'tweak' is visible.

• Audience: inclusion, exclusion, count sanity-check against last send
• Content: links, images alt text, plain-text part, unsubscribe
• Identity: from, reply-to, authenticated domain
• Stop conditions: who can pause, and how fast

Access, vendors, and incidents

Limit who can export the list and who can hit send. Shared logins are how ex-contractors still have your audience. Use SSO if the ESP offers it. Agencies need a role, an end date, and a rule that the client owns the account. If the agency built the audience in their reseller portal, you do not have a program. You have a hostage.

When a bad email goes out, pause the campaign, send a correction only if the error is factual and harmful, and tell support what people will reply. Do not send a second joke email about the mistake unless you are sure the list still likes you. Log the cause (wrong segment, bad merge, leftover test link) and change the checklist. Management is that change, not the apology.