Learning path · Level 10 · Tutorial 4

Present and Defend Your Marketing Plan

Assemble the completed marketing plan and communicate it through a concise written or spoken pitch. Rehearse responses to text-based stakeholder challenges, then improve the plan with a structured self-review; no live audience, recording, or file submission is required.

  • Level: Advanced
  • Duration: 25 min
  • 8 steps
Start tutorial Back to the path
Present and Defend Your Marketing Plan

What you will go through

  1. Consolidate Your Existing Plan 4 min
  2. Lead with an Executive Recommendation Lead with a concise executive recommendation grounded in the learner’s consolidated Working plan. 3 min
  3. Structure a Three-Minute Pitch Turn your executive recommendation into a concise, timed decision story while keeping detailed support in your Working plan. 4 min
  4. Defend the Reasoning, Not the Certainty Respond to a stakeholder challenge with traceable reasoning, calibrated uncertainty, and a bounded decision request. 3 min
  5. Rehearse Three Stakeholder Challenges Rehearse concise, evidence-grounded responses to three independent stakeholder challenges affecting your existing marketing plan. 4 min
  6. Score the Plan's Readiness Use a six-criterion rubric to identify the most consequential weakness in your Working plan before making a material revision. 3 min
  7. Make and Trace a Material Revision Correct one substantive weakness, propagate the change through your plan, and keep the revised decision request honest about remaining uncertainty. 3 min
  8. Present, Defend, and Close Integrate your revised plan into one final delivery, defend a stakeholder challenge, and record a justified readiness verdict. 4 min

What you will learn

  • Consolidate the strategic core, channel decisions, execution roadmap, budget scenarios, and measurement framework into one internally consistent plan.
  • Write an executive summary and deliver a three-minute spoken pitch or concise written equivalent that states the recommendation, expected outcomes, key risks, and requested decision.
  • Respond to scenario challenges such as reduced capacity, weaker conversion, or unavailable tracking, defending assumptions without overstating certainty.
  • Score the plan using a self-review rubric covering evidence, cross-channel coherence, feasibility, forecast assumptions, decision rules, and consent safeguards.
  • Revise a material weakness and record how the correction affects dependent activities, resources, assumptions, or measurement decisions.

Before you start

  • Connect Channels in an Integrated Marketing Plan
  • Build a Capacity-Aware Marketing Roadmap
  • Set Decision Rules for Measurement and Experiments

Step 1 of 8

Consolidate Your Existing Plan

Assemble the same plan

One case, one Working plan

Build one stakeholder-facing Working plan from the same business case you developed in the preceding tutorials. Do not begin a new case or replace your business, audience, offer, objectives, planning horizon, currency, units, or numeric baselines.

Use your saved plain-text artifacts first. Consolidation means that every section tells the same operational story: chosen channels support the objective, the roadmap fits capacity, spending matches the scenario, forecasts retain their conditions, and measurement rules use data that consent and access conditions permit.

Apply Evidence, Assumption, Forecast, and Unknown to individual claims—not to an entire section. A recorded channel choice or commitment is not automatically Evidence merely because it appears in the plan. Missing material remains Unknown; do not invent research sources, historical results, or precision.

See the plan as a linked system

A central plan folder connects to eight visual panels representing strategy, channels, roadmap, resources, forecasts, measurement, consent, and experiments.

Treat the eight sections as connected commitments, not as separate documents. Trace each material claim to the section that supports it before presenting it.

Recover only what you can trace

Same-case recovery packet

If an artifact is missing, use this compact Same-case recovery packet. It preserves your original case identity; it does not create replacement facts. Reconstruct only what you can support from your own notes or prior work. Mark a provisional reconstruction Assumption, a projected result Forecast, and an unavailable fact Unknown.

Keep cash values in your plan’s original currency, such as USD 1,250.50, and keep percentages and baselines unchanged. Record the section reference beside claims that depend on another section.

Eight required sections

Use these prompts only for sections that are missing or incomplete. Keep recovered entries short and traceable.

Same-case recovery prompts for your Working plan
Plan sectionRecovery prompt
Strategic coreBusiness, audience, offer, objective, and planning horizon. Mark missing support Unknown.
Channel decisionsIncluded, deferred, or excluded channels; each role and handoff.
Execution roadmapPhases, readiness gates, owners, approvals, and dependent work.
Resources and budget scenariosCash spending and staff capacity in original units; scenario limits.
Forecast assumptionsInputs, conditions, conversion or timing assumptions, and review point.
Measurement and decision rulesOutcome, source, observation window, data checks, owner, and action rule.
Consent safeguardsPermitted data use, access conditions, restrictions, fallback, and decision limits.
Experiment prioritiesUnresolved assumption, pending decision, dependencies, and priority order.

Find the mismatch or dependency

Check links, then feasibility

Run a consistency check after packaging. First, check links: every channel and experiment should serve a stated objective, and every forecast or decision rule should point to its assumptions and permitted data. Then check feasibility: dates, staff hours, approvals, cash spending, and measurement access must coexist.

An inconsistency is a direct mismatch—for example, a roadmap commitment that exceeds available staff capacity. An unresolved dependency is a condition that prevents a commitment or decision from being reliable—for example, required measurement access not yet confirmed. Do not hide either one: correct it now or state the condition required before approval.

High-value cross-checks

Use this cross-check before you call the package complete.

Compare connected sections rather than reviewing each section in isolation.
CheckCompareQuestion to resolve
Purpose and scopeStrategic core + Channel decisionsDoes every selected channel have a role tied to an objective?
Delivery capacityExecution roadmap + Resources and budget scenariosDo timing, ownership, approvals, staff capacity, and cash fit together?
Conditional outcomeResources and budget scenarios + Forecast assumptionsDo forecast inputs match the selected scenario and original baselines?
Permitted decisionsMeasurement and decision rules + Consent safeguardsCan the stated data source legally and practically support this decision?
Learning sequenceExperiment priorities + Execution roadmapCan each experiment run after dependencies are ready and inform a pending decision?

Example

Make an uncertainty actionable

A concise issue record can use this pattern:

Unknown — [Plan: Consent safeguards] does not confirm whether the planned source is available. Therefore [Plan: Measurement and decision rules] cannot use that source for its stated decision. Condition before approval: confirm permitted access or limit the decision to the available measures.

Replace the bracketed sections and condition with your own plan details. This is not a new claim; it makes the dependency visible.

Record your plan audit

Audit your Working plan

Create a compact audit of your Working plan.

  1. On separate lines, account for all eight headings: Strategic core, Channel decisions, Execution roadmap, Resources and budget scenarios, Forecast assumptions, Measurement and decision rules, Consent safeguards, and Experiment priorities. Mark each section Complete or Incomplete. For each section, name one key claim and label that claim as Evidence, Assumption, Forecast, or Unknown, with an internal reference such as [Plan: Channel decisions]. You may add more labels when the section contains materially different claims.
  2. Identify one concrete inconsistency or unresolved dependency spanning at least two sections.
  3. State either the specific correction you will make now or the condition required before approval.

Keep the original case identity and numeric baselines intact. A section’s completeness does not make every claim inside it Evidence.

Write at least 450 characters (0/450).

Step 2 of 8

Lead with an Executive Recommendation

Lead with a concise executive recommendation grounded in the learner’s consolidated Working plan.

Turn the plan into a decision brief

A recommendation first

An executive summary is a decision brief, not a compressed list of tactics. A stakeholder should be able to identify the recommendation and the decision requested in the first sentence.

Draft from your Working plan in this order:

  1. Recommendation and customer opportunity — [Plan: Strategic core]
  2. Coordinated response — [Plan: Channel decisions]
  3. Expected outcome, clearly labeled Forecast — [Plan: Forecast assumptions]
  4. Resource commitment — [Plan: Resources and budget scenarios]
  5. Material risk, Assumption, or Unknown that could change the decision — [Plan: Measurement and decision rules] or [Plan: Consent safeguards]
  6. A bounded decision requested.

Use only decision-relevant detail. Keep an Evidence claim traceable, keep a Forecast conditional, and do not hide an Unknown that would materially affect approval.

From activities to a decision

A comparison between a scattered activity list and a connected decision brief for the same marketing plan.

The decision-led version connects activities to an outcome, resources, a qualification, and an approval; it does not merely name channels.

Build a traceable summary

Bound the approval

A bounded approval request specifies all three boundaries:

  • What: the recommended coordinated response or named phase.
  • Period: the phase or planning horizon being authorized.
  • Conditions: the decision rules, consent limits, or evidence checks that can change the next action.

Use this drafting pattern, replacing every bracket with information from your plan:

“Recommend approval of [scope] for [period] to address [customer opportunity]. The coordinated response is [response]. Forecast [expected outcome], subject to [material assumption or risk]. This requires [cash and/or staff commitment]. Decision requested: approve [scope] under [named condition].”

Do not convert a qualification into certainty. For example, attach an outcome to its Forecast assumptions rather than presenting it as a guaranteed result.

Example

Keep qualifications decision-relevant

Before drafting, make a short claim map:

| Summary element | What to verify in your Working plan |
|---|---|
| Opportunity | Evidence in Strategic core |
| Response | Included channels and handoffs in Channel decisions |
| Outcome | Forecast and conditions in Forecast assumptions |
| Resources | Cash and staff capacity in Resources and budget scenarios |
| Qualification | Assumption or Unknown in Measurement and decision rules or Consent safeguards |
| Approval | Scope, period, and condition in Execution roadmap |

This map is preparation, not extra prose. Your final executive summary must be 80–120 words.

Recognize a decision-ready recommendation

Choose the stronger opening

Which opening is decision-ready for your plan?

Select the opening that best serves an executive summary.

Write your summary

Draft your executive recommendation

Write an 80–120-word executive summary for your Working plan. Lead with your recommendation. Include: the customer opportunity; the coordinated response; one expected outcome labeled or clearly qualified as a Forecast; the cash and/or staff resource commitment; one material Assumption, Unknown, risk, or consent condition; and an explicit decision requested stating what is authorized, for which phase or period, and under what condition.

Use your existing business case and preserve its original currency, units, baselines, and planning horizon. Add plan references in the form [Plan: Forecast assumptions] where they help trace a central claim.

Write at least 400 characters (0/400).

Step 3 of 8

Structure a Three-Minute Pitch

Turn your executive recommendation into a concise, timed decision story while keeping detailed support in your Working plan.

Tell one decision story

One story, one decision

Your executive summary states the recommendation. Your pitch now carries one decision story: it gives stakeholders just enough to approve, conditionally approve, or defer that recommendation.

Use six connected parts:

  1. Customer opportunity
  2. Coordinated response
  3. Expected outcomes
  4. Resource request
  5. Risks and controls
  6. Decision requested

Keep each part anchored in your Working plan. The pitch explains the decision; it does not recite every activity, channel metric, or planning note.

The six-part pitch flow

A six-segment timeline moves from customer opportunity through coordinated response, outcomes, resources, risks, and a final approval decision.

Use this order to move from why action matters to the specific decision requested.

Three-minute timing map

Use these elapsed ranges as a disciplined outline:

  • 0:00–0:30 — customer opportunity
  • 0:30–1:15 — coordinated response
  • 1:15–1:45 — expected outcomes
  • 1:45–2:15 — resource request
  • 2:15–2:45 — risks and controls
  • 2:45–3:00 — decision requested

The longer response segment explains how the chosen channels work together. The final 15 seconds must name the decision requested, rather than ending with a general invitation for questions.

Use layers and qualified figures

Keep detail available, not crowded

Layer your communication. The pitch carries the recommendation and only the figures that change the decision. Your Working plan retains the detail that makes those claims traceable.

For each meaningful figure, attach its condition. For example, describe an expected outcome as a Forecast that depends on stated assumptions, timing, and measurement limits—not as a guaranteed result. Identify retained facts as Evidence, provisional inputs as Assumption, and unresolved information as Unknown.

Do not add together channel-attributed outcomes as though they were automatically unique business outcomes. Point stakeholders to the relevant plan section when they need the method, baseline, or decision rule.

Pitch layer and support layer

Use the pitch to name the point; use the plan to support it.

