Decide When a Template Change Needs a Separate Version
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A corrected spelling mistake should not create the same review burden as a changed delivery promise. But treating both as routine edits can leave a team unable to establish what a customer was told or which workflow supplied the message data.
Create a separate internal template version when a change affects meaning, customer expectations, the interpretation of variables, or how another process uses the template. Keep genuinely cosmetic corrections within the existing version only if the previous wording remains recoverable. Every saved change needs history; not every saved change needs a separate operational version.
This is an internal classification decision, not a ruling about WhatsApp editing or review requirements. An internal label such as “minor correction” does not determine whether a platform edit is permitted or whether review is required.
1. Separate the wording record from the operational version
Two records solve different problems. A revision record preserves exactly what changed. An operational version identifies a message contract that people and workflows can deliberately select, review, and retire.
The message contract includes more than the visible sentence. It also includes what each variable means, the intended recipient situation, the linked destination, and any commitment or offer the recipient may act on.
A useful internal structure therefore has three layers:
- Template family: the continuing purpose, such as an order-status notification.
- Operational version: a particular meaning and usage contract within that family.
- Revision: a recorded correction that does not change that contract.
These are recommended recordkeeping concepts, not claims about fields or controls available in a particular product. A controlled register can hold them if the messaging workspace does not.
Use a separate family when the purpose is genuinely different, rather than merely creating another version of an unrelated message. For example, an order update and an optional promotional offer should not share a family solely because both mention the same product. That is an internal taxonomy choice; platform classification still needs its own assessment.
2. Apply four tests before choosing the review path
Read the old and proposed text side by side, then answer the following questions. Do not classify the change by character count: a single changed word can reverse an obligation.
- Meaning: Would a reasonable reader understand a different fact, instruction, condition, or level of certainty?
- Customer expectations: Could the change alter what someone expects to receive, pay, do, or wait for?
- References: Would an earlier message, support explanation, linked document, or recorded approval become misleading if it pointed to the new wording?
- Downstream use: Does a variable, selection rule, audience rule, button, destination, or workflow dependency need different handling?
A “yes” usually calls for a separate operational version. A “not sure” calls for investigation, not automatic treatment as a small edit. The editor should identify the person who can resolve the uncertainty: for example, an operations owner for a delivery promise or a data owner for a variable.
If all answers are “no,” a correction within the current version may be appropriate. Still preserve the prior text, the reason for the edit, and who checked it. Without that record, “we only fixed a typo” becomes an assertion nobody can verify later.
3. Use a filled change-classification table
Fictional worked example: The following messages, version labels, amounts, and timings are hypothetical. The table shows internal decisions only; it does not predict platform editing or review outcomes.
The team uses “R” for a wording revision and “V” for an operational version. Those labels are illustrative, not a required naming convention.
Change Meaning / expectation References / downstream Internal decision Corrected typo Unchanged Unchanged Keep V1; record R2 Revised commitment Changed Support guidance affected Create V2 Changed variable May appear unchanged Data contract changed Create V2 Altered offer Changed Offer rules affected Create V2
Corrected typo: retain the version, preserve the revision
Before: “Your order has been dispacthed.”
After: “Your order has been dispatched.”
Classification: spelling correction only. The event, recipient action, and degree of certainty remain the same. No variable or destination changes.
Decision and rationale: retain internal V1 and record R2. A separate selectable version would add clutter without representing a different message contract.
Review path: a designated copy reviewer compares the complete messages and confirms that only the spelling changed. Record the old text, corrected text, reason, reviewer, and effective point. If the organisation requires an independent check, the editor should not self-approve.
Revised commitment: create a separate version
Before: “We aim to dispatch your order within three business days.”
After: “We will dispatch your order within two business days.”
Classification: both certainty and timing have changed. This is not a stylistic shortening: the new text sets a different customer expectation.
Decision and rationale: create internal V2. Preserve V1 so support can distinguish the earlier target from the later commitment.
Review path: the operations owner verifies the proposed promise and its intended scope; the messaging owner checks wording and selection rules. Check whether queued communications should retain the old version or be reassessed. Do not silently apply the new promise to every existing case.
Changed variable meaning: version the data contract
Before and after visible text: “Your order update: {{1}}.”
Old variable meaning: {{1}} contains a dispatch date.
New variable meaning: {{1}} contains an estimated arrival date.
Classification: the visible wording is unchanged, but the information supplied has a different meaning. A previous producer may still supply a dispatch date even if a new reviewer expects an arrival date.
Decision and rationale: create internal V2 and define its input explicitly. Consider replacing the vague wording with a clear description of the date rather than relying on hidden documentation.
Review path: the data owner checks the source and meaning of the value; the workflow owner checks every producer; a reviewer checks rendered messages with representative fictional inputs. Release only when the intended meaning is consistent across wording, documentation, and data preparation.
Altered offer: preserve the offer customers received
Before: “Use code RETURN10 for 10% off your next order.”
After: “Use code RETURN15 for 15% off orders over £50.”
Classification: the benefit, code, and eligibility condition have changed. The new offer is not simply a better-formatted description of the old one.
Decision and rationale: create internal V2. Keep V1 available as historical evidence, not as an automatically reusable campaign option.
Review path: the offer owner checks the benefit and conditions; the messaging owner checks audience selection and destination consistency. Confirm that support can identify which offer a recipient received. Permission and opt-out handling remain separate checks, not consequences of the version number.
4. Route reviews by the risk that changed
A new version does not need every department to review everything. It needs reviewers who can validate the changed contract. Use a short change note to make the review specific:
- Changed: the exact wording, variable definition, destination, or usage rule.
- Why it matters: the expected difference for the recipient or downstream process.
- Dependencies: the known workflows, guidance, and scheduled activity that refer to it.
- Evidence needed: what the reviewer must inspect before agreeing.
- Release decision: who authorises operational use after the necessary checks.
For a spelling correction, evidence may be a clean comparison of the full text. For a variable change, it should include input definitions and rendered examples. For an offer, it should include the destination and applicable conditions. Review the actual changed risk rather than asking for an unexplained approval.
Translations deserve the same treatment. A source-language punctuation edit may be cosmetic, while a translated revision changes certainty or eligibility. Do not assume every language inherits the source version’s classification without checking the meaning.
5. Keep internal decisions separate from platform status
Record internal readiness and platform status separately. A team may agree that a new version is correct while the template is not yet ready for its intended platform use. Conversely, an approved template may be operationally unsuitable because its offer expired or its variable mapping is wrong.
WhatsApp Platform uses approved templates to initiate conversations and for messages outside the customer-service window. That window opens or resets with a user message and lasts 24 hours. Recipient permission and opt-outs also matter. Check the current WhatsApp Business Messaging Policy for the precise requirements that apply.
Before changing or replacing a platform template, verify the current editing and review guidance and the relevant workspace capabilities. Do not infer requirements from an internal designation such as V2 or R2. If relying on workspace features, confirm their availability in the current plan.
Keep campaign preparation, template review, and actual delivery as separate states. Template approval does not guarantee delivery. An internal release decision should therefore identify what is ready, what remains pending, and what may actually be used—not collapse all three into a single “approved” label.
6. Preserve references without leaving every version active
Keeping history does not mean leaving every old version available for routine selection. Historical records and selectable operational options serve different purposes.
For each released version, preserve the final wording, variable definitions, intended usage, review decision, effective period, and replacement relationship. Where your records support it, retain enough information to connect a sent communication to the wording and values used at that time. If the messaging system does not retain this relationship, define a separate controlled record rather than assuming it exists.
Before retiring a version, inspect its known references:
- Scheduled or queued communications that may still select it.
- Workflow rules or manual instructions that name it.
- Support guidance that explains its promise or offer.
- Linked destinations and documents that must remain intelligible.
- Reporting that groups results by template identity.
A replacement relationship is not an instruction to redirect every reference automatically. Historical reporting should continue to identify the old message. Future selection rules may need deliberate migration. If old and new versions coexist, document their respective use cases and assign an owner to end the overlap.
7. Recover when a change was classified incorrectly
The most damaging mistake is overwriting a meaningful change and later discovering that different customers received different promises under the same internal identity. Stop further use of the uncertain wording where possible, preserve the records still available, and reconstruct the affected period. Do not manufacture missing history.
Create a distinct version for future use, then identify the workflows and communications that need review. If a customer-facing clarification is necessary, have the relevant owner decide its content and scope using the records available. Merely reverting the template does not resolve expectations already created.
The opposite mistake is version sprawl: every punctuation edit becomes another selectable option. To recover, group cosmetic revisions under their stable operational contract while preserving the original records. Mark redundant options as unavailable for new use where the workflow permits, and update selection guidance. Do not erase identifiers needed to explain earlier activity.
Also avoid blindly restoring an old version after a data change. An earlier message may be incompatible with the current variable producer. Recovery should restore a compatible combination of wording, input definitions, and usage rules—not just familiar text.
8. Test the rule on your next batch of changes
Start with a bounded pilot rather than renaming the entire catalogue. As a hypothetical exercise, take the next ten proposed edits and classify each with the four tests before anyone changes the live wording.
- Have the editor record the proposed class and rationale.
- Have a second reviewer independently check the classification.
- Resolve disagreements by naming the changed meaning, expectation, reference, or dependency.
- Record the chosen version path, required reviewers, and release conditions.
- After use, check for wrong-version selection, unresolved references, and missing history.
Measure classification disagreements, edits with recoverable prior wording, and changes whose dependencies were checked before release. Also record cases where a supposedly cosmetic edit later required a new version. These observations reveal whether your rules are too loose or unnecessarily strict.
The immediate deliverable is a small change register with a decision, rationale, owner, and review path for each edit. If a reviewer can explain why a typo stayed within a version while a variable change did not, the team has a workable rule—not merely a naming convention.
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