Back to all articlesTemplate lifecycle

Create a Version Register That Distinguishes Approval From Release

Alactic Editorial10 min read

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

A team member finds an approved template in a shared document and assumes it is ready to use. Another finds a newer draft and assumes it replaced the old wording. Both documents look plausible because neither records the actual release decision.

Resolve this with a version register that keeps two separate fields: reported status, recording what the platform currently reports, and internal release state, recording whether your team has authorised that exact version for use. Then maintain one explicit current-version pointer for each message purpose and operating scope.

This WhatsApp template version management register can live in a spreadsheet or a shared document. It is a recommended manual operating record, not a claim that a messaging platform provides native version control. The useful result is simple: staff can identify the authorised wording without interpreting document titles, approval screenshots, or chat history.

1. Define what “current” means before adding versions

“Current” should mean the version internally released for a particular purpose and scope, not the newest file or the most recently approved submission. Approval and release answer different questions.

  • Reported status: What status does the platform show for this exact submitted template?
  • Internal release state: What has your team decided people may do with this version?
  • Current-version pointer: Which released version should staff select for this purpose?

Define the purpose narrowly enough that one answer is useful. “Customer updates” is too broad if it includes order confirmations, dispatch notices, and appointment reminders. “Order dispatch notice” is a workable logical purpose because it describes a specific communication job.

Scope the pointer by workspace or account and language where those differ. If two distinct operating workflows require different wording, name those scopes too. Otherwise, two teams may each claim a different version is current while both are looking at an incomplete record.

One current version per purpose does not mean one version for every audience everywhere. It means one unambiguous answer within a defined scope. Where there is no suitable released version, write None — do not use rather than leaving a blank cell that someone might interpret as permission to improvise.

2. Use two state fields with different rules

Copy the reported status from the actual workspace record, preserving the label shown there. Record where and when it was checked. Do not substitute an internal label such as “ready” for an external label such as “approved,” and do not present an old observation as a live status.

Use a short, deliberately defined vocabulary for internal release state:

  • Draft: Wording is being developed and is not authorised for operational use.
  • Held: The version is not authorised for use, whether it is awaiting review, needs internal checks, or has been rejected externally.
  • Released: The team has authorised this exact version for the stated purpose and scope.
  • Suspended: Use has been stopped while an issue is investigated.
  • Retired: The version is preserved for history but is no longer authorised for use.

These are proposed internal labels, not platform status names. Their value comes from consistent interpretation. An externally approved version can remain held because its variables are unclear or its operational instructions are unfinished. A previously released version can become suspended without losing the historical fact that it was approved.

Under the WhatsApp Business Messaging Policy, approved templates are used to initiate Platform conversations and outside the customer-service window, which opens or resets when a user messages the business and lasts 24 hours. Approval does not guarantee delivery. Recipient permission and opt-outs still matter. The register therefore records wording authority; it does not replace recipient checks or prove that a message can or will be delivered.

3. Build the minimum record around an exact wording reference

Create one row per version. Never reuse a version identifier, even when a revision seems minor. A changed date format or variable instruction can affect what a recipient sees, so it deserves a traceable record.

Keep these fields in the main register:

  • Logical message purpose and scope: The job the message performs and where the row applies.
  • Version identifier: A stable internal identifier, separate from the platform template name.
  • Wording reference: A fixed snapshot of the submitted wording, including relevant components and variable definitions.
  • Reported status: The observed external status, with check time and evidence reference.
  • Internal release state: The team's operational decision.
  • Owner: The person accountable for maintaining the row and resolving questions.
  • Superseded-version links: Which released version this one replaced, and which version later replaced it.

A wording reference must lead to a specific revision, not a document that quietly changes underneath it. In a manual system, a dated, read-only snapshot can be sufficient. Include the body, header, footer, buttons, and variable meanings where applicable, rather than storing only the most visible sentence.

For external matching, also record the workspace or account, template identifier or name, and language. These are lookup details, not substitutes for the internal version ID. A person finding the right name in the wrong workspace has not verified the version.

4. Filled fictional example: a register staff can use

The following is a hypothetical worked example. All names, identifiers, wording references, statuses, and dates are fictional. The example uses a document-based wording archive and a manually maintained register; it does not describe an existing product feature.

The fictional team uses the scope “Service workspace / English.” Its current-version index sits above the detailed records:

Hypothetical current-version index
Scope: Service workspace / English

Order dispatch notice → DISPATCH-v03
Appointment reminder → REMINDER-v01
Appointment cancellation notice → None — do not use

Index owner: Maya Chen
Last reconciled: 14 May 2026, 09:30 UTC

Below it, the version register contains both released and non-released records. Keeping them together is safe because each row states its release decision explicitly.

HYPOTHETICAL FILLED REGISTER
Shared scope: Service workspace / English
All reported statuses checked: 14 May 2026, 09:00 UTC
Evidence location: Status log / 2026-05-14

Purpose: Order dispatch notice
Version: DISPATCH-v01
Wording reference: Archive / DISPATCH-v01 / frozen copy
External lookup: dispatch_notice_01 / English
Reported status: Approved
Internal release state: Retired
Owner: Maya Chen
Supersedes: None
Superseded by: DISPATCH-v03

Purpose: Order dispatch notice
Version: DISPATCH-v02
Wording reference: Archive / DISPATCH-v02 / frozen copy
External lookup: dispatch_notice_02 / English
Reported status: Rejected
Internal release state: Held
Owner: Maya Chen
Supersedes: None — never released
Superseded by: None
Candidate replacement for: DISPATCH-v01

Purpose: Order dispatch notice
Version: DISPATCH-v03
Wording reference: Archive / DISPATCH-v03 / frozen copy
External lookup: dispatch_notice_03 / English
Reported status: Approved
Internal release state: Released
Owner: Maya Chen
Supersedes: DISPATCH-v01
Superseded by: None

Purpose: Order dispatch notice
Version: DISPATCH-v04
Wording reference: Archive / DISPATCH-v04 / frozen copy
External lookup: dispatch_notice_04 / English
Reported status: Pending
Internal release state: Held
Owner: Maya Chen
Supersedes: None — not released
Superseded by: None
Candidate replacement for: DISPATCH-v03

Purpose: Appointment reminder
Version: REMINDER-v01
Wording reference: Archive / REMINDER-v01 / frozen copy
External lookup: appointment_reminder_01 / English
Reported status: Approved
Internal release state: Released
Owner: Omar Patel
Supersedes: None
Superseded by: None

Purpose: Appointment reminder
Version: REMINDER-v02
Wording reference: Archive / REMINDER-v02 / frozen copy
External lookup: appointment_reminder_02 / English
Reported status: Approved
Internal release state: Held
Owner: Omar Patel
Supersedes: None — not released
Superseded by: None
Candidate replacement for: REMINDER-v01
Hold reason: Variable instructions not yet verified

Purpose: Appointment cancellation notice
Version: CANCEL-v01
Wording reference: Archive / CANCEL-v01 / frozen copy
External lookup: appointment_cancel_01 / English
Reported status: Rejected
Internal release state: Held
Owner: Omar Patel
Supersedes: None — never released
Superseded by: None

The distinction between candidate replacement and supersedes is important. DISPATCH-v02 was intended to replace v01, but it never did. DISPATCH-v03 is the actual successor. Likewise, approved REMINDER-v02 has not displaced REMINDER-v01.

A hypothetical wording snapshot for DISPATCH-v03 might contain: “Your order {{1}} has been dispatched. View the dispatch details at {{2}}.” Its accompanying instructions would define {{1}} as the order reference and {{2}} as the order-specific dispatch-details link. Those instructions belong to the version record so staff do not invent their own interpretation.

5. Make release a deliberate handover

Use a short release procedure rather than treating an approval notification as an instruction to switch. The owner prepares the record; a named release decision-maker authorises the change. Small teams may assign both responsibilities to one person, but the decision should still be recorded.

  1. Verify the match. Compare the archived wording, external identifier, language, and workspace with the actual template record.
  2. Refresh reported status. Record the observation time and evidence. Resolve discrepancies before proceeding.
  3. Check operational readiness. Verify variable instructions, intended purpose, and any human escalation instructions relevant to the workflow.
  4. Record authorisation. Add the decision-maker, effective time, and a short reason to the release log.
  5. Switch the pointer. Mark the new version released, retire the previous version, and add reciprocal supersession links in one controlled editing session.
  6. Reconcile usage locations. Check shared instructions, prepared campaign references, and any manually maintained workflow selections that relied on the old version.

The register does not itself update those other locations. Assign that work explicitly and record what remains outstanding. If a shared document cannot prevent simultaneous edits, designate one editor for the release handover and ask others to wait until the consistency check is complete.

Keep campaign preparation, template review, and actual sending separate. A campaign can be prepared while its intended version remains held, but preparation must not be interpreted as release authorisation. Equally, a released template is not evidence that a particular recipient is eligible to receive it.

6. Recover from conflicting records without erasing history

Two versions appear to be current

Pause new selection for that purpose while the owner compares the release log, wording snapshots, and current-version index. Do not resolve the conflict by choosing the highest version number. Record the correction, identify the authoritative version, and inspect the usage locations that may have followed the wrong pointer.

The external status no longer supports use

Update the reported-status evidence and suspend the affected release. If no reviewed alternative is available, change the pointer to “None — do not use.” An older approved version should not become current automatically; confirm that its wording and operating instructions are still suitable before authorising its return.

The wrong wording was used

Preserve the affected version, selection record, and relevant operational references. Stop further use while the owner establishes what happened. Separate a stale register entry from a wrong variable value or a workflow still pointing to a retired version; each requires a different correction. Use your established incident process for assessing any follow-up rather than assuming a replacement message is always appropriate.

A draft overwrote the archived wording

Treat the reference as unreliable until it has been reconciled with trustworthy evidence. Do not reconstruct it from memory and label it exact. Restore the snapshot if possible, document the gap, and change the archive practice so future edits create new revisions instead of replacing old ones.

7. Keep the register lightweight, but inspect its weak points

A single document is quick to start and easy to read, but consistency depends on disciplined editing. Separate status observations, wording archives, and release logs provide better traceability, but introduce more links to maintain. Choose the smallest arrangement in which a colleague can identify the current version and verify its wording without asking the owner.

Use controlled choices for internal release states if your document tool supports them. Limit who can change release decisions, while allowing the staff who select wording to read the record. These are operating recommendations, not assertions about controls available in a particular workspace.

Review the register when a submission changes status, when wording changes, when a release is made, and when a problem is reported. Add a recurring reconciliation appropriate to how frequently your team changes templates. A check timestamp makes stale evidence visible; it does not guarantee the external status has remained unchanged.

For a hypothetical first cleanup, choose three active message purposes. Inventory every version you can find, assign stable IDs, freeze the wording references, and publish one current pointer or an explicit no-use instruction for each. Then ask a colleague who did not build the register to identify the authorised wording and its variable instructions.

Measure the unresolved conflicts, missing snapshots, and usage locations still pointing to retired versions. The immediate target is not a larger register: it is no ambiguous current pointers in that initial scope, with every unresolved issue assigned to an owner.

Template lifecycleWhatsApp operationsVersion managementRelease controls

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