Write campaign scope boundaries that prevent late additions
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A campaign to help existing customers adopt one feature can quickly acquire a prospect offer, a product announcement, and an event invitation. Each request may sound small. Together, they create several competing campaigns sharing a deadline.
Useful scope boundaries explain more than what the team will produce. They identify who the campaign serves, what action it supports, which barriers it addresses, and what it deliberately leaves out. They also establish how to decide whether a late request belongs.
The filled hypothetical worksheet below turns those boundaries into an operating practice. It distinguishes an acceptable clarification from a new purpose, tests both production capacity and recipient attention, and records what happens when a request lacks a credible rationale.
1. Anchor the boundary to one audience action
A deliverables list cannot control scope by itself. An email and a guide describe formats, not purposes. Almost any request can be presented as another paragraph or link.
Start with this sentence:
This campaign helps [defined audience] who [relevant situation] take [one primary action] during [defined period].
Use an observable action. Increase engagement leaves room for almost anything; save a first report gives reviewers a concrete reference point. A request that helps the same audience complete that action may belong. A request for a different audience or decision needs a different assessment, however easy it is to produce.
Connect the success measure to that action. Clicks can help diagnose interest or navigation problems, but they do not establish that recipients completed the intended task. If clicks are the only measure, an unrelated offer may look successful while distracting from the campaign’s purpose.
2. Pair inclusions with the expansions they exclude
Write exclusions around plausible requests rather than using a blanket phrase such as no extra work. Pairing each inclusion with its nearest expansion gives reviewers something they can apply.
- Audience: Include eligible existing customers; exclude prospects who need a different proposition.
- Action: Include help with the primary task; exclude purchases or registrations that introduce another decision.
- Message: Include explanations that resolve task barriers; exclude unrelated product news.
- Assets: Include named campaign materials; exclude additional channels or formats requiring separate planning.
- Measurement: Include the intended outcome and useful diagnostics; exclude unrelated targets added to justify extra content.
- Time: Include the agreed campaign period; exclude open-ended follow-up.
Where useful, name the destination for excluded work: prospect acquisition needs a separate campaign brief, for example. This makes routing more practical than simply saying no.
Distinguish additions from corrections. An inaccurate instruction or broken destination needs attention, but the correction may reveal a larger readiness problem. If the audience cannot complete the action, reassess the campaign rather than treating the problem as a routine copy edit.
3. Use this filled hypothetical scope worksheet
Fictional worked example: Cedar Desk is an invented software business. All quantities, periods, capacity allowances, requests, and decisions below are hypothetical. This is a recommended workflow, not an Alactic customer result or a description of product controls.
Purpose and outcome
- Campaign: First saved report.
- Audience-action sentence: Help existing account administrators with reporting access who have not saved a report complete their first saved report during a two-week campaign.
- Primary action: Save a first report using existing product access.
- Primary measure: Number and proportion of eligible recipients completing that action during the campaign period.
- Interpretation: Completion during the period is an observed outcome, not proof that the campaign alone caused it.
- Diagnostics: Guide visits and reported obstacles to completion.
Included work and limits
- Assets: One invitation email, one reminder email, and one short campaign guide.
- Message: Explain the value of a saved report, access prerequisites, and how to begin.
- Destination: The existing reporting area, supported by the guide.
- Help: An existing route for recipients to ask questions.
- Capacity: The content owner has reserved two hours for small guide clarifications before final review. Larger additions require a revised commitment or substitution.
- Clarity boundary: Emails retain one prominent action leading toward saving a report. Supporting explanations must not introduce another offer or bury that action.
- Outcome review: Summarise completions and recurring obstacles for the defined audience and period.
Explicit exclusions
- Prospect acquisition: People without accounts cannot take the defined action.
- Upgrade promotion: Buying access is different from using access already available.
- General launch news: Unrelated announcements do not resolve a reporting barrier.
- Webinar programme: Registration and attendance introduce separate actions and assets.
- Product redesign: Record product obstacles for the responsible owner; do not absorb redesign into campaign work.
- Indefinite reminders: Further follow-up requires review after the campaign period.
Decision ownership and record
- Campaign lead: Classifies requests and maintains the decision record.
- Marketing lead: Approves any replacement of the audience, action, or intended outcome.
- Affected work owner: Confirms effort and identifies any displaced commitment.
- Record fields: Request; audience and action; barrier or requirement; clarity effect; capacity effect; decision; displaced work; owner.
One person may hold several responsibilities in a small team. The important distinction is between confirming capacity and approving a change of purpose.
4. Apply a complete change-request rule
Assess purpose before effort. A quick addition can still be wrong for the campaign.
- Audience test: Does it serve the audience already defined?
- Action test: Does it help recipients complete the primary action without introducing a competing decision?
- Support test: What credible barrier does it remove or requirement does it address? A stakeholder preference alone is not a rationale.
- Envelope test: Does it fit the assets, period, and confirmed capacity? Does it keep the primary action prominent without unnecessary competing information?
Apply the outcomes explicitly:
- All tests pass: Accept and record the reason.
- Audience or action fails: Route to a separate campaign brief, unless the purpose owner deliberately replaces the current purpose.
- Audience and action pass, but support fails: Decline or defer pending a clear rationale, even if spare capacity exists.
- Support passes, but capacity fails: Propose a named substitution, narrower alternative, or revised commitment. Do not accept until the affected owner confirms the choice.
- Support passes, but clarity fails: Narrow, relocate, or remove the addition and reassess. Available production time does not resolve a crowded message.
An unanswered question is not approval. If new information invalidates the audience or action itself, pause and rebrief instead of forcing the request through the existing tests.
5. Work through the requests and record the decisions
The following filled entries continue the fictional Cedar Desk example. They can be reused as a model for a campaign decision log.
Accepted clarification: reporting access
Request: Explain who has reporting access. Rationale: Administrators need to establish eligibility before starting. Decision: Accept a short clarification in the guide. Clarity: Keep the email action unchanged. Capacity: The content owner confirms a hypothetical half-hour effort within the reserved allowance. Displaced work: None. Owner: Campaign lead.
Accepted narrowed alternative: troubleshooting
Request: Create a separate troubleshooting article. Rationale: The requester identifies two specific setup obstacles affecting the same task. Decision: Decline the separate asset; accept a short troubleshooting section in the existing guide. This is a narrowed alternative, not a substitution.
Clarity: Place it after the main instructions so readers can begin without navigating extra material. Capacity: The content owner estimates one hour for drafting and review. Combined with the access clarification, that uses one and a half hours of the hypothetical two-hour allowance. Displaced work: None. Owner: Campaign lead, with capacity confirmed by the content owner.
Deferred unsupported addition: company background
Request: Add a company-history paragraph to the guide. Audience and action: The requester intends it for the same administrators, but identifies no reporting obstacle it resolves. Decision: Defer pending a credible rationale, despite the remaining capacity. Reason: It fails the support test and adds reading without demonstrated task value.
Rejected competing action: upgrade discount
Request: Add an upgrade offer to the reminder. Decision: Route to an upgrade-campaign brief. Reason: It introduces a purchase decision rather than helping recipients use existing access. Short copy would not fix that mismatch.
Rejected audience expansion: prospects
Request: Send the campaign to prospects. Decision: Route to an acquisition brief. Reason: Prospects must become customers before they can complete the defined action; changing the recipient list would not make this campaign suitable.
Deferred extension: further reminders
Request: Continue reminders beyond the agreed period. Decision: Review completions and reported barriers first. Reason: The request changes the time boundary and needs a capacity decision; the original brief does not authorise an ongoing programme.
6. Treat recipient attention as a separate cost
Production effort and recipient attention are different constraints. A link takes little time to insert but can give readers another decision. A substantial guide clarification may take longer to produce while making the primary task easier.
Review the changed asset, not just the request description. Can a reader still identify the intended next step? Does essential guidance appear before optional detail? Does the addition require an unrelated choice? If the action becomes harder to locate, the change has not passed the clarity check.
When capacity is the problem, compare meaningful commitments. Removing a sentence does not necessarily fund a new asset. Name the work being reduced or removed, and have its owner confirm the exchange. When attention is the problem, consider moving necessary detail into the existing guide while preserving a clear route from the message. Then review that arrangement again; relocation alone does not prove the content belongs.
7. Recover a campaign whose scope has already drifted
Review the campaign as a whole rather than defending each addition separately.
- List every requested recipient action. Separate the intended task from purchases, registrations, enquiries, and other asks.
- Map each action to its audience. Identify incompatible starting situations.
- Choose the governing purpose. Retain the original or deliberately replace it; do not label several competing actions primary.
- Apply the four tests. Remove unsupported content, separate other campaigns, and confirm capacity for retained changes.
- Issue a revised boundary. Update the audience, action, measure, inclusions, exclusions, and decision log together.
If recipients cannot perform the central action, removing distractions is insufficient. Pause the campaign until the readiness problem is understood.
8. Check whether the boundary works in practice
Use the worksheet on one active campaign and assess the next requests against it. Record accepted requests, narrowed alternatives, genuine substitutions, deferrals, and work routed elsewhere.
Look for observable failures: work starting before approval, accepted requests with no barrier stated, substitutions without named displaced work, or assets whose main action becomes harder to find. These reveal which part of the rule needs attention.
If useful requests repeatedly fail only on capacity, review the allowance. If reviewers keep disagreeing about relevance, sharpen the audience-action sentence and support test. The goal is not a high rejection rate; it is a usable boundary that makes decisions explainable before work begins.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications