There's a simple test for a marketing plan. Pick any recommendation in it — a channel, a message, a sequence — and ask why. If the answer is somewhere in the plan itself, it's defensible. If the answer is "experience" or "that's what we did last time," it's a guess wearing a strategy's clothes.
Most plans fail the test. Not because the people who wrote them were wrong, but because the reasoning was never written down. The research happened (or didn't), the decision got made, and the plan recorded the decision without the reason.
The three lines every recommendation should trace to
The audience line. Who is this for, specifically, and what do they decide on? "Lead with the subscription offer" only makes sense if the plan already established that repeat buyers in this category are subscription-first. If that fact isn't in the plan, the recommendation is floating.
The competitive line. What are the alternatives saying, and where's the gap? A key message earns its place by occupying ground nobody else holds. If the plan doesn't show the ground, it can't show why the message is right.
The demand line. Where are these buyers actually looking? A channel recommendation with no search or behavior data behind it is a preference. With it, it's a decision.
What this does in the room
When a client or a leadership team pushes on a plan, the pushback is almost always "why this and not that?" A defensible plan answers from inside itself: here's the recommendation, here's the research line it stands on, here's the source. The conversation moves from opinion to evidence, and the person presenting stops having to be the evidence.
This matters more the less you know the room. A consultant in a new industry, or a marketing manager presenting to a CEO who's been in the business twenty years, can't win on authority. They can win on traceability.
How to build one
Write the research first and number its sections. Then, when you write the plan, cite them: "Channel mix — see §3.4, buyer behavior." It feels formal. It's actually the fastest way to find out which recommendations are guesses, because those are the ones you can't cite.
Every plan Swiftly produces works this way. The research report is structured and sourced, and each recommendation in the strategic plan points to the research it was built on. The "why?" test is built into the format, so nobody has to run it later, in the room, under pressure.
A plan you can't defend line by line isn't a plan. It's a list of things you're hoping work.