Named sections let stakeholders inspect detail without interrupting the main story.
Pitch layerSupporting detailPlan section
Customer need and recommendationAudience evidence and chosen offerStrategic core
How channels work togetherHandoffs, inclusions, and exclusionsChannel decisions
What will happen and whenOwners, gates, and dependenciesExecution roadmap
What is requestedCash and staff-time scenariosResources and budget scenarios
What outcome is expectedInputs, horizon, and conditionsForecast assumptions
How adaptation will occurReview cadence, thresholds, and limitsMeasurement and decision rules
How data use is boundedPermissions and fallback limitsConsent safeguards
What will be tested firstDecision value and dependenciesExperiment priorities

Tip

Figure-selection rule

Before drafting, choose a small number of decision-relevant figures from your plan. A figure belongs in the pitch only if it clarifies the expected outcome, resource request, material risk, or decision requested. Keep its currency, units, numeric baseline, and condition exactly as recorded in your plan.

Check the narrative order

Sequence the pitch

Put the six pitch parts into the order that creates a decision-oriented three-minute story.

  1. Decision requested
  2. Resource request
  3. Expected outcomes
  4. Risks and controls
  5. Customer opportunity
  6. Coordinated response

Create your pitch draft

Draft your three-minute pitch

Draft your pitch using your current Working plan—not a new business case.

Choose one route:

  • Spoken-pitch outline: write six timed blocks for 0:00–0:30, 0:30–1:15, 1:15–1:45, 1:45–2:15, 2:15–2:45, and 2:45–3:00. Read it aloud with your own timer; no recording or audience is needed.
  • Written equivalent: write 350–400 words in the same six-part order.

In either route, state an explicit recommendation, a conditional expected outcome labeled Forecast, one material risk and its control, and a specific decision requested. Attach conditions to figures and direct supporting detail to named sections, for example [Plan: Forecast assumptions]. Keep Evidence, Assumption, Forecast, and Unknown distinct.

Step 4 of 8

Defend the Reasoning, Not the Certainty

Respond to a stakeholder challenge with traceable reasoning, calibrated uncertainty, and a bounded decision request.

Frame a defensible response

Calibrate the claim

A stakeholder challenge tests the reasoning behind your Working plan; it does not require certainty. Calibrate each claim before responding:

  • Evidence: a retained, traceable fact in your plan.
  • Assumption: an input that must hold for a commitment to work.
  • Forecast: a conditional estimate, not a promise.
  • Unknown: information the plan does not yet establish.

Use a specific section reference, such as [Plan: Forecast assumptions], rather than confidence or vague authority. A valid challenge may change a tactic, scope, or assumption without changing the strategic priority.

A bounded defense flow

A four-stage flow showing Position, Basis, Implication, and Decision, moving from recommendation to evidence, consequence, and requested approval.

Use Position → Basis → Implication → Decision to make a concise response without turning a conditional plan into a guarantee.

Name the limit and the next decision

Four claim labels

Choose the label from what your Working plan can support—not from how confident the sentence sounds. A useful response names the limit and then states what should happen next.

Claim calibration guide

Use these labels to keep a defense precise.

Each claim should point to the plan section that can substantiate or qualify it.
LabelWhat it meansUseful defense language
EvidenceA documented plan fact“The plan records … [Plan: Strategic core]”
AssumptionA condition used to make the plan feasible“This depends on … [Plan: Resources and budget scenarios]”
ForecastA conditional projected outcome“This estimate holds if … [Plan: Forecast assumptions]”
UnknownA question the plan cannot answer yet“We do not yet know …; the limit is …”

Example

Example: defend the reasoning

A stakeholder challenge says: “Can you promise the planned outcome?”

Position: Proceed with the coordinated priority in the Working plan; do not promise the outcome.

Basis: The projected outcome is a Forecast with stated conditions [Plan: Forecast assumptions].

Implication: If those conditions are not observed during the defined review window, the outcome estimate is less reliable and the activity follows its decision rule [Plan: Measurement and decision rules].

Decision: Approve the planned phase subject to those conditions and review rules.

This acknowledges the challenge while protecting the strategy. The forecast can be qualified; it need not be defended as a fact.

Practice claim calibration

Classify the support

Match each statement to its appropriate claim label.

Tap an item and then its matching pair.

Apply the response structure

Rewrite an overconfident defense

A stakeholder challenge says: “Why should we believe this outcome?” A response currently says: “This plan will deliver its forecast because our channels are coordinated.”

First, label that claim as Evidence, Assumption, Forecast, or Unknown. Then rewrite the response using Position → Basis → Implication → Decision.

