Back to all articlesCampaign briefs

Separate campaign facts, assumptions, and unresolved decisions

Alactic Editorial10 min read

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

A brief says the audience is ready, the offer is available, and the support team can handle responses. The writing is confident. The approver cannot tell which statements have evidence behind them, which are working guesses, and which still need someone to choose a direction.

The fix is not to make every sentence cautious. Put consequential uncertainty in a campaign brief assumptions register: classify each statement, name the person responsible for resolving it, specify the evidence or decision required, and state what happens if it remains unresolved.

Then approve a defined scope rather than a reassuring document. Some unknowns can remain open during creative development. Others must prevent audience approval, release authorisation, or a promise appearing in the campaign.

1. Separate what is known from what must be chosen

Use three labels with different closure rules:

  • Fact: A statement supported by evidence that applies to this campaign. Record the source, scope, and when it was checked. A fact about a previous offer or a different audience is not automatically a fact about this one.
  • Assumption: A statement being treated as true for planning without sufficient evidence. Record how it will be checked and what changes if it is wrong.
  • Open decision: A choice that an authorised person has not made. Record the options, decision owner, and latest useful decision point.

This distinction prevents two common mistakes. First, a team may keep researching a question that actually needs a decision, such as which of two offers to promote. Second, it may treat an evidence gap as a matter of preference, such as whether the selected audience has the necessary permission for the planned communication.

A single sentence can contain all three categories. “We will send the approved offer to eligible contacts on Thursday” may hide an established offer, an unverified audience, and an undecided release date. Split it into separate entries. Each should be capable of changing status independently.

2. Capture only uncertainty that can change the campaign

The register should not become a catalogue of everything the team does not know. Include a statement when being wrong could change the audience, claim, offer, channel, timing, resource commitment, or approval decision.

For each entry, capture:

  • ID and statement: One claim or choice, written precisely enough to resolve.
  • Type and current status: Fact, assumption, or open decision; then verified, pending, accepted temporarily, or closed.
  • Evidence or validation method: What supports it now, or what specific check would resolve it.
  • Owner: One person accountable for bringing back an answer, even if others help.
  • Decision point: The stage before which an answer is needed.
  • Consequence: What changes if the assumption is wrong or the decision stays open.
  • Approval effect: Which activity can proceed and which must wait.

Avoid entries such as “Check audience” or “Operations to confirm.” They leave both the question and the responsibility ambiguous. Write “Audience owner to verify that the selected records meet the documented inclusion rules before audience approval.”

Also distinguish a validation owner from a decision owner. The person who gathers evidence may not have authority to accept the remaining uncertainty.

3. Filled fictional example: a campaign uncertainty register

All campaign details in this worked example are hypothetical. A fictional training business is preparing a WhatsApp campaign inviting existing contacts to request information about an upcoming workshop. Creative development can begin, but the team has not authorised release. The roles below represent designated individuals on that fictional team.

F1 — What the offer actually includes

  • Type and status: Fact; verified within the fictional scenario.
  • Statement: The current offer includes a workshop place and a downloadable workbook. It does not include individual coaching.
  • Evidence and method: The offer owner has checked the current offer sheet and confirmed the inclusions in the campaign record.
  • Owner and decision point: Offer owner; recheck if the offer changes before copy approval.
  • Consequence if no longer true: Revise the brief and remove unsupported inclusions from every affected asset.
  • Approval effect: Copy may use these inclusions while the offer version remains unchanged.

A1 — Permission for the intended audience

  • Type and status: Assumption; pending validation.
  • Statement: Every contact in the proposed audience has appropriate permission for the planned WhatsApp communication and has not opted out.
  • Validation method: Check the proposed audience against the relevant permission records and current opt-out records. Remove records whose eligibility cannot be established.
  • Owner and decision point: Audience owner; before audience approval, with a fresh check before release authorisation.
  • Consequence if wrong: Reduce or rebuild the audience. Do not treat a smaller eligible audience as a reason to restore uncertain records.
  • Approval effect: Blocks audience approval; does not block drafting copy for an eligible audience.

A2 — Template readiness

  • Type and status: Assumption; pending validation.
  • Statement: The planned initiation message can use an approved template appropriate to the campaign.
  • Validation method: Confirm the required template's current status and check that the intended content fits its approved use. Record the exact version checked.
  • Owner and decision point: Messaging owner; before release authorisation.
  • Consequence if wrong: Revise the message or move the release decision until the required template is available.
  • Approval effect: Preparation may continue, but template readiness remains a separate release condition. Approval is not evidence of future delivery.

A3 — Coverage for incoming questions

  • Type and status: Assumption; pending validation.
  • Statement: The service team can cover the proposed response period and route questions it cannot answer to a named person.
  • Validation method: Obtain a named coverage roster, confirm handover ownership, and walk through a fictional question outside the standard response guidance. This checks readiness, not future response volume.
  • Owner and decision point: Service lead; before the release time is approved.
  • Consequence if wrong: Move the release time, narrow the campaign scope, or arrange coverage before authorisation.
  • Approval effect: Blocks approval of the proposed release time, not development of the offer or audience rules.

D1 — Whether to promise limited availability

  • Type and status: Open decision; unresolved.
  • Choice: Use neutral invitation copy or include a limited-availability claim supported by a current capacity record.
  • Decision method: The offer owner supplies the capacity evidence; the campaign approver chooses the permitted wording.
  • Owner and decision point: Campaign approver; before copy approval.
  • Consequence if unresolved: Use the documented fallback: neutral invitation copy without a scarcity claim.
  • Approval effect: Does not block copy approval if the fallback is explicitly accepted.

D2 — Primary response route

  • Type and status: Open decision; unresolved.
  • Choice: Invite a reply in WhatsApp or direct the recipient to an information page.
  • Decision method: Review the recipient journey, ownership of each destination, and the service team's confirmed coverage.
  • Owner and decision point: Campaign lead; before final asset approval.
  • Consequence if unresolved: Keep alternative drafts, but do not approve a final call to action or destination.
  • Approval effect: Blocks final asset approval because it changes both the message and the handover.

A4 — Preference for concise introductory copy

  • Type and status: Assumption; proposed for temporary acceptance.
  • Statement: A concise introduction is sufficient for this audience to understand the invitation.
  • Validation method: Review the draft for essential offer details and a clear route to further information. Audience preference remains unverified; an internal review cannot establish it.
  • Owner and decision point: Content lead; request acceptance at copy approval.
  • Consequence if wrong: Recipients may need additional explanation. The draft must not omit essential conditions merely to stay short.
  • Approval effect: May remain open if the approver accepts the uncertainty and the information route is ready.

For the WhatsApp-specific checks, the current Business Messaging Policy is the relevant external reference. Recipient permission matters, opt-outs must be honoured, and approved templates are used to initiate Platform conversations and outside the customer-service window. That window opens or resets with a user message and lasts 24 hours. Template approval does not guarantee delivery. These requirements should not be confused with the team's own proposed approval workflow.

4. Decide what blocks which approval

A blanket “blocked” status is often too blunt. It can stop useful preparation while leaving the actual release condition unclear. Instead, connect each unresolved item to the activity it affects.

Use three approval treatments:

  1. Must resolve: The unknown affects audience eligibility, truthfulness of a claim, necessary channel readiness, or the ability to handle the proposed journey. Hold the affected approval until there is evidence or a changed scope.
  2. Proceed with a fallback: An unresolved choice has a safe, explicit alternative. Record who accepts the alternative and apply it to the assets.
  3. Accept temporarily: The remaining uncertainty is bounded, the consequence is understood, and the approver accepts it without representing it as fact.

In the fictional register, uncertain audience permission cannot be compensated for by polished copy. By contrast, the team can remove an unsupported scarcity claim and continue. The distinction is whether the campaign has a workable alternative, not whether the deadline is close.

5. Ask for evidence that answers the exact question

“Confirmed with the team” is weak evidence because it does not show what was confirmed. Ask owners to return an answer, its scope, and a reference to the supporting record.

Validation should match the uncertainty. An offer inclusion needs an authoritative offer record. A staffing assumption needs named coverage. A response-route decision needs an authorised choice. A screenshot of a draft does not establish audience eligibility, and an approved template does not establish that the campaign has been delivered.

Define the completion condition before assigning the check. Otherwise, owners may return partial evidence that looks complete. For A1, a useful result is a reviewed eligible audience with unresolved records excluded—not a statement that permission records exist somewhere.

Keep sensitive recipient-level evidence out of a broadly circulated brief. Reference the controlled record and summarise the finding. The approver needs the basis for the decision, not an unnecessary copy of the underlying contact data.

6. Make sign-off specific and conditional

An approval comment should identify the brief version, approved scope, remaining uncertainty, and release conditions. Avoid “Looks good” when the audience, message, or timing is still unsettled.

Hypothetical approval record: “Approve creative development using the confirmed offer inclusions. Accept concise introductory copy as a working assumption, provided essential conditions and the information route are clear. Use neutral wording without a scarcity claim. Audience approval remains pending the permission check. Release authorisation remains pending template readiness, response-route selection, and confirmed service coverage.”

This is not approval to send. It permits specified work while preserving the unresolved gates.

Keep the register beside the brief and link entries to affected sections using their IDs. If a late edit changes the call to action, revisit D2 and A3 rather than assuming earlier sign-off still covers the new journey.

7. Recover when an assumption fails before release

When an assumption proves wrong, do not silently rewrite the brief and preserve the old approval. Record what changed, identify the affected assets and decisions, and reopen only the relevant approvals.

Suppose the fictional service lead cannot confirm coverage. The team can move the proposed release time or redesign the response route. Either choice requires the corresponding journey and timing checks again; it does not necessarily require reopening the verified offer inclusions.

Watch for three register failures:

  • Everything is a blocker: Separate irreversible commitments from reversible preparation, and define fallbacks where possible.
  • Everything is accepted: Require a named approver and an explicit consequence for each accepted uncertainty. A deadline is not evidence.
  • Closed items never reopen: Record the conditions that invalidate evidence, such as a changed offer, audience, template, or response route.

The register is useful only if its status changes the work. A red item that everyone ignores is decoration.

8. Run a bounded uncertainty review on the next brief

Before the next approval meeting, mark every consequential statement as fact, assumption, or open decision. Move the assumptions and decisions into the register, and add evidence references for the facts that support approval.

At the meeting, check three observable outcomes: every unresolved entry has one owner; every blocking entry names the approval it holds; and every temporarily accepted assumption has a recorded consequence and approver.

Finish with a decision record that states what may proceed now and what cannot. If a colleague who missed the meeting can identify the next required check without asking the author, the brief is doing its job.

Campaign briefsApproval workflowsUncertainty managementCampaign planning

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