You have looked at a person's journey and used RACE to separate discovery, interaction, sale and the later relationship. A list of possible activities is still not a plan. You need to know what is happening now, what you want to change, which choices give the work direction, who can carry it out and how you will learn from the result. SOSTAC® helps you ask those questions in a sensible order.
SOSTAC® is the planning system created by PR Smith. Its six parts are Situation, Objectives, Strategy, Tactics, Action and Control (Smith, n.d.; Smith, 2020). The initials are memorable, but the purpose is practical: make a plan that another person can understand, carry out and challenge. You will build a one-page outline with real evidence and clearly marked unknowns. This is a public beginner guide, not a plan for a particular company or an invented customer.
Figure 1
Figure 1 in words: SOSTAC® asks how a plan is made and checked: situation, objectives, strategy, tactics, action and control. RACE, from Chapter 11, groups customer-facing marketing activity as Reach, Act, Convert and Engage. You can examine relevant RACE activity under several SOSTAC® questions. They have different jobs, so you do not need to choose one framework as a replacement for the other (Chaffey, 2020).
First, the six questions in plain English
Read the six parts as a conversation about a decision:
Situation — Where are we now? What do we know about customers, the offer, competitors, current results and conditions outside our control?
Objectives — Where do we want to go? What meaningful change, for whom, by when and under which counting rule?
Strategy — How will we get there? Which audience, promise, position and broad route will we choose, and what will we leave out?
Tactics — What exactly will we use? Which offer, content, price, channel, page, communication or service detail will carry out that direction?
Action — Who will do what and when? What has to be made, approved, delivered, maintained and handed over?
Control — How will we know and adapt? What will we observe, when, through which source and who decides what to change?
These questions come from Smith's framework, but the explanatory wording in this chapter is our teaching version (Smith, n.d.). They are connected, rather than six folders you complete once. You may discover in Control that your original Situation was incomplete. A resource constraint found during Action may require a narrower Strategy. The official summary template also keeps resources alongside the six sections rather than pretending a plan can run without people, money, data or time (SOSTAC® Planning Official Site, n.d.).
Figure 2
Figure 2 in words: Situation grounds Objectives, which guide Strategy; Tactics specify it, Action assigns and delivers it, and Control checks the result. The return to Situation means evidence can change the next plan. The figure is an original teaching redraw of PR Smith's named questions, not a copy of his visual template.
Before filling any box, choose scope: one offer, one relevant audience or task, a period for the plan and an owner. “Everything the business might ever market” is too broad for a first page. If the offer is proposed rather than available, label it proposed. If the audience is a hypothesis, say so. A blank or “unknown” cell with a sensible research question is more honest than a fabricated result.
Situation: establish where you really are
Situation analysis is a short, evidence-based account of the starting point. It does not require a hundred-page market report. Smith's account includes customers, competitors, the organisation's own capabilities and external conditions (Smith, n.d.). Earlier chapters gave you useful notes on the offer, market, customers and claims. Bring their findings into this section, with dates and sources. Do not simply paste every note into the one-page summary.
Start with the customer or user: what task are they trying to complete, what questions do they ask, and what obstacles have you actually observed or been told about? Use the journey map from Chapter 10 when you have evidence. If it is still an assumption map, distinguish that from a reported or observed journey. A search phrase, a page visit and a person's account are different kinds of evidence. Each can help, but none automatically explains every motive.
Next, examine alternatives and competitors. An alternative could be a comparable offer, another way to solve the task or the decision to wait. What can a person compare: price, access, time, evidence, support or limits? Verify the details at a date you can record. Do not describe an alternative as inferior because your business hopes to be chosen. The useful planning question is where your offer is genuinely suitable and where it is not.
Look at the organisation's current capability. What can it actually deliver? Which messages, pages and support processes exist now? What does available evidence say about enquiries, sales, successful use or recurring questions? A dashboard can be part of this picture, but check each metric's definition and the period it covers. If you do not have a baseline, write baseline unknown. You can then plan to collect a first comparable period.
Finally, note external conditions that could change the decision: availability, partner dependence, customer access, shifts in demand, or applicable rules. Do not fill the page with every possible trend. Select conditions with a plausible route to the chosen task and record how you know about them. Smith's own situation guidance calls for customer, competitor, company and external analysis (Smith, n.d.).
Figure 3
Figure 3 in words: The four lenses are customer task, alternatives, delivery capability and external conditions. For each, state a relevant question and record whether your answer is observed, reported, sourced, assumed or unknown. This is a compact set of prompts, not a claim that any particular market behaves in a certain way.
A SWOT can summarise strengths, weaknesses, opportunities and threats, but it does not create evidence. Strengths and weaknesses concern the organisation's relative capability; opportunities and threats concern external conditions. If a proposed “strength” is unsupported, mark it as a hypothesis. The Situation summary should end with a small number of consequential findings: facts or well-labelled uncertainties that could change a decision. An attractive diagram full of generic adjectives will not do that.
Objectives: define the change you seek
An objective describes an outcome you intend to reach. It is different from a task such as “post three times a week.” A task might be one way to work toward an objective; it cannot tell you by itself whether the person's problem was better solved. Smith's framework asks where you want to be, and his guidance includes both broad aims and specific measures (Smith, n.d.).
Begin with a customer outcome and a business outcome that can coexist. A suitable person should be able to understand, choose, use or obtain help with the offer. The business might need qualified enquiries, completed sales, successful starts, appropriate repeat use or another result tied to that service. Define the counted event in ordinary language. An enquiry received, an enquiry judged relevant and an enquiry answered are three different things. Do not quietly switch definitions to make a target appear met.
You encountered SMART in Chapter 4: Specific, Measurable, Achievable, Relevant and Time-bound. Different sources use variants of the A and R words; Smith's own page uses “Achievable” and “Realistic” (Smith, n.d.). The useful habit is to test whether the objective names the outcome, measure, practical capacity, purpose and review date. A baseline is what actually happened under a stated rule in a comparable earlier period. A target is a proposed future result. If there is no baseline, collect one or explicitly explain the uncertainty before promising a numerical gain.
Figure 4
Figure 4 in words: Ask who should achieve what, what counts, whether the plan can reasonably support it, why it matters and when it will be reviewed. The separate baseline and target labels prevent a proposed number from masquerading as an observed result. The figure contains no invented numbers.
Keep objectives few. One primary outcome and one or two guardrails may be enough for a first plan. A guardrail is a condition you do not want to worsen while pursuing the main goal, such as clarity of terms, quality of service or time to answer a relevant question. You do not need to give every possible measure a target. Choose those that change a decision, and state the source, period and owner for each.
Chapter 11's RACE view can help you locate an objective: is the immediate problem that the right person cannot find the explanation, cannot investigate, cannot complete a suitable purchase, or cannot use the offer afterward? Do not assume that more Reach fixes a broken onboarding step. The priority should come from Situation evidence, not from the metric that is easiest to screenshot.
Strategy: make the choice that directs the plan
Strategy is the broad choice about who you will serve, what value you will offer and how that position can reach the objective within constraints. It is not a synonym for “we will make videos” or “we will use social media.” Those are possible tactics. Smith emphasises target markets, positioning and the choices that guide later detail (Smith, n.d.). Chaffey similarly distinguishes the overall planning process from RACE's digital activity areas (Chaffey, 2020).
Write a short strategic statement in your own working plan using these blanks: “For [evidence-labelled audience/task], we will help with [specific need] by [credible value and delivery route], while leaving out [a tempting but unsuitable use or audience].” Do not fill the blanks with a fictional company for this article. The value must be supportable in the offer, not only in an advert. If it cannot yet be checked, label it a proposition to test.
Positioning means the place you want an offer to occupy in a person's set of choices. It depends on what the offer actually delivers and on the alternatives people consider. A value proposition is a concise explanation of the benefit, who it helps and why the claim is believable. Earlier chapters covered both from a beginner's view. Here you use them to decide which messages and channels make sense, and which would create a promise the service cannot keep.
A strategy has trade-offs. If you select one audience's question for the first period, you may defer another. If a channel requires more budget or support capacity than you have, you may choose a narrower route. If the offer needs careful explanation before a sale, an instant purchase message may be unsuitable. List the important choice and its reason, not a list of every channel someone has suggested.
Figure 5
Figure 5 in words: Strategy states audience, need, position and broad route. Tactics specify offer details, content, channels and touchpoints. A tactic belongs in the plan only when you can explain how it follows from the strategic choice and what it helps a person do. The table uses generic fields rather than a made-up campaign.
What if the Situation evidence is weak? A valid first strategy may be to learn before scaling: choose a small audience and real question, make one accurate explanation available, and observe whether it helps. That is still a strategic choice when you state the uncertainty, scope and decision that the learning will inform. It is not a promise that a small experiment will prove every customer need.
What if two objectives pull in different directions?
A plan may seek more enquiries while also aiming to answer questions carefully. These aims can support each other, but a tactic that increases form submissions by hiding important terms would conflict with the second. A strategy should say which outcome has priority and which safeguards must hold. Otherwise different team members may optimise separate numbers while the person experiences one confusing service.
Write the tension plainly. Which decision would you make if the first measure improved and the second worsened? What evidence would help you understand the trade-off? A guardrail from the Objectives section makes this visible, but the strategic choice must honour it. You may decide to serve a smaller group well, explain an exclusion clearly, or delay a Reach activity until the offer is ready. The exact choice belongs to the real organisation and evidence; the point here is to make it explicit.
There can also be a gap between a position and an operational capability. A promise of fast help needs an owner, hours of availability and a reliable response route. A promise of simple setup needs instructions a beginner can actually follow. The Strategy states the direction; Tactics and Action must make it real. If they cannot, revise the promise before publishing it. An honest, narrower position can be stronger than a broad claim that breaks at the first handoff.
Tactics: turn the choice into concrete touchpoints
Tactics are the specific methods through which you carry out the strategy. Smith describes them as the detail of strategy, including the marketing mix and communication channels (Smith, n.d.). In this series, the marketing mix is the set of connected decisions about the offer and how people encounter and receive it; Chapter 13 will explore the 7Ps and 4Cs more fully. Here you should already ask whether the product or service, price, access and support match the message.
A tactic can be an explanatory article, a clearer page, a fair comparison, a revised sign-up step, a relevant channel placement, a useful follow-up or better support instructions. Those are categories of possible work, not instructions to do all of them. For each chosen tactic, answer: which customer question does it address, where in the journey does it appear, what must be true for it to work, and which objective could it plausibly support?
Use RACE to check coverage, not to fill boxes for appearance. A tactic may help Reach when a truthful answer becomes findable, Act when details help a person investigate, Convert when the sale and confirmation are clear, and Engage when use and help are reliable. One tactic can support more than one part. Another tactic may be purely internal and still necessary to deliver a customer-facing promise.
Do not confuse a channel with a tactic's purpose. Email might answer a pre-purchase question, provide a post-purchase service update or invite feedback. A page may introduce an offer, explain terms or help someone resolve a problem. Describe what it does at that touchpoint. If a planned tactic uses a person's data or sends them messages, check the actual permission, technology and current requirements before using it; the planning worksheet itself does not grant permission.
There is also an order of work. If the sale depends on accurate terms, those terms must be confirmed before a campaign directs people to them. If support cannot yet fulfil a promise, fix the delivery handoff before amplifying the message. A tactic that makes an existing problem more visible may increase activity while worsening the person's experience.
Action: make the work deliverable
Action in SOSTAC® is the execution plan: who does what, by when, using what skills and process? Smith explicitly includes responsibilities, resources and internal coordination (Smith, n.d.). This is not the same as Act in RACE, which means a prospective customer's meaningful interaction. Similar words, different jobs.
Write each deliverable as an action another person can recognise. Name an owner, a reviewer or approver if needed, a due point, a dependency and a clear definition of done. A dependency is a prerequisite: an accurate offer statement may need approval before the page is published; an access process may need testing before a promise about immediate use appears. Avoid scheduling dependent work as though it were all independent.
Figure 6
Figure 6 in words: Before publishing a promise, establish the source, confirm the offer and the service handoff, prepare the communication, then review what reaches the customer. The boxes are generic work dependencies, not a claim that a specific organisation follows this exact process. Each transition needs an owner and a readiness check.
The first action might be research, because a missing answer could change the entire plan. “Find out why people leave” is too vague if you have no way to ask or observe. A more useful action names the question, method, participants or records you can appropriately access, and who will turn findings into a decision. It can still be small. What matters is that completion is verifiable and no participant's words are invented.
Estimate capacity honestly. How much time does the owner actually have? Which design, writing, engineering, customer service or review skills are required? Can the planned channel be maintained after launch? If an action has no owner, it is a wish. If an owner has no time, it is an unfunded wish. Revise the scope or schedule rather than hiding the constraint.
Control: decide how to learn and correct course
Control is the planned review of progress and results, not surveillance of individual customers. Smith asks what will be measured, when and what happens when results change (Smith, n.d.). Decide this before launching the tactic. Otherwise it is easy to select the most flattering metric afterward.
For each objective, record the measure, counting rule, source, baseline if known, review date and person responsible. Then add a decision rule: what question will you investigate if the result differs from what you expected? The rule need not be an automatic “stop at exactly this number.” It should tell the team when to inspect quality, customer feedback, delivery and the assumptions behind the plan.
For example, if a report shows more visits but no clearer customer outcome, do not automatically buy more Reach. Check whether visits are relevant, whether the explanation helps people decide and whether the sale or use step works. This is a conditional diagnostic question, not a fabricated result. If reported sales rise but support problems also rise, check whether the offer was delivered as promised. Control should connect business measures to the person's task.
Figure 7
Figure 7 in words: Measure under a defined rule, compare with a real baseline or stated target, investigate what may have changed, make a decision and update the plan. A changed metric is a prompt for investigation, not automatic proof that one tactic caused it. Control produces evidence for the next Situation.
Check measurement limitations. A platform's impression is not necessarily attention; a click is not understanding; a form start is not a completed sale; a purchase is not successful use. Counts from different systems may use different time zones, periods and deduplication rules. A small number of events can fluctuate sharply. Ask whether the measurement itself changed, whether another part of the service changed and whether offline outcomes are missing.
A short review might say: “We observed [real result] under [definition and source] in [period]. Compared with [actual baseline or target], this suggests [careful interpretation]. We still do not know [important alternative]. We will [named next check or change].” Leave the brackets empty until evidence exists. This is how Control becomes an honest learning habit rather than a success story written in advance.
Keep a small decision record
A one-page plan changes. Without a record, a later reader cannot tell whether a new tactic came from customer evidence, a delivery constraint or someone's preference. Under the page, keep a short decision log: date, what changed, the evidence or reason, who decided, which section was affected and when the decision will be reviewed. You do not need a new software platform. A small dated note linked to the plan is enough.
Separate a finding from an interpretation and from an action. “A support record contains a question” is a recorded event. “The earlier explanation may be unclear” is an interpretation to check. “Review and revise the explanation” is a proposed action. This distinction prevents a plausible story from being copied into the next plan as though it were established fact. It also makes it easier to reverse a decision when new evidence arrives.
Set a review rhythm that matches the length of the plan and the time it takes for the customer outcome to occur. You can inspect a broken page promptly, but later use or repeat purchase may need a longer period. A daily visit count and a monthly service outcome should not be compared as though they describe the same window. If little has happened, record that the evidence is insufficient rather than declaring a winner. Agree who will revisit the question and what additional observation would make the next decision fairer.
Resources: people, money, time and usable evidence
Smith's planning materials place resources alongside SOSTAC®; his basic manual highlights people, money and minutes, and the summary template also calls out data (Smith, 2020; SOSTAC® Planning Official Site, n.d.). The exact mnemonic matters less than confronting the constraint. A plan with a schedule but no responsible person, or with paid activity but no budget, is not deliverable.
Figure 8
Figure 8 in words: People means the capacity and skills to do and maintain the work; money is the available budget; time is the schedule and dependencies; data means the evidence and measurement you can use appropriately. Mark unknown capacity openly. These categories come from Smith's resource prompts, expressed here in plain language.
You can make the first page without a full spending forecast, but you cannot assume a tactic is free because a platform account is free. Writing, design, review, service readiness and ongoing support take time. A paid placement has a cost beyond the creative work. A measurement method may need setup and maintenance. Chapter 14 will help you build a more explicit budget and time limit. For now, ask whether the selected strategy is credible within the resources you can name.
Put the six sections on one page
The one-page outline is a decision summary. It is not the full research archive or a substitute for supporting notes. The official summary template includes six sections and resources (SOSTAC® Planning Official Site, n.d.). The worksheet below is an original, simplified teaching layout with space for evidence status, ownership and the next check. It does not copy Smith's grid or fill it with invented content.
Figure 9
Figure 9 in words: Situation contains a consequential finding and source; Objectives define outcome and measure; Strategy states a reasoned choice; Tactics name methods that follow that choice; Action assigns delivery; Control names how and when to review. Put longer evidence in supporting notes and keep the one-page version readable.
Figure 10
Figure 10 in words: At the top, identify the offer, audience or task, period and owner. Fill the six SOSTAC® rows with brief notes, evidence or an explicit unknown, then list people, budget, time and data needed. The worksheet has no prefilled company, target, performance claim or customer story.
A 55-minute first pass
Choose scope (5 minutes). Name one offer, one audience or task, a review period and an owner. Mark a proposed offer or audience as such.
Write Situation (10 minutes). Record up to three findings or unknowns that could change a decision. Add source and date for each. Separate customer evidence from internal opinion.
Write Objectives (8 minutes). State one meaningful outcome, its counting rule and review date. Add a real baseline if available; otherwise mark it unknown.
Write Strategy (8 minutes). Choose the audience need, credible value and broad route. Name one attractive alternative you are deferring and why.
Write Tactics (8 minutes). Select a small number of touchpoints or offer changes that follow the strategy. Check their place in the journey and RACE plan.
Write Action (6 minutes). Assign owner, dependency, approval or readiness check and due point to each chosen tactic.
Write Control and resources (10 minutes). Set source, review rhythm, investigation question and decision owner. Check people, money, time and usable evidence.
Read the page from top to bottom. Can another person follow the logic from a real finding to an objective, choice, tactic, delivery step and check? If one arrow breaks, revise that part. An unverified claim should remain a hypothesis, not quietly move into the Situation as a fact.
Common mistakes and a quick check
Writing tactics before the problem produces a channel list with no reason. Return to Situation and Objectives. Calling a tactic a strategy leaves no direction for choosing among methods. State the audience, value and trade-off. Setting a target without a baseline hides uncertainty; gather a baseline or explain the provisional nature of the target. Giving nobody the handoff means the plan may never be delivered. Measuring only clicks can miss an unusable offer after the sale.
There is also a mistaken belief that finishing the six boxes makes the plan true. SOSTAC® is a structure for reasoning and execution; it cannot authenticate a customer quote, verify a competitor claim or guarantee a result. Your sources and later checks do that work. Smith's official guide is a strong original explanation of the framework, while Chaffey (2022) provides a digital-marketing interpretation and cautions that stages can be revisited.
Try these classification questions. “Where are people currently unable to get an answer?” belongs first in Situation. “Which change should happen by the review date?” is an Objective. “Which audience and promise will we prioritise?” is Strategy. “Which page or message will implement it?” is Tactics. “Who will make and approve it?” is Action. “How will we check the actual outcome and revise?” is Control. If a proposed answer lacks evidence, mark the uncertainty in the relevant section rather than filling it with a story.
The article remains complete without either video. Original publisher pages and public YouTube metadata or descriptions were checked on 14 November 2026. Full playback, transcripts, captions, UK access and embedding remain to be verified before publication.
See the framework from its creator:SOSTAC - how to write the perfect plan (in 4 minutes), PR Smith (2012), approximately four minutes as titled and described on his own site. Use it after Figure 2 for the six questions. It is original professional teaching, not a peer-reviewed study.
Walk through the six sections:How to do a SOSTAC® plan for your business, Anna at Digisparq Media (2022). Public description timestamps cover Situation at 01:31 through Control at 06:16; exact runtime was not independently verified. It is an independent creator's practical explanation with book and affiliate promotions disclosed in the description. The article does not repeat any example from it.
What to remember
Situation describes the evidence-based starting point; Objectives define the change.
Strategy makes an audience, value and direction choice; Tactics specify the methods.
Action assigns work, dependencies and readiness; Control checks outcomes and changes the next plan.
Resources—people, money, time and usable data—must support the choices.
RACE organises customer-facing activity across the relationship; SOSTAC® organises how the plan is made, delivered and reviewed.
A blank or “unknown” field with a next check is more useful than a polished, invented result.
Further watching: PR Smith (2012) ‘SOSTAC - how to write the perfect plan (in 4 minutes)’, YouTube, 3 October. Available at: https://www.youtube.com/watch?v=StYGaCeaRkQ (Accessed: 14 November 2026). Digisparq Media (2022) ‘How to do a SOSTAC® plan for your business’, YouTube, 21 January. Available at: https://www.youtube.com/watch?v=4a8qtqpOgVE (Accessed: 14 November 2026).
A beginner-friendly route through 26 short lessons on customers, offers, channels, content and measurement. Start anywhere, with no account or paid tools.
Learn the difference between features and benefits, write a promise customers understand, and check which kinds of online value you can honestly deliver.