Use one exact reference from your Working plan. State one relevant limitation without weakening the strategic priority, and finish with a clear decision implication or decision requested.

Write at least 250 characters (0/250).

Step 5 of 8

Rehearse Three Stakeholder Challenges

Rehearse concise, evidence-grounded responses to three independent stakeholder challenges affecting your existing marketing plan.

Set up the rehearsal

Run independent rehearsals

Treat each challenge as a separate baseline change

Use your plan as it stands now. Do not combine the scenarios or silently replace a baseline. For every response, make a concise four-part case:

  • Position: state the adaptation or boundary.
  • Basis: name the affected Evidence, Assumption, Forecast, or Unknown and cite the relevant plan section, for example [Plan: Forecast assumptions].
  • Implication: identify changed commitments, dependent activities, and what remains strategically protected.
  • Decision: state the revised decision requested—approval, conditional approval, or deferral.

A challenge can justify changing scope, sequence, or a decision limit. It does not prove proportional returns or causality.

Three separate changes to one plan

A plan package branches separately to a reduced-capacity scenario, a lower-conversion scenario, and an unavailable-tracking scenario, each connected to different plan sections.

Keep the baseline plan fixed. Trace each scenario only through the sections it actually affects.

Example

Use the four-part frame

Response frame

Position: [the adaptation or limit]

Basis: [Evidence, Assumption, Forecast, or Unknown + plan-section reference]

Implication: [what changes, what is protected, and which commitments depend on it]

Decision: [the decision requested]

Use only claims that your plan can support. If information is unavailable, name it as Unknown rather than filling the gap with invented results.

Tip

Rehearsal rule

Keep the response short enough to say aloud. Specific plan references make a challenge response more defensible than confidence or extra detail.

Respond to reduced capacity

Challenge 1: Capacity falls

A stakeholder challenge changes staff capacity only: your plan has 25% less staff capacity for the same planning horizon. Cash availability is unchanged.

Write a brief response for your plan using exactly these labels: Position → Basis → Implication → Decision.

Identify the affected claim with Evidence, Assumption, Forecast, or Unknown and a plan reference. State which priority remains protected, which commitments or dependent activities change, and the revised decision requested. Do not claim that reducing effort produces a proportional outcome.

Write at least 280 characters (0/280).

Respond to weaker conversion

Challenge 2: Conversion is weaker

At the planned review, observed conversion is 30% below the rate assumed in your plan. Treat this as an independent change to the baseline.

Write a brief response for your plan using exactly these labels: Position → Basis → Implication → Decision.

Identify the affected claim and cite [Plan: Forecast assumptions] or [Plan: Measurement and decision rules] as appropriate. State what must be checked within the planned observation window and data-quality checks, what forecast or commitment may change, what remains protected, and the revised decision requested. Do not treat the result as proof of a cause.

Write at least 300 characters (0/300).

Respond without bypassing safeguards

Challenge 3: Tracking is unavailable

A planned tracking source becomes unavailable because consent or access conditions are not met. Treat this as an independent change to the baseline.

Write a brief response for your plan using exactly these labels: Position → Basis → Implication → Decision.

Identify the affected claim and cite [Plan: Consent safeguards] and/or [Plan: Measurement and decision rules]. State what can still be measured, which decision must be limited or deferred, what strategic priority remains protected, and the revised decision requested. Do not propose a workaround that bypasses consent or access conditions.

Write at least 300 characters (0/300).

Step 6 of 8

Score the Plan's Readiness

Use a six-criterion rubric to identify the most consequential weakness in your Working plan before making a material revision.

Treat readiness as a whole-plan check

Review the plan behind the pitch

Your executive summary and pitch make a recommendation; the readiness review tests whether the underlying Working plan can support it. Review the whole plan, not just the strongest channel or the polish of the presentation.

For material claims, preserve the labels Evidence, Assumption, Forecast, and Unknown. A score is an honest judgment of readiness—not a reason to relabel an Unknown as Evidence.

The review has six criteria. Each score must point to the plan section that supports the judgment, using a reference such as [Plan: Forecast assumptions].

Six connected readiness checks

A central plan is connected to six symbols representing evidence, channel coherence, feasibility, forecasts, measurement decisions, and consent safeguards.

Score all six connected areas. A weakness in one area can limit the decision readiness of the entire Working plan.

Apply the rubric consistently

Score with anchors, not impressions

Use the shared scale for every criterion: 0 = missing or contradictory, 1 = present but incomplete, and 2 = explicit, consistent, and traceable.

Read the descriptors as anchors, then cite the section that supports your score. Before considering any total, flag a central unsupported claim, an infeasible commitment, or an unresolved consent failure. These can outweigh a high score elsewhere.

For measurement readiness, also ask whether an experiment would inform a real pending decision—not merely produce an interesting result.

Six criteria and scoring anchors

Use the descriptor that best matches the current Working plan. The final self-review will place a [Plan: ...] reference beside every score.

A total can summarize the review, but it cannot cancel a material blocker.
Criterion0 — missing or contradictory1 — present but incomplete2 — explicit, consistent, traceable
Evidence and traceabilityCentral claims lack labels or conflictSome claims have references; key gaps remainMaterial claims are labeled and traceable to plan sections
Cross-channel coherenceOffers, handoffs, or objectives conflictMain channels connect; gaps or duplication remainChannel roles, handoffs, and promises align
FeasibilityCommitments exceed capacity or resourcesResources are outlined; dependencies remain unclearOwners, time, cash, approvals, and dependencies are workable
Forecast assumptionsForecast is unsupported or presented as factSome assumptions or conditions are missingBaselines, units, conditions, and uncertainty are explicit
Measurement and decision rulesNo usable measure, rule, or fallbackMeasures exist; windows, checks, or decisions are incompleteMeasures, checks, fallbacks, and decisions align; experiments inform pending decisions
Consent and responsible executionA required safeguard is absent or contradictedSafeguards exist; access or limits remain unresolvedConsent conditions, access limits, and responsible actions are documented

Choose substance over polish

Prioritize the consequential weakness

Which finding should receive priority as the material weakness?

Run your own readiness review

Score your plan and select the priority weakness

Complete a readiness review of your current Working plan. Write six lines, one for each criterion:

  • Evidence and traceability: 0, 1, or 2 — [Plan: section heading]
  • Cross-channel coherence: 0, 1, or 2 — [Plan: section heading]
  • Feasibility: 0, 1, or 2 — [Plan: section heading]
  • Forecast assumptions: 0, 1, or 2 — [Plan: section heading]
  • Measurement and decision rules: 0, 1, or 2 — [Plan: section heading]
  • Consent and responsible execution: 0, 1, or 2 — [Plan: section heading]

Then name one material weakness to correct and explain why it matters more than a cosmetic improvement. Keep any reconstructed entry labeled as Assumption or Unknown; do not invent support for it.

Write at least 350 characters (0/350).

Step 7 of 8

Make and Trace a Material Revision

Correct one substantive weakness, propagate the change through your plan, and keep the revised decision request honest about remaining uncertainty.

Recognize a material revision

Change commitments, not just wording

A revision is material when it changes a commitment, assumption, dependency, safeguard, or decision. It can change what a stakeholder should approve.

Start with the weakness identified in your self-review or stakeholder challenge. Then create a copy of your Working plan called Revised plan. Do not silently replace the original: the before-and-after trail is evidence of responsible planning.

Changing wording is not a material revision. Changing a channel’s scope because capacity fell, limiting a decision because consent-based tracking is unavailable, or revising a forecast assumption after weaker conversion is material.

Use claim labels precisely: retain Evidence that still supports the plan; identify changed Assumption or Forecast statements; mark anything still unresolved as Unknown.

One correction can propagate

Before-and-after map showing that a consent or measurement correction affects forecasts, channel scope, and decision rules.

Trace every arrow affected by the correction; a plan is consistent only when connected commitments agree.

Tip

Materiality test

A useful test: if the correction could alter resources, timing, expected outcomes, a measurement-based action, or the decision requested, it needs dependency tracing. Cite the supporting location as, for example, [Plan: Measurement and decision rules] rather than claiming certainty without a plan reference.

Write the record and trace dependencies

Revision record

Record the revision in this order. Keep the original business case, currency, units, and numeric baselines; do not fill gaps with invented results.

Weakness → Correction → Dependencies → Recheck

Use this structure for one consequential issue in your plan.

A traceable record links the change to the plan sections it affects.
Record fieldWhat to write
WeaknessThe contradictory, infeasible, unsupported, or unsafe commitment; cite its plan section and claim label.
CorrectionThe specific revised commitment, assumption, safeguard, or decision rule.
DependenciesAt least two affected plan sections and what changes in each: scope, owner, timing, staff hours, cash, forecast, measurement, or experiment.
RecheckAffected rubric criteria, new 0–2 score, supporting section reference, and any remaining Unknown.

Example

Pattern only: record a source-availability correction

Weakness: A planned source cannot be used because its consent or access condition is not met. Unknown: whether an alternative source will become available in time. [Plan: Consent safeguards]

Correction: Limit the related performance decision to the measures that remain permitted and available; do not claim source-level certainty. [Plan: Measurement and decision rules]

Dependencies: Update the affected channel commitment and its review owner; qualify the related forecast rather than treating it as confirmed; reconsider any experiment that depends on the unavailable source.

Recheck: Re-score consent and responsible execution, measurement and decision rules, and any criterion affected by the forecast. The result may support conditional approval rather than full approval.

Align the decision story

Bring the summary, pitch, and rubric forward

Propagation is complete only when the stakeholder-facing story matches the Revised plan.

  1. In the 80–120-word executive summary, replace any recommendation, expected outcome, risk, or decision requested that the correction changes.
  2. In the three-minute pitch—or its 350–400-word written equivalent—replace the affected claim at the relevant moment. State the condition plainly instead of hiding it behind confident language.
  3. Re-score only the affected rubric criteria using the shared scale: 0 = missing or contradictory, 1 = present but incomplete, 2 = explicit, consistent, and traceable. Write a supporting reference beside each score, such as [Plan: Forecast assumptions].

A revision can legitimately end in conditional approval or deferral. State the remaining Unknown, why it matters, and what evidence or authorization would resolve it.

Consistency check

Use this quick cross-check before presenting the revised version.

Each changed statement should lead back to a current plan section.
If you changed…Also check…
Channel scope or commitmentExecution roadmap, resources and budget scenarios, and pitch response
Staff hours, owner, or timingExecution roadmap and resources and budget scenarios
A forecast input or expected outcomeForecast assumptions, executive summary, and pitch
A metric, source, threshold, or limitationMeasurement and decision rules and consent safeguards
An experiment’s decision value or feasibilityExperiment priorities and measurement and decision rules
Approval status or conditionExecutive summary, pitch, and decision requested

Tip

Credibility comes from boundaries

Do not erase uncertainty to make the pitch smoother. A defensible statement names the boundary: what the plan supports now, what remains an Assumption or Unknown, and the decision requested under that condition.

Apply the revision to your plan

Make your material revision

Create a revision record for the most consequential weakness in your own plan. Use the exact headings Weakness → Correction → Dependencies → Recheck.

Include: the original plan-section reference and claim label; one specific correction; effects in at least two connected plan sections; one revised sentence for your executive summary or pitch; affected rubric criterion scores with section references; and any remaining Unknown plus whether you now seek approval, conditional approval, or deferral.

Write at least 500 characters (0/500).

Step 8 of 8

Present, Defend, and Close

Integrate your revised plan into one final delivery, defend a stakeholder challenge, and record a justified readiness verdict.

1. Assemble the current version

Build one decision-ready package

Your final package must describe one current business case: your plan. Put the revised commitments—not superseded assumptions—at the center.

Check that these eight sections agree with the executive summary, pitch, challenge response, rubric, and revision record:

  • Strategic core
  • Channel decisions
  • Execution roadmap
  • Resources and budget scenarios
  • Forecast assumptions
  • Measurement and decision rules
  • Consent safeguards
  • Experiment priorities

Trace important statements with the appropriate label: Evidence, Assumption, Forecast, or Unknown. Use section references such as [Plan: Forecast assumptions]. If an earlier artifact is missing, reopen the Same-case recovery packet for the same business case. A reconstruction remains an Assumption or Unknown; consolidation does not turn it into Evidence.

One source of truth

A central revised plan connects to eight plan sections and feeds the summary, pitch, stakeholder defense, and final decision.

