# Nurture Sequence Content Map

Connect a sequence of permission-based messages to recipients’ changing questions, readiness, evidence needs, choices, pauses, exits, and handoffs.

## Usage note

Use this map only for recipients the organization may contact and give every sequence a clear exit, suppression, and preference path. A nurture program should support a decision without pretending that every person moves through identical stages. Do not increase frequency simply because someone has not taken the desired action.

## How to use this template

1. Define lawful entry, recipient situation, desired supported decision, exclusions, and completion or exit events.
2. List changing questions and evidence needs without assuming one linear path for everyone.
3. Give each message one reader-centered job, verified claim set, choice, and appropriate next action.
4. Configure timing, branching, frequency, suppression, reply handling, preferences, and human handoffs.
5. Test the sequence end to end, monitor suitable outcomes and harm signals, and assign ongoing source and automation owners.

## Blank template

### Sequence foundation

- **Sequence name:** [Internal name]
- **Entry event:** [Observable and permitted trigger]
- **Recipient situation:** [What is happening?]
- **Contact basis and preferences:** [Approved record]
- **Decision supported:** [What may the person choose?]
- **Completion event:** [When the sequence stops]
- **Exclusions:** [Who should not enter]
- **Sequence owner:** [Accountable role]

### Message record

- **Message number or branch:** [Identifier]
- **Recipient question now:** [Need at this moment]
- **Message job:** [Orient / Explain / Prove / Compare / Invite / Confirm / Handoff]
- **Core content:** [Minimum useful information]
- **Claim sources:** [Links and owners]
- **Limitation:** [Condition that must be visible]
- **Primary action:** [Specific and optional where appropriate]
- **Alternative choice:** [Wait, decline, ask, or another]
- **Send trigger:** [Event and delay]

### Branching and safeguards

- **If completed:** [Suppress or confirmation path]
- **If inactive:** [Pause, stop, or useful follow-up]
- **If replied:** [Human route and response target]
- **If support issue appears:** [Remove from sales flow and route]
- **Frequency cap:** [Rule]
- **Collision rule:** [Other campaigns or operational emails]
- [ ] Unsubscribe and preferences work where required.
- [ ] Essential facts are not withheld for later messages.
- [ ] A non-purchase or non-action path remains clear.

### Measurement and maintenance

- **Useful outcome:** [Appropriate decision or completed task]
- **Guardrails:** [Complaints, opt-outs, support confusion, unsuitable conversion]
- **Automation test:** [Entry, branch, suppression, and exit]
- **Fact owner:** [Role]
- **Reply owner:** [Role]
- **Review trigger:** [Product, price, policy, or evidence change]
- **Next review:** [YYYY-MM-DD]