Back to all articlesCampaign briefs

Map campaign dependencies before committing to a launch

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

The copy is nearly finished, the audience file exists, and the campaign brief has an owner. Yet nobody can confirm whether the offer applies to that audience—or who will handle replies. A task list can look healthy while the decisions needed to launch remain blocked.

Before committing, map each consequential output to its prerequisites, accountable owner, and acceptance evidence. Then name the decision that cannot proceed without it. Work that does not depend on the missing input can continue in parallel.

The goal is not to diagram every activity. It is to distinguish work that can begin, work that can be finalised, and a campaign that can be authorised.

1. Turn tasks into dependency statements

A task says, “Prepare the audience.” A dependency statement says, “The audience owner cannot release the final recipient list until eligibility rules and permission checks are accepted.” The second version exposes both the missing inputs and the decision they control.

Use this structure when reviewing a brief:

Before we can approve [output or decision], [owner] must provide [specific input], accepted using [observable evidence].

If the input is described as “alignment” or “stakeholder feedback,” make it more specific. What must those stakeholders decide? What record would show that the decision is settled?

Useful map entries are outputs: an accepted offer rule, a reproducible audience definition, a checked destination, or an agreed response-handling plan. Activities such as holding a meeting belong in the task plan unless they produce one of those outputs.

Also distinguish available from accepted. A spreadsheet in a shared folder is available. A spreadsheet checked against eligibility rules, with exceptions resolved and acceptance recorded, can support a release decision.

2. Separate prerequisites from parallel work

Not every relationship deserves a blocking arrow. Classify it according to what the downstream owner can responsibly do without the input.

  • Hard prerequisite: the downstream decision must wait. Final audience release depends on accepted eligibility rules and permission evidence.
  • Provisional dependency: drafting can proceed against an explicit assumption, but acceptance must wait. Copy might be drafted while an offer restriction remains unresolved.
  • Parallel work: useful work can proceed independently. A response-handling checklist can be prepared while message wording is reviewed.
  • Shared-resource constraint: independent tasks need the same person. This affects capacity, not the logical relationship between their outputs.

Ask: “If this input changes, which accepted decision must we reopen?” If the answer is none, the proposed dependency may be unnecessary. If several decisions would change, the input probably belongs near the start of the chain.

Allow provisional work where rework is cheap and contained. Do not let a drafting assumption become an accepted fact when it controls recipient eligibility, the campaign promise, or response handling.

3. Use this filled dependency map

Fictional worked example: a business is preparing a WhatsApp campaign inviting existing customers to request a consultation about a new service package. All names, records, versions, and states below are hypothetical. This is a recommended operating design, not a description of Alactic controls or customer results.

This campaign initiates Platform conversations, so it needs an approved template. Under the WhatsApp Business Messaging Policy, recipient permission matters and opt-outs must be honoured. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Check the current policy for precise requirements.

The two tables are linked by shared row IDs. Copy both views when adapting the artifact: the structure alone does not explain what counts as accepted.

Hypothetical dependency map: structure and current state
IDRequired outputPrerequisitesAccountable ownerState
AOffer and eligibility rulesNonePriya, offer leadAccepted
BAudience release evidenceAMateo, data leadOpen
CAccepted message contentALena, copy leadAccepted for intended destination; live comparison outstanding
DAccepted request formAOwen, web leadOpen
EReply-handling readinessASara, service leadAccepted
FTemplate review outcomeCLena, copy leadPending
GLaunch authorisationB, C, D, E, F; final cross-output checkAmira, sponsorBlocked
Hypothetical dependency map: acceptance evidence and blocked decisions
IDRequired acceptance evidenceDecision blocked if missing
AAccepted offer record v2: inclusions, exclusions, and eligible customer criteria.Finalising eligibility, copy, form, and response answers.
BAudience rule v2; permission evidence; opt-out exclusions; closed exception log.Final recipient release.
CAccepted copy v3 matching offer v2 and the intended destination specification. Request wording checked against that specification, not the current live form.Submitting final content for template review.
DForm check v2: correct offer, successful request submission, and accurate confirmation.Authorising use of the destination in this campaign.
ENamed reply owner and backup; accepted response guide and human escalation route.Authorising a campaign expected to generate replies.
FApproved template record matching the accepted campaign content.Initiating this campaign’s Platform conversations.
GEvidence index for B–F; recorded comparison of the final message, approved template, corrected live form, confirmation, and response guide against offer v2; sponsor’s recorded authorisation.Launch commitment.

Read the chains as A → B → G, A → C → F → G, A → D → G, and A → E → G. C also feeds G directly because accepted wording must be compared with the final destination, not merely submitted for template review.

In this snapshot, B has an unresolved permission record, D still describes an earlier offer, and F is awaiting review. C is accepted only against the intended destination specification. It does not certify the live form.

Correcting D therefore cannot clear G by itself. The final comparison must establish that the message promise, form, confirmation, and response guidance agree. If correction changes the intended request or offer, reopen C and reassess F before authorisation. Template approval does not guarantee delivery; preparation, review, and actual delivery remain separate states.

4. Make acceptance evidence inspectable

Someone other than the map’s author should be able to inspect the evidence and understand the readiness judgment. “Done,” “checked,” and “approved in chat” are weak records unless the accepted output and scope are identifiable.

Keep these details beside each row or in its linked evidence record:

  • Output reference: the identifiable document, rule, or deliverable, including its version where relevant.
  • Acceptance condition: what must be true, not merely which activity must happen.
  • Accountable owner: the person responsible for resolving gaps and producing acceptable evidence.
  • Acceptor: the person authorised to judge whether the condition is met; this may differ from the producer.
  • Invalidation trigger: a change that makes the acceptance stale.

For B, “list uploaded” is insufficient. Evidence must connect the released audience to the eligibility rule, permission evidence, and opt-out exclusions. A changed eligibility rule requires another check even if the audience file has not changed.

For D, opening the page is not enough. Acceptance covers the advertised request and its confirmation. G then checks consistency across outputs. Those are different tests: a form can work correctly while presenting the wrong promise.

Keep evidence proportional. Each required record should support an identified decision. Collecting unrelated screenshots and meeting notes creates work without necessarily reducing uncertainty.

5. Find what actually controls commitment

Read backwards from G. Identify each unaccepted prerequisite, then follow its prerequisites until you reach an actionable missing input. This shifts discussion from general progress to the work that can change the decision.

In the hypothetical example, asking Amira to approve G does not resolve B, D, or F. Mateo needs to resolve the permission exception; Owen needs to correct and check the form; Lena needs the template review outcome. After those steps, the final consistency comparison still remains. Further copy polishing is not automatically useful.

The longest chain is not necessarily the one controlling commitment. Without reliable effort and waiting-time information, this map shows logical dependencies, not a completion forecast. A short chain containing an external review can carry more uncertainty than a longer chain of accepted internal outputs.

Watch for circular dependencies. Suppose Priya needs audience size to settle the offer, while Mateo needs offer rules to define the audience. Split exploration from commitment: produce a provisional audience estimate using recorded assumptions, settle the offer, then release the final audience against accepted rules. The exploratory estimate must not become release evidence by default.

An observable improvement is a more precise decision: the team can identify which input would unblock which output, rather than reporting that the campaign is “almost ready.”

6. Recover without disguising missing evidence

When a prerequisite fails, choose an action that changes the dependency honestly. Asking someone to mark a row complete is not a recovery plan.

  • Resolve the input: obtain the missing evidence or decision, then recheck affected outputs.
  • Reduce scope: remove a segment, offer variant, or destination whose prerequisites cannot be met. Update the brief and map before accepting the smaller campaign.
  • Use an accepted alternative: select an output that genuinely meets the current requirements. Similar wording or an old approval does not establish suitability.
  • Continue reversible work: prepare downstream material against a recorded assumption while keeping final acceptance blocked.
  • Withhold commitment: leave authorisation open when a necessary prerequisite remains unresolved.

For B, Mateo might exclude records with unresolved permission evidence rather than treat uncertainty as permission. That changes the audience scope, so the release record and any affected decisions need review.

For D, removing the link without revising the message could create another mismatch. Recovery must preserve a coherent promise and response path, not simply clear a table cell.

For E, any proposed automation needs a clear human escalation path. Record who takes over and how unresolved requests reach that person. This is a workflow requirement, not an assertion that a particular product supplies an automated control.

7. End the review with an operational handoff

A commitment review should produce a decision, not another progress summary. Confirm the scope under consideration, inspect the evidence that supports it, and record whether it is authorised, needs recovery work, or remains blocked. Sponsor authority cannot substitute for permission evidence or a required template approval.

Hypothetical handoff for this map: Amira withholds launch authorisation. The next unresolved input is B’s permission exception, owned by Mateo; he must provide either sufficient evidence for inclusion or a revised audience release excluding the affected records. Owen continues the form correction in parallel, while Lena tracks the template review outcome. None of those actions authorises sending.

Re-review is triggered by changes to offer rules, audience scope, message content, destination behaviour, template outcome, or response ownership. Reopen only the affected acceptances, but always complete G’s final consistency check against the versions proposed for use.

Keep three conditions distinct in the handoff: unowned dependencies need an accountable person; unresolved prerequisites need acceptable evidence; invalidated acceptances need rechecking after a change. A task-completion percentage cannot reveal those differences.

Campaign planningCampaign briefsDependency mappingMarketing operations

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