Back to all articlesTemplate lifecycle

Run a Controlled Cutover Between Template Versions

Alactic Editorial9 min read

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

A replacement template can be ready while staff still select the old one, saved drafts retain outdated wording, and an assisted workflow uses its previous reference. Announcing that the replacement is available does not establish which version people must use.

A controlled cutover separates permission to prepare changes from permission to resume submissions. It identifies the replacement, reconciles pending work, records individual acknowledgements, and releases each sending path only after verification. Historical records may retain the old version without authorising its continued use.

This guide starts after dependency discovery: you already know where the old template is used. It covers the operational handover, not campaign scheduling or exact interface instructions. The filled runbook below can be adapted to your own release.

1. Define the effective point and the scope

Identify the actual template reference, language, intended use, and internal revision. A label such as “new version” is insufficient. If revisions are not separate selectable objects in your workspace, explain how operators will identify the intended selection.

Define what the effective time governs. A practical rule is new send submissions after the effective time, not delivery time. An earlier submission might arrive later without indicating a cutover failure.

Include every discovered sending path and its pending work: saved drafts, queued submissions, in-progress operator sessions, and any other unsent manual work. Changing a default does not establish that existing work changed. If a pending item cannot be inspected or safely stopped, keep its path held.

For WhatsApp, approval and operational release are separate gates. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Recipient permission matters, opt-outs must be honoured, and approval does not guarantee delivery. Check the current WhatsApp Business Messaging Policy for precise requirements.

2. Separate preparation, authority, and path release

Use three decisions rather than one ambiguous instruction to “go live”:

  1. Preparation authorisation: Named owners may hold affected work, inspect pending items, update references, and prepare replacement drafts. They may not resume submissions.
  2. Effective-point decision: The release owner confirms that the replacement becomes authoritative at the stated time, provided the final gate passes.
  3. Path release: After verifier acceptance, the release owner explicitly permits a particular path to submit again.

Before preparation starts, confirm the replacement’s identity and relevant approval state, wording and variable mapping, use-point ownership, staff coverage, and stop route. Define what evidence each owner must return.

These are recommended operating controls, not claims about Alactic functionality. Check your workspace and current plan for available controls. Do not assume a CRM change updates Communications, an assisted workflow, or an Android app. Where technical restrictions are unavailable, document a supervisor-controlled hold and its limitations.

3. Filled runbook: identity, authority, and pending work

Fictional worked example: All names, identifiers, dates, times, counts, and outcomes below are hypothetical. This is a recommended workflow, not an Alactic customer result or evidence of built-in controls.

A service team is replacing a collection-notification template to clarify what recipients should have ready. Discovery found a shared selection guide, a manual sending workspace, an assisted workflow, and saved drafts. The following completed record is also a reusable artifact: retain its fields when preparing your own cutover.

Release identity

  • Record: CUT-042; evidence stored in a restricted release folder under the identifiers below.
  • Old version: collection_ready_en_r3, English, internal revision R3.
  • Replacement: collection_ready_en_r4, English, internal revision R4.
  • Release owner: Maya Chen, operations lead.
  • Implementation owners: Daniel Ortiz, manual workspace; Priya Shah, assisted workflow; Lewis Grant, guide and staff coordination.
  • Independent verifier: Aisha Bell, service quality lead.
  • Effective point: 15 September 2026, 10:00 UTC, governing new submissions within this scope.
  • Authority rule: R4 alone is authorised for new submissions after the effective point. Neither path may resume until Maya separately releases it.

Preparation and gate chronology

  • 09:10 | E01: Priya records the exact replacement reference, English language, and approved state.
  • 09:15 | E02: Aisha accepts the wording and variable mapping.
  • 09:30 | E03: Owners reconcile the discovered use points and assign verification methods.
  • 09:45 | D01: Maya authorises preparatory changes under hold beginning at 09:50, including draft replacement and workflow-reference changes. Proceeding toward the 10:00 effective point is conditional on the 09:55 gate and final reconciliation. This decision does not authorise resumed submissions.
  • 09:50: Lewis starts the hold on both affected sending paths. Unrelated work may continue. Operators must not create additional affected pending work during reconciliation.
  • 09:55 | D02: Maya accepts the pending-work inventory below and permits preparation to continue under hold. Any newly discovered work requires reconciliation before activation.

Pending-work disposition: E04

  • Three saved R3 drafts: Daniel identifies them at 09:50 and replaces them with checked, unsent R4 drafts by 09:58. Aisha verifies them under E07.
  • Two in-progress manual sessions: Operators OP-01 and OP-03 stop before submission at 09:50 and 09:51 respectively. Their unsent R3 compositions are discarded; no pending submission remains from either session.
  • Other manual work: At 09:55, Daniel reconciles the assigned workspace with all four on-duty operators. There are no additional manual drafts, queued submissions, or unsent compositions beyond the three listed drafts.
  • Assisted workflow: Priya confirms no pending or in-progress submission at 09:55; the workflow remains held while its reference changes.
  • Final reconciliation, 09:59: Daniel and Priya confirm only the three checked R4 drafts remain pending. Session dispositions are unchanged. No new pending work entered either path during the hold or final reconciliation. Lewis records operator confirmations in E04.

Had any session or queue remained unaccounted for, the affected path would have stayed held. An empty queue cannot be inferred from a changed reference.

4. Record bounded actions and individual acknowledgements

Ownership alone is not authorisation. Specify what each person may change, what remains prohibited, and what evidence closes the task.

Completed preparation actions

  • Daniel, 09:50–09:58: Replaces only the three identified unsent drafts. Does not resubmit previously submitted messages. Confirms completion at 09:58.
  • Priya, 09:50–09:58: Updates the assisted workflow reference to R4 using authorised controls, checks variable mapping, and leaves the path held. Confirms completion at 09:58.
  • Lewis, by 09:59: Updates the selection guide, collects acknowledgements, and documents the residual selection control described below.

Individual acknowledgement register: E05

Each entry records the same explicit acknowledgement: the operator can identify R4, will not select R3 for new submissions, will respect the path hold, and will stop and contact Lewis if R4 is unavailable. The underlying records are retained individually.

  • OP-01 | 09:56 | E05-A: Acknowledged; earlier session disposition recorded in E04.
  • OP-02 | 09:57 | E05-B: Acknowledged.
  • OP-03 | 09:58 | E05-C: Acknowledged; earlier session disposition recorded in E04.
  • OP-04 | 09:59 | E05-D: Acknowledged.
  • OP-05 | 11:50 | E05-E: Incoming operator acknowledged before taking affected work at 12:00.
  • OP-06 | 11:53 | E05-F: Incoming operator acknowledged before taking affected work at 12:00.

A read receipt does not establish that someone understands the selection rule. Keep an unacknowledged operator off affected work until their individual record is complete.

5. Verify each path before releasing submissions

Configuration evidence shows what a path is set to use. Observed activity shows what it actually used. Keep non-sending checks distinct from submissions, and record the release decision between verifier acceptance and resumed sending.

Completed verification and release log

  • 09:57 | E06 | Guide: Aisha verifies that R4 is identified as authoritative from 10:00 and R3 is marked retired for new submissions. Pass.
  • 09:58 | E07 | Drafts: Aisha checks all three replacement drafts against R4 wording and mapping. No unsent R3 draft remains. Pass.
  • 10:00 | D03 | Activation: Maya accepts E04’s final reconciliation and the completed on-duty acknowledgements. R4 becomes authoritative; both sending paths remain held pending their separate releases.
  • 10:01 | E08-A | Manual verification: Aisha accepts a non-sending selection check of R4 and the manual draft evidence. Pass.
  • 10:01:30 | D04 | Manual release: Maya explicitly authorises manual submissions to resume, subject to Lewis’s pre-submission selection review.
  • 10:02 | E08-B | First manual submission: OP-02 selects R4; Lewis checks the exact reference before authorising submission. Aisha records the resulting submission reference. No R3 submission occurs.
  • 10:04 | E09 | Assisted verification: Aisha accepts the active reference and a non-sending preview showing R4 with the expected mapping. The path is still held.
  • 10:05 | D05 | Assisted release: Maya authorises this path to resume. Its first subsequent submission is included in E10.
  • 10:30 | E10 | Observation: Aisha reviews all six in-scope submissions since activation. All reference R4; none reference R3. Delivery outcomes are recorded separately.
  • 12:00 | E11 | Staff coverage: Lewis reconciles the active roster against E05-A through E05-F. No unacknowledged operator handled affected work.

Store evidence where authorised reviewers can retrieve it without copying unnecessary recipient details into the runbook.

6. Control visible old versions and exceptions

Historical visibility and selectability are different. In this hypothetical workspace, R3 remains both visible in historical records and selectable for new manual submissions. The guide’s retirement label does not prevent selection.

Lewis therefore reviews every affected manual selection before submission, checking the exact R4 reference and recording acceptance alongside the submission record. If Lewis is unavailable, manual submissions stop until Maya assigns a replacement reviewer. The assisted path remains fixed to its verified R4 reference; any reference change requires a new hold and review.

This manual control remains required after cutover closure, until R3 is demonstrably unavailable for new manual selection and Aisha verifies that restriction. It has no automatic shift-end expiry. Lewis must hand the control to a named, acknowledged supervisor at each shift change.

  • R4 unavailable: Hold affected work and contact Lewis; do not silently fall back to R3.
  • Unexpected old draft: Establish whether it was already submitted. If unsent, hold and reconcile it before replacement.
  • Incorrect wording or mapping: Pause the affected path and escalate to Maya for a correction or revised release decision.
  • Uninspectable queue or session: Keep that path held rather than assuming it is clear.
  • Recipient opt-out: Stop the affected send and follow the opt-out process. Version release is not recipient permission.

Only Maya may authorise a reversal or revised effective time. A reversal requires its own suitability check, pending-work reconciliation, acknowledgements, and verification. Keep a clear human escalation route for assisted work.

7. Close the cutover without dropping residual controls

12:10 | E12 | Closure: Maya accepts E01–E11 and decisions D01–D05. Every discovered use point is verified, all active operators have acknowledged, and pending work is fully reconciled. The six reviewed submissions support R4 use during that observation period, not a guarantee about future activity.

Maya closes the migration tasks but explicitly retains Lewis’s pre-submission review while R3 remains selectable. Lewis owns the next-shift handover; Aisha must verify any later technical restriction before Maya may retire that review requirement.

For a larger operation, a defined sample may replace full submission review, but it cannot establish what happened outside the sample. Record that limitation. Before releasing any path, ask its owner which observable check would reveal continued old-version use. If there is no answer, keep that path held.

Template lifecycleWhatsApp operationsRelease management

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