Email Cadence Basics: Timing, Purpose and Stop Rules

A cadence is a planned series of messages tied to one purpose and one audience. It is not a license to keep contacting someone until they answer. The useful design question is what new value each step adds, and what signal should end the sequence.

A practical way to apply it

Choose a finite number of touches, a minimum gap, permitted weekdays and a local sending window. Set an entry reason, owner and stop conditions before drafting. Leave enough time for a person to reply and for the team to act on that reply.

Before using the pattern

Start with the event that makes a message relevant, then decide what each later step contributes. A simple review sheet can list entry event, delay, message purpose, owner and exit event. Check that two active cadences cannot contact the same person about unrelated topics at once.

A worked example

For example, a consultant who receives a request could reply on day one, send one useful checklist several days later, then close the loop with a brief note. A reply, unsubscribe, invalid address or changed business context ends or routes the sequence.

Common mistakes to avoid

Avoid adding steps just to increase activity. Revisit the audience and the reason for contact instead. Record why a person entered and which event ended the cadence; this makes later review possible. A relevant message and a clear exit are more useful than an arbitrary high volume.