Stack Planning
Part of Marketing technology roadmaps
Sequencing tool changes around campaign commitments
Plan marketing tool changes around committed campaigns with preparation, cutover and decision points that protect live work.
Schedule a tool change backwards from the campaign work it could affect. Identify the last point at which the existing route must remain dependable; then reserve time to prepare, check and, if necessary, defer the new route. A launch date is a constraint on the change, not a reason to skip its checks.
Mark the commitments before choosing a cutover
Put confirmed sends, content releases, paid-media changes and reporting deadlines on one calendar. For each, ask which system creates the work, which acts on it and who receives the result. Include the period before launch when audiences, approvals or creative are being finalised. A campaign can depend on a tool well before its public launch date.
Classify a proposed change by its effect. A change to an unused reporting view may be easy to schedule during a campaign. Replacing the system that holds its approved audience or scheduled messages needs a closer continuity plan. Ask the campaign owner to state the latest acceptable time for a corrected record, approval or report to arrive.
Campaign Commitment Timeline with Change Preparation
- Finalise Audience & Creative
- Before campaign launch
- Paid-Media Changes Implemented
- 3 days prior to launch
Work backwards from the decision point
Use these checkpoints for each affected campaign:
| Checkpoint | Question for the owner |
|---|---|
| Prepare | Are the required records, roles, definitions and connected systems understood? |
| Rehearse | Has the proposed route been checked with safe normal and exception cases? |
| Decide | Is there enough time to correct a failure before committed work is due? |
| Cut over | Is each scheduled item or automation active in only the intended route? |
| Observe | Can the receiving team verify the result and report a problem? |
Set an internal decision point before the campaign’s final preparation begins. If a critical check is incomplete then, either narrow the change or keep the established route for that campaign. Record who makes that call. A date on a project board does not replace the decision.
Key Metrics for Successful Cutover Planning
- Decision Point Before Launch
- Mandatory internal review
- System Downtime Risk
- Avoid during active campaigns
Handle work already in motion
List drafts, approvals, queued sends, active automations and reports that span the proposed cutover. Assign each item to the old or new route. If both systems must run during a transition, state which one may publish or send and which is available only for checking or retrieval. Set a way to detect a duplicate or missing action as early as possible, and name who will respond.
Consider a hypothetical product launch with an email already approved and a new audience tool still awaiting a correction check. The campaign owner may keep that send on the established route, complete the audience check after launch and move a later campaign. That choice preserves the committed send while leaving the technology change open; it does not establish that the old route is suitable indefinitely.
After cutover, ask the receiving team to inspect the promised output: the published item, delivered hand-off or usable report. Close the change only when its owner has recorded the result, unresolved exceptions and who will handle the next campaign.
