Make conditional campaign approval precise enough to act on
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
An approver writes, “Approved, provided the offer wording is corrected and the audience is checked.” The designer starts exporting assets. The campaign owner books a launch slot. Someone else assumes sending can begin as soon as the edits are uploaded. Each person has interpreted the same sentence differently.
The solution is to record two separate decisions: permission to prepare and permission to launch. A conditional campaign approval should name the work that may proceed, the commitments that remain prohibited, the evidence required to close each condition, and the person who must make the final release decision. Closing the conditions should make the campaign eligible for that decision—not silently grant permission to launch.
The record below is a recommended operating practice, not a description of a software control. It can live in a shared document, campaign brief, or approval register, provided the team can identify the current version.
1. Replace the ambiguous verdict with a bounded decision
“Approved with changes” combines an assessment of the campaign with an instruction to the team. Separate them. The approver may support the campaign’s direction while withholding authority to publish, spend, or contact recipients.
Use an explicit decision statement such as:
Preparation is authorised only for the activities listed below. Launch is not authorised. Each outstanding condition requires the specified evidence and acceptance by its named verifier. After all conditions are closed, the named release approver must issue a separate release decision for the identified campaign version.
This wording leaves room for useful work without pretending the campaign is ready. It also avoids treating silence as permission.
Give the record a current decision state. Useful choices are preparation authorised, awaiting final release, released, held, and withdrawn. A condition can be open, evidence submitted, accepted, or reopened. These are working labels; what matters is that the team understands what each permits.
Do not use one “approved” label for both the campaign and its individual conditions. A campaign can have every condition accepted and still be awaiting a final release decision.
2. Draw the boundary around preparation and commitments
List actions rather than broad departments or phases. “Production may proceed” is too loose: it might mean editing a draft, commissioning a supplier, or placing an irreversible print order.
For each permitted activity, specify its limit. Internal asset preparation might be allowed, while external publication remains prohibited. A supplier quote might be requested, while a purchase order remains unauthorised. A test might use internal recipients only, not the intended campaign audience.
Consider three kinds of exposure:
- External exposure: Will customers, partners, or the public see or receive anything?
- Financial commitment: Will the action commit money or create cancellation costs?
- Rework exposure: Will completing the task now make a later correction difficult or expensive?
Preparation is not automatically harmless. If the unresolved condition concerns the core offer, polishing every asset may create avoidable rework. Permit low-cost draft work and hold final production until the offer is settled.
The trade-off is deliberate: a narrow preparation allowance may slow some work, but a blanket hold can waste time on tasks that are safe to complete. The record should make that choice visible rather than leaving each contributor to guess.
3. Write conditions that someone can actually close
A usable condition has an observable acceptance test. “Check the audience” is an instruction to do work, not a definition of completion. It does not say which audience, what to check, or who decides whether the result is acceptable.
For each condition, record:
- Required change: The specific defect or uncertainty to resolve.
- Owner: The person responsible for producing the correction and evidence.
- Closure evidence: The revised asset, comparison, test result, or other inspectable output.
- Acceptance test: What the verifier must observe before accepting it.
- Verifier: The person authorised to accept that condition.
- Timing and consequence: When evidence is needed and what happens if it is late.
A deadline is not an acceptance test. Nor is “owner confirms done” sufficient when the approver needs to inspect the result. Keep the evidence proportionate: a wording correction may need only a marked comparison and final preview, while an audience correction may need the selection rules, exclusions, and a refreshed summary.
If a condition cannot be tested without another decision, name that decision. For example, “choose the final offer” should identify who chooses it and where the selected wording will be recorded.
4. Filled hypothetical conditional-approval record
Fictional worked example: All names, dates, counts, versions, and limits below are hypothetical. This record illustrates a campaign offering an existing-customer service review. It is not a customer result or a product capability claim.
Decision and scope
Record: CA-017
Campaign: Existing-customer service review invitation
Accountable campaign owner: Maya Chen
Conditional decision issued: 8 September 2026, 10:00, team operating time
Current state: Preparation authorised; launch not authorised
Reviewed baseline: Campaign brief version 3, message copy version 4, audience definition version 2
Proposed release window: 10 September 2026, 10:00–12:00, team operating time
Final release approver: Elena Park
Deputy: None designated; if Elena is unavailable, launch remains on hold.
Permitted work
- Revise the invitation and landing-page draft to address the listed conditions.
- Prepare internal previews and send tests only to the named internal review group.
- Rebuild the proposed audience and prepare an access-limited review summary.
- Prepare a support response sheet and confirm staff availability without making external commitments.
Prohibited commitments
- No customer sends, public publication, or customer-facing scheduling commitments.
- No paid placement, supplier booking, or non-cancellable purchase.
- No expansion beyond the audience definition under review.
- No change to the offer, campaign objective, channel, or release window without renewed review.
Outstanding conditions
C1 — Remove the unsupported response-time promise.
Owner: Maya Chen.
Required change: Remove the promise of a same-day review from both the invitation and landing-page draft.
Evidence: Message copy version 5, landing-page draft version 3, and a marked comparison against the reviewed baseline.
Acceptance test: Neither asset promises same-day completion; both describe the same next step.
Verifier: Elena Park.
Evidence due: 9 September, 12:00.
Status: Open.
C2 — Correct and substantiate the intended audience.
Owner: Ravi Shah, audience lead.
Required change: Use the agreed existing-customer selection rules and exclude recipients recorded as opted out. Resolve records with uncertain contact permission before inclusion.
Evidence: Audience definition version 3, exclusion summary, and a dated review snapshot stored in the restricted campaign folder.
Acceptance test: Selection and exclusion rules are documented; unresolved permission records are excluded; the summary reconciles included and excluded records without an unexplained difference.
Verifier: Priya Das, customer operations lead.
Evidence due: 9 September, 14:00.
Status: Open.
C3 — Confirm that the response route is staffed.
Owner: Noah Bell, support lead.
Required change: Assign a named responder and backup for the proposed release window and document how unanswered requests are handed over.
Evidence: Response sheet version 2 and written acknowledgement from the responder and backup.
Acceptance test: Both people acknowledge their role; the response sheet names the handover route and unresolved-request owner.
Verifier: Priya Das.
Evidence due: 9 September, 16:00.
Status: Open.
Final sign-off requirements
Release packet: Accepted closure entries for C1–C3; final asset previews; final audience snapshot reference and count; support response sheet; and a summary of changes since the reviewed baseline.
Release rule: Maya submits the packet. Elena either releases the identified versions for the stated window or records a hold. Condition verifiers cannot grant launch permission through their individual acceptance entries.
Missed window: If written release is absent by the proposed start time, do not launch. Agree a new window and recheck time-sensitive evidence.
Final decision field: Pending. No release authority has been issued.
5. Close conditions without losing the evidence trail
Keep the original condition intact. Add a closure entry rather than replacing the requirement with “done.” The entry should identify the submitted evidence, verifier, acceptance result, and time of acceptance.
In the hypothetical record, a useful entry would read: “C1 accepted by Elena Park on 9 September at 11:40. Compared message copy version 5 and landing-page draft version 3 with the baseline. Same-day promise removed from both; next-step wording matches.”
That is more useful than a tick because it tells a later reviewer what was inspected. It also limits the acceptance to those versions. If someone changes the message again, the earlier acceptance is not evidence that the new wording was checked.
Return inadequate evidence with a specific reason. “C2 remains open: the exclusion summary does not account for records with uncertain permission” gives the owner a concrete next action. “Not approved” does not.
For a small, low-risk correction, one person may own and verify the change if the decision maker explicitly accepts that arrangement. Do not add reviewers merely to make the record look rigorous. Separate verification is most useful where mistakes would be hard to reverse or the result requires independent judgement.
6. Make release a separate, version-specific decision
The release approver should see the assembled campaign, not just a series of isolated corrections. Individually acceptable edits can still produce an inconsistent whole—for example, an invitation that describes one next step and a response sheet that describes another.
Use a final statement that identifies the release boundary. A hypothetical completed release entry might say:
Released by Elena Park on 10 September 2026 at 09:20 for the 10:00–12:00 window only. Scope: message copy version 5, landing-page draft version 3, and audience snapshot AS-017-final containing 420 recipients. C1–C3 are accepted. No additional audience, revised offer, or later release window is authorised by this decision.
This illustrates a later decision; it does not change the pending state of the filled record above. The actual record would need the approver’s own confirmation.
A release decision authorises the specified action. It does not prove that publication or sending occurred, or that recipients received anything. Keep authorisation and the subsequent execution record separate.
7. Define what happens when the plan changes
A conditional approval needs an exception route, especially near a planned launch.
- A condition misses its deadline: Record the delay and decide whether the window remains feasible. Do not treat the missed deadline as an implicit waiver.
- A material asset changes after acceptance: Reopen the affected condition and identify any connected assets that need another check.
- The audience or offer expands: Return the changed scope to the approver. Acceptance of the original scope does not cover the expansion.
- The approver is unavailable: Use a previously named deputy or hold. Availability pressure is not delegated authority.
- Unauthorised activity has begun: Stop further activity where possible, record what actually happened, notify the accountable owner, and obtain a recovery decision. Do not backdate approval.
Not every minor correction needs a complete review restart. Define what can remain closed and reopen only the affected conditions, unless the change undermines the campaign’s overall basis. Record the reason so the narrower review is understandable.
8. Test the record before the next handoff
For the next campaign receiving conditional approval, ask the producer and campaign owner to read the record separately. Each should be able to answer: What may I do now? What must I not commit? What evidence is missing? Who decides release? Which versions and window would that release cover?
If their answers differ, revise the record before work continues. A measurable first target is that every open condition has an owner, observable acceptance test, evidence reference or evidence requirement, and named verifier—and that no final decision field is blank or implied.
After the campaign, review unresolved-at-release conditions, work repeated because scope was unclear, and commitments made before authority existed. Use those observations to tighten the next record, not to add fields nobody uses.
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