Treat the Revised plan as the source for every final communication. A change in one connected commitment must be reflected everywhere it is used.

2. Deliver the recommendation

Complete your final delivery

Choose one route. Do not create a new case or add unsupported claims while presenting.

Spoken route: use your own timer and deliver the current pitch once in three minutes. Speak from your revised plan; no audience, recording, or upload is needed.

Written route: make a final 350–400-word review of your written equivalent. It should communicate the same recommendation, expected outcomes, resource request, risks and controls, and decision requested.

In either route, preserve qualifications that affect judgment. Name a conditional outcome as a Forecast, identify unresolved information as Unknown, and direct a stakeholder to supporting detail such as [Plan: Measurement and decision rules].

Three-minute story map

Use this timing map for the spoken route. The written route follows the same sequence without timestamps.

Keep detailed evidence in the named plan sections rather than adding every metric to the main pitch.
Elapsed timePitch focusSupporting section
0:00–0:30Customer opportunityStrategic core
0:30–1:15Coordinated responseChannel decisions
1:15–1:45Expected outcomesForecast assumptions
1:45–2:15Resource requestResources and budget scenarios
2:15–2:45Risks and controlsConsent safeguards
2:45–3:00Decision requestedMeasurement and decision rules

Tip

Keep the recommendation aligned

Before you close, compare the pitch with your 80–120-word executive summary. They may differ in detail, but they must request the same decision and use the same current commitments.

A useful final check: every figure or operational claim in the pitch should be traceable to a plan section; every material limitation should remain visible rather than being softened into certainty.

3. Defend one challenge

Answer from the revised plan

Now defend one stakeholder challenge using the Revised plan, not the baseline that existed before your material correction.

Select one previously rehearsed challenge: 25% less staff capacity with unchanged cash availability; conversion 30% below the assumed rate at the planned review; or a planned tracking source unavailable because consent or access conditions are not met.

Use the structure Position → Basis → Implication → Decision. Acknowledge what the challenge changes, protect only what your plan supports, and name a plan reference. Treat each scenario as an independent change to the baseline unless your plan explicitly connects it to another condition.

Final stakeholder defense

Write a concise response to one stakeholder challenge in no more than 110 words. Use these exact labels: Position → Basis → Implication → Decision. Ground the Basis in at least one reference such as [Plan: Execution roadmap]. State what is Evidence, Assumption, Forecast, or Unknown where relevant, and request the approval, conditional approval, or deferral your response now requires.

Write at least 180 characters (0/180).

4. Verify and close

State a justified readiness verdict

Finish with a readiness verdict.

Approval means the plan can proceed as currently committed. Conditional approval means it can proceed only with explicit conditions, owners, and limits. Deferral means a material gap prevents the requested commitment now.

Choose the verdict your evidence supports—not the most optimistic label. A strong final close also identifies how the material revision improved defensibility and confirms that all linked outputs now use the current plan.

Close your plan

Record your final close in four compact parts:

  1. Delivery route completed: three-minute spoken pitch or 350–400-word written equivalent.
  2. Decision requested and your readiness verdict: approval, conditional approval, or deferral. State any remaining condition explicitly.
  3. Material improvement using Weakness → Correction → Dependencies → Recheck.
  4. Consistency proof: name two supporting references in the form [Plan: …] that confirm the revised commitment is reflected across the package.

Write only what is true of your plan.

Write at least 300 characters (0/300).

Summary

Final review

Your decision-ready package is complete when one Revised plan supports the summary, pitch, defense, readiness verdict, and revision record.

  • Use the eight plan sections as one current source of truth.
  • Present a three-minute spoken pitch or a 350–400-word written equivalent with the same recommendation as the executive summary.
  • Defend a stakeholder challenge with Position → Basis → Implication → Decision and calibrated claim labels.
  • Choose approval, conditional approval, or deferral based on explicit conditions.
  • A material revision improves defensibility only when its dependencies are updated and rechecked.

Path complete

Congratulations! You completed: Present and Defend Your Marketing Plan

You have presented, defended, and closed your marketing plan. Your final package now links a current recommendation, qualified reasoning, a justified decision request, and a traceable material revision.

You completed the path

Congratulations! You went through every tutorial in this path.

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate