Map Dependencies Before Replacing an Approved Template
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
The replacement template is ready, but the staff procedure still names the old version. A saved message selection list may contain it too. An authorised workflow could reference it without anyone remembering who configured that step. Replacing the template before resolving these dependencies can leave different parts of the operation following different instructions.
Before authorising replacement, build a bounded dependency inventory: identify the old template precisely, inspect the places your team uses to select or reference it, and give every known use an owner and a migration decision. Record what you could not inspect as explicitly as what you found. A search with no results is not proof that no dependency exists.
The practical goal is a reviewable decision: each known dependency will be migrated, retired or temporarily retained under a named owner, while unresolved uses block the affected part of the change.
1. Define exactly what is being replaced
Start with a small identity record for the old template and its proposed replacement. Use the most stable identifying reference available in your workspace, alongside the readable name and language. A name alone may be ambiguous, especially when staff use nicknames or several versions have similar wording.
Record the purpose of the change as well. Replacing wording while preserving the same operational purpose is different from introducing a message that asks the recipient to take a new action. Dependencies may remain technically selectable while becoming operationally wrong.
- Old template: exact name or reference, language and intended use.
- Replacement: exact name or reference, language and current review status.
- Behavioural difference: changed wording, required values, destination or recipient action.
- Change boundary: which team, workspace and operating process are included.
- Decision owner: the person authorised to approve the bounded replacement.
Do not treat approval status as evidence that the migration is complete. Template review, campaign preparation and actual delivery are separate states. 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 the user messages the business and lasts 24 hours. Recipient permission and opt-outs still matter; approval does not guarantee delivery.
2. Bound the search before collecting references
A useful inventory states where the team looked. Otherwise, “we checked everything” can mean one person searched a shared folder while another assumed the workspace had already been inspected.
Split discovery into three surfaces:
- Operating instructions: staff procedures, onboarding notes, checklists and handover documents that tell someone when or how to use the template.
- Saved references: message selection lists, shared reference sheets, saved preparation records and other places from which staff choose a message.
- Authorised workflows: configured processes that reference the template, where such functionality is available and the reviewer has permission to inspect it.
Check your workspace and current plan for the availability of relevant lists, workflow settings and inspection options. Do not assume dependency discovery is automatic or that one product surface exposes references held elsewhere. If a reviewer cannot access an area, ask its authorised owner to inspect it and provide a finding; do not work around access controls.
For each surface, record the location inspected, the reviewer, the inspection date and any exclusions. Define a cutoff for the inventory and ask owners to route new references through the change owner until replacement is complete. This keeps a bounded search from becoming stale while people continue adding uses of the old template.
3. Search for meaning as well as the template name
Search exact references first, then likely aliases and task language. A procedure may say “send the collection reminder” rather than naming the template. A selection list may display a friendly label while storing another reference underneath.
Ask the people who perform the task to show how they choose the message. This can reveal a dependency that a document search misses: an old bookmark, a copied checklist or an instruction passed along during handover. Record only what you can locate or substantiate. A remembered use without a confirmed location belongs in the unresolved list, not among verified findings.
For every match, ask:
- Does this item actually select or invoke the old template, or merely mention it historically?
- Who uses it, and who can change it?
- Does it rely on particular values, wording or a recipient response?
- Would replacing the reference preserve the intended task?
- How will the owner demonstrate that the dependency has been resolved?
Separate live instructions from historical records. An archived incident note may need to retain the old name so the record remains understandable. It should not automatically be rewritten just because it appears in search results.
4. Use a filled dependency map, not a list of names
Fictional worked example: All names, references, roles and findings below are hypothetical. This example illustrates a recommended operating record, not a claim about available product controls.
A fictional service team is replacing collection_ready_v1 with collection_ready_v2, both in English. In this example, the replacement has been approved. The old message asks the recipient to reply to arrange collection; the replacement asks them to reply with a preferred collection day. The team must therefore check both message selection and staff handling instructions.
Map header: Scope is the service team's shared operating folder, its message selection list and its authorised collection-notification workflow, where accessible. The operations lead owns the replacement decision. Personal copies and another team's workspace have not been inspected and are recorded as exclusions.
Dependency A: staff procedure
- Location and link to old template: Shared procedure “Notify a customer that an item is ready,” message-selection step, explicitly names
collection_ready_v1. - Owner: Service supervisor.
- Finding: The procedure tells staff to handle any reply as a general collection enquiry. It does not explain how to record a preferred day.
- Decision: Migrate the instruction and response-handling guidance together.
- Replacement check: The supervisor reviews the revised procedure; a staff reviewer follows it in a walkthrough and identifies the replacement plus the correct handling of the requested reply.
- Current state: Draft revised; walkthrough pending. This dependency is not closed.
Dependency B: message selection list
- Location and link to old template: Shared “Collection messages” list, entry labelled “Ready for collection,” points staff to
collection_ready_v1. - Owner: Messaging coordinator.
- Finding: The friendly label does not distinguish the old and replacement messages.
- Decision: Replace the active entry and remove the old entry from the team's routine selection guidance, using whatever controls are actually available.
- Replacement check: A reviewer checks the underlying reference and message preview, not just the visible label, and confirms that required values match the intended task.
- Current state: Update prepared; publication held until the procedure is ready.
Dependency C: authorised workflow, where available
- Location and link to old template: The hypothetical workspace contains an authorised “Collection notice” workflow whose message step references
collection_ready_v1. Availability and access have been confirmed in this example. - Owner: Workflow owner with authority to inspect and amend that process.
- Finding: The old step's supplied values must be compared with the replacement's requirements. Existing authorisation is not assumed to cover a changed customer request.
- Decision: Hold the affected workflow change until the owner confirms value compatibility and obtains the required authorisation for the revised use.
- Replacement check: Inspect the configured reference and values through permitted review or testing options; verify that replies can reach a named human escalation route.
- Current state: Blocked pending owner review. No automatic execution is assumed.
Additional finding: An archived handover note mentions the old template. The operations lead decides to retain it as history, with a clear indication that it is not current operating guidance. A reported personal checklist remains unverified and has an assigned follow-up owner.
5. Give each dependency a decision and a closure condition
“Found” is not a migration decision. Use a small set of explicit outcomes:
- Migrate: Change the reference and any dependent instructions. Close only after the owner supplies the agreed replacement evidence.
- Retire: Stop using the dependent item. Confirm that staff no longer rely on it for the active process.
- Retain temporarily: Keep the old use for a stated reason, with an owner and review trigger. This is a deliberate split state, not a completed replacement.
- Retain as history: Preserve a non-operational reference without presenting it as current guidance.
- Unresolved: The use, location or owner is not yet confirmed. State which part of replacement it blocks.
Owners should be people who can resolve the dependency, not merely people who discovered it. Where amendment and approval belong to different roles, record both.
Evidence should match the risk. A document dependency may close with a reviewed revision and walkthrough. A workflow dependency needs confirmation of its actual reference, required values and authorisation. Requiring the same evidence for every item adds work without necessarily improving the decision.
6. Authorise a bounded switch, not an unsupported clean sweep
Before the switch, review the map as a whole. Are all active uses in scope resolved? Are temporary exceptions compatible with keeping the old template available? Is any excluded area likely to use the same old reference?
The trade-off is between search completeness and an indefinitely delayed change. You do not need an unprovable claim that no reference exists anywhere. You do need a defensible boundary, named owners and an explicit treatment of uncertainty.
If one team is ready and another remains unresolved, consider a staged change only if the uses can actually be separated. Do not retire a shared old template while an authorised use still depends on it. If separation cannot be established, hold the replacement decision rather than hiding the conflict in a checklist.
In the fictional example, the operations lead cannot yet authorise complete replacement: the procedure walkthrough is pending and the workflow dependency is blocked. Preparing the selection-list update does not remove either blocker.
7. Check for drift and recover without guessing
After an authorised change, revisit the same surfaces used for discovery. Check that published instructions, active selection references and inspected workflow references agree. A changed label with an unchanged underlying reference is a failed migration even if the list looks correct.
Use task-level observations: can staff identify the intended message, supply the required values and handle the reply as instructed? Where a controlled test is available and authorised, distinguish successful configuration or preparation from actual delivery. Do not send test messages to recipients without the necessary permission.
If a missed dependency appears, add it to the map immediately. Assign an owner, identify the affected process and stop further replacement steps in that area until the conflict is understood. Do not blindly restore the old reference: first confirm that the old template remains available and appropriate for the use. If neither version can be used safely for the intended task, route the work to the designated human owner.
A missed dependency is also evidence that the search boundary needs adjustment. Inspect adjacent instructions or references of the same type rather than repeating the entire search without a reason.
8. Make the next review measurable
Open a shared record and fill the identity header before changing any reference. Then ask each surface owner to return either dependency rows or a scoped “none found” result, including where they looked and what they could not inspect.
At the authorisation review, report the counts of known dependencies by decision, unresolved owners, uninspected surfaces and closure checks still pending. These counts describe the inventory; they do not prove universal coverage.
The immediate completion test is concrete: every known operational use has an owner, a migration decision and a replacement check, and every remaining uncertainty has a stated effect on the switch. That gives the approver a basis for authorising replacement—or a precise reason to wait.
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