Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Templates

Nurture Sequence Plan Template

A lead nurture sequence plan template: stage and goal, entry trigger and conditions, exits, re-entry, messages and timing, hand-off to sales and measures.
Templateintermediate11 min readUpdated

What this template is for

Write one plan for each nurture sequence in a business-to-business or considered-purchase programme, before the workflow is built, and revise it whenever the sequence changes. A sequence in this sense is a workflow with one goal for leads at one stage: problem-aware leads who downloaded an explainer, solution-aware leads comparing options, evaluating leads who stalled, or leads sales returned as not yet ready. The first-contact flow after a sign-up is a different job, and the welcome series tutorial ends in its own template for it.

The plan sits between other documents. The nurture sequences guide explains goals by stage, entry, exit and re-entry rules, content, timing, sales involvement and measurement, and asks for the rules to be written in plain language next to the workflow; this plan is that writing. The lead scoring model template sets the points and thresholds the plan refers to, and the inbound lead handling playbook runs what happens once a lead reaches sales. The email marketing calendar schedules campaign sends that compete for the same inbox. After the build, the email automation flow launch checklist checks the built flow, including every branch, before it is switched on. The plan does not replace any of them; it is the per-sequence page that says what the workflow is meant to do.

Writing it first has a practical point. When qualified leads rarely survive the first sales conversation, the diagnosis of MQLs not converting to SQLs lists no nurture for genuinely early leads among the causes, and asks for stage-based nurture with an observable exit event. A plan that cannot name its goal event or its exits is not ready to build. A sequence already running without them is the first thing the diagnosis for leads stalling in a nurture sequence checks before it reads the content, the hand-off threshold and who was let in.

The template

Copy the table into the workflow's description field, a page linked from it, or the team's automation inventory, and keep the field names so every sequence's plan reads the same way.

FieldWhat to write
Stage and goalThe stage of the buying journey the sequence serves and the observable action that counts as progress
Entry trigger and conditionsThe event that puts a lead in, and the gates such as consent, not a customer and no open opportunity
ExitsThe goal event, disqualifying events and higher-priority workflows that take a lead out before the series ends
Re-entry ruleWhether a lead can enter again, after what interval or into which shorter variant, and who decides
Messages and timingEach message with its job, the content it carries, its channel and when it is sent
Consent and frequencyThe consent each channel relies on and how the sequence fits within the frequency promised to the lead
Score and hand-offHow actions in the sequence change the lead score and the point at which the lead goes to sales
Sales involvementWhat sales sees while the lead is in the sequence and what it does when the lead is handed over
Measures and holdoutProgression to the next stage against a group held out of the sequence, and the date results are read
Owner and reviewThe sequence owner, where the rules are written beside the workflow and when the sequence is reviewed

Use the workflow's name from the naming convention as the plan's title, so the plan and the workflow can be found from each other.

How to fill each section

Stage and goal

Name the stage the sequence serves and one goal the system can observe. The nurture sequences guide tabulates stages from problem-aware to customer, the question a lead has at each and the kind of observable goal that fits: "views pricing or requests a demo", not "educate the lead". If the team plans in top, middle and bottom of the funnel, the TOFU, MOFU, BOFU framework maps onto the same stages. One sequence, one goal; a sequence with two goals is two sequences.

Entry trigger and conditions

Write the trigger, the event that shows the lead is at this stage, and every gate: consent recorded for the channel, not a customer, no open opportunity, not in a higher-priority sequence, not recently contacted by sales. The nurture sequences guide notes that most nurture failures are entry failures. Write each gate as the field and value the platform will check, so the builder does not have to interpret it.

Exits

List the exits in order: the goal event first, then disqualifying events such as an unsubscribe, a bounce, a reply asking to stop, a closed-lost deal or a salesperson taking the record, then the higher-priority workflows that pull a lead out. Say what happens to a lead that reaches the end without progressing. The automation governance guide adds the rails every workflow shares: the global Suppression List checked before every send and the customer and pipeline suppression conditions. Name them here so the plan shows the sequence uses them rather than its own copies.

Re-entry rule

Decide whether a lead that has been through the sequence may enter again, and how: after a minimum interval, into a shorter variant, or only on a person's decision. The nurture sequences guide asks that the platform's re-enrolment setting be chosen deliberately rather than left at its default. Write the interval as the business's own choice and name who decides exceptions.

Messages and timing

One row per message: its job, the content it carries, the channel and when it sends relative to entry or the previous step. Choose content by the question the lead has now; the B2B content guide sets out content by role and stage and the proof business buyers look for, and the nurture guide's test applies to every row: if the lead reads this and nothing else, are they closer to the goal? Mark any step that is a personal note or a task for a salesperson, and record branches by industry, role or interest as their own rows.

Name the consent each channel relies on and where it is recorded. The list building and consent guide summarises how the GDPR describes consent and how the ICO's direct marketing guidance explains the UK's rules on electronic marketing, including the way to opt out that every message must offer; an unsubscribe is an exit. Then say how the sequence fits within the frequency the lead was promised at sign-up and the global cap and workflow priority that the governance guide sets. This is general direction, not legal advice.

Score and hand-off

Write which actions in the sequence change the lead score, referring to the rules in the scoring model rather than copying points, and the point at which the lead leaves nurture for sales: a threshold that makes it an MQL, or a declared action such as a demo request that routes it immediately. The lead scoring guide explains thresholds, negative scoring and the automatic hand-off on a declared action; the lead scoring model template holds the values.

Sales involvement

Say what sales can see while the lead is in the sequence, any human step inside it, and what sales does at hand-off: the response expected, how a lead is accepted as a Sales-Qualified Lead or returned with a reason, and what happens to returned leads. The sales and marketing alignment guide puts these commitments in the service-level agreement; the plan refers to it and records anything specific to this sequence, such as who sends a personal note.

Measures and holdout

Write the measure, progression to the goal within a defined window, and the comparison: a random group of eligible leads held out of the sequence and read over the same window. The email metrics and testing guide explains how a Holdout Group is drawn at entry, kept out of the flow but not out of everything else, and read as a rate per entrant. Add time to goal and the downstream acceptance rate, and name the date results are read and who reads them. Step-level clicks and unsubscribes are for editing the sequence, not for judging it.

Owner and review

Name one owner, a deputy and where the plan is kept beside the workflow. The automation governance guide defines ownership as a person, not a team, responsible for the purpose being true, the measure being reported and the workflow being retired when its job is done, and sets the change control a sequence edit goes through. Write the review date, and review the plan with the scoring calibration so both change together.

Filled example

Below, the plan is completed for an invented business. The names, figures and dates are illustrative.

Illustrative example — not a real result

Yuldracet Payroll Services plans a solution-aware sequence

Yuldracet Payroll Services is an invented payroll bureau for small employers. Its marketing manager wrote this plan for leads who download its guide to changing payroll provider, before the workflow was built.

FieldYuldracet's plan
Stage and goalSolution-aware: the lead knows it may outsource payroll and is weighing providers. Goal: books a call with an adviser or views the pricing page twice within 30 days
Entry trigger and conditionsTrigger: downloads "Changing payroll provider: a guide". Gates: email consent recorded; lifecycle stage not "customer"; no open opportunity; not in the evaluating sequence; no sales activity logged in the last 14 days
Exits(1) Goal event: books a call, or second pricing-page view; moves to the evaluating sequence or to sales. (2) Unsubscribe, hard bounce, reply asking to stop, deal closed-lost, a salesperson takes ownership. (3) A demo request or the "talk to us" form, which starts the hand-off workflow. Leads reaching the end without progressing return to the monthly newsletter
Re-entry ruleMay re-enter once, no sooner than 120 days after leaving, into a shorter three-step variant. Anything else is the marketing manager's decision
Messages and timing(1) Day 0, email: deliver the guide and one question about current payroll size. (2) Day 3, email: checklist of what to ask a new provider. (3) Day 8, email: case study of a 40-employee café group that switched mid-year. (4) Day 14, email: what switching involves, step by step, with honest timings and who it suits less well. (5) Day 21, plain-text email from a named adviser asking one question, sent as a task the adviser approves. (6) Day 28, email: pricing explained, with a link to the calculator
Consent and frequencyEmail only, on recorded consent from the download form, which promised "the guide and a few emails about switching provider". Each email carries the unsubscribe link. Global cap of 2 marketing emails a week applies; this sequence ranks above the newsletter, which is held while a lead is in it
Score and hand-offClicks on steps 3, 4 and 6 add intent points as set in the scoring model; pricing views add more. Hand-off at the scoring model's MQL threshold, or immediately on a call booking or demo request
Sales involvementAdvisers see sequence membership and step on the CRM record. Step 5 is written and sent by the assigned adviser. On hand-off, the adviser contacts the lead within the service-level window, accepts or returns it with a reason code; returned leads with the code "too early" wait 60 days, then may re-enter as above
Measures and holdout10% of eligible leads held out at entry, at random. Measure: share reaching the goal within 30 days, enrolled against holdout; time to goal; share of progressed leads accepted by advisers. First read 30 June by the marketing manager, with the sales lead
Owner and reviewOwner: marketing manager; deputy: marketing executive. Plan linked from the workflow description; workflow named "LM_EM_SolutionAware_SwitchGuide_Live". Reviewed each quarter with the scoring calibration

At the first read, 23% of enrolled leads had reached the goal against 13% of the holdout, and advisers accepted most of the leads handed over. Step 2 had the fewest clicks and two unsubscribes, so the marketing manager replaced it with a short comparison of in-house and outsourced payroll and noted the change and its date in the plan.

Common mistakes

  • A goal nobody can observe. "Build trust" cannot end a sequence. Write the event the system can see.
  • Entry without gates. A sequence that only checks the trigger enrols customers and leads already talking to sales. Write every gate as a field and value.
  • The end of the series as the only exit. A lead that books a call on the second message should not get the remaining four. List the goal event and disqualifiers first.
  • Re-enrolment left at the default. Leads loop, and the default may send the same messages again word for word. Decide the rule.
  • Points copied into the plan. Scores copied from the model go stale the first time it is recalibrated. Refer to the model.
  • Sales told afterwards. A hand-off nobody agreed to receive has no urgency. Agree what sales sees and does before the sequence is built.
  • Judging the sequence on opens and clicks. Engagement shows which steps to edit. Progression against a holdout shows whether the sequence works.
  • No owner beside the workflow. A plan kept in someone's drive leaves with them. Link it from the workflow and name an owner and a deputy.

The scoring model the plan refers to and the calendar for campaign sends that share the inbox are in the templates library.

Frequently asked questions

Why write a plan for each sequence rather than one for the whole nurture programme?

Because each sequence has its own goal, entry rules, exits and re-entry rule, and those are the parts a new owner most needs and most often cannot find. The site's nurture sequences guide asks for these rules to be written in plain language next to the workflow. A programme-level view still matters, for frequency and priority between workflows, but it lives in automation governance; the plan here is per sequence and points to those shared rules rather than restating them.

How is the nurture sequence plan different from the lead scoring model?

The lead scoring model sets the points, decay and thresholds for every lead. The nurture plan records how one sequence uses them: which actions inside the sequence change the score, which threshold or declared action ends the sequence and hands the lead to sales, and what happens if sales returns the lead. Keep the numbers in the scoring model and refer to them from the plan, so that a change to the model does not leave old values in a plan.

What does the plan need to say about consent?

The channels the sequence uses and the consent each relies on, as the site's list building and consent guide describes it from the ICO's direct marketing guidance: marketing messages go only where consent or the rules allow, every message offers a way to opt out, and an unsubscribe ends them. The plan also says how the sequence fits within the frequency promised to the lead at sign-up. This is general direction, not legal advice, and rules differ between markets.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Direct marketing guidance — Information Commissioner's Office (UK)

Related