Set a Schedule Lock and Rules for Last-Minute Changes
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A late request to move a campaign is not just a calendar edit. Staff may already be assigned, inventory may be reserved, and someone may have prepared the send using the original time. If the request lives in a chat while the calendar shows something else, nobody can confidently say which instruction governs.
Set a schedule-lock point after which the agreed send time stays in force unless a named decision-maker approves an exception. Record the request, review its operational impact, and make the revised time authoritative only after the calendar and actual sending setup have been checked and confirmed. If the existing time becomes unsafe or impractical, explicitly hold the campaign rather than leaving people to infer what happens next.
This is a manual operating practice for timing changes. It does not replace campaign-content approval, determine account access, or assume that a software feature will enforce the lock.
1. Give the schedule one authoritative home
Choose one calendar entry or schedule record as the reference for the campaign's timing. Other places can link to it, but they should not become competing sources of instruction. A chat message can raise a change request; it should not silently replace the recorded schedule.
The authoritative record needs enough detail to distinguish a current instruction from an old plan:
- Campaign identifier: a stable name or reference that remains the same when timing changes.
- Send date, time, and time zone: not simply “tomorrow afternoon.”
- Timing scope: whether the time applies to the whole campaign or a named send batch.
- Lock point: the exact date and time when ordinary rescheduling ends.
- Timing status: for example, planned, locked, change pending, held, or revised and confirmed.
- Current revision: a simple reference linking the calendar to the latest timing decision.
Keep the approved plan separate from evidence that it has been implemented. The calendar states what should happen; the sending setup must be checked to establish what is currently configured. A mismatch is a problem to resolve, not a reason to assume either one is correct.
When a request is under review, retain the current locked time and add the proposed time as a clearly labelled request. Do not overwrite the current time just to show what somebody wants.
2. Place the lock before commitments become expensive to unwind
The right lock point depends on what must be rearranged if the send moves. Work backwards from the last practical opportunity to change staffing, stock allocation, support coverage, or a related operational handoff.
A lock immediately before sending may protect the calendar from edits but do little to protect operations. An unnecessarily early lock can make sensible adjustments cumbersome. Choose a point that gives affected teams enough time to respond, then test whether it works in practice.
Hypothetical rule: A business locks a campaign at 15:00 UTC on the day before its scheduled send. By then, the operations lead must have confirmed stock readiness and the support lead must have confirmed coverage. Requests arriving after that point use the exception process.
Before marking the schedule locked, the schedule owner should confirm:
- The recorded time includes a time zone and an unambiguous date.
- The affected teams have acknowledged the timing.
- The current sending setup matches the recorded plan, or any remaining setup task has a named owner and deadline.
- The primary timing decision-maker and backup are known.
- The team knows whether the existing schedule continues while a request is pending.
A schedule lock should make changes deliberate, not make a bad plan untouchable. Its value is that a request must now justify disrupting commitments already made.
3. Define exceptions narrowly enough to support a decision
Without exception rules, every late request becomes a debate about urgency. Define the circumstances that merit review, while making clear that qualifying for review is not the same as receiving approval.
Useful exception categories include an operational dependency becoming unavailable, an incident that makes the planned timing inappropriate, or a verified readiness problem that requires postponement. A request to send earlier deserves particular scrutiny because it removes preparation time rather than adding it.
Preference alone should not normally reopen a locked schedule. “A different time might perform better” is a weaker reason than “the fulfilment team cannot support the planned window.” The decision should reflect the concrete impact, not the seniority or persistence of the requester.
Require each request to contain:
- The campaign reference and current locked time.
- The proposed replacement time, including time zone.
- The reason for changing it and what happens if it stays unchanged.
- Which staffing, inventory, or related commitments could be affected.
- The latest point at which a decision can still be implemented and checked.
A narrow exception policy has a trade-off: it may reject a plausible commercial opportunity because the disruption is too large or the evidence too weak. Record that choice plainly. The aim is not to eliminate judgement but to make the cost of a timing change visible.
4. Assign decision authority and a safe fallback
Name one role that can authorise a post-lock timing change and one backup. The requester supplies the reason; affected leads report impacts; the authorised decision-maker accepts or rejects the trade-off. The schedule owner then coordinates the update and confirmation.
These can be different people without creating a full approval hierarchy. Keep this arrangement limited to timing decisions. It does not grant authority over campaign content or establish software permissions.
The decision record should distinguish three outcomes:
- Approve: accept a specific new date and time, with any conditions that must be satisfied before implementation.
- Reject: keep the existing locked schedule, provided it remains operationally viable.
- Hold: prevent the planned send while a dependency or timing conflict remains unresolved.
No reply is not approval. Set a decision deadline early enough to leave time for implementation and verification. If the deadline passes, follow the stated fallback: retain the locked time if it is still viable, or hold if a known blocker makes proceeding inappropriate.
Also designate who can call an immediate timing hold when a serious conflict is discovered. A hold is a protective pause, not permission to choose a new send time. In a manual process, someone must still check whether the send can be stopped and confirm what actually happened.
5. Use this filled schedule-control checklist
Fictional worked example: The following campaign, people, dates, times, and operational details are hypothetical. They illustrate a completed manual record, not an Alactic customer result.
Locked schedule
- Campaign: SUMMER-STOCK-16, one campaign send.
- Authoritative record: Shared campaign calendar entry SUMMER-STOCK-16, timing revision 1.
- Locked send time: 16 June 2026 at 10:00 UTC.
- Schedule-lock point: 15 June 2026 at 15:00 UTC.
- Schedule owner: Maya, campaign coordinator.
- Timing decision-maker: Elena, commercial operations lead. Backup: Sam, duty operations manager.
- Lock confirmation: Maya recorded at 15:05 UTC on 15 June that support and inventory leads acknowledged the time and that the sending setup matched revision 1.
Exception request
- Request reference: TC-17, received on 16 June at 08:10 UTC.
- Requester: Jordan, inventory lead.
- Requested change: Move the send from 10:00 UTC to 13:00 UTC on 16 June.
- Reason: The stock allocation needed for the campaign is not ready for the original window.
- Impact of no change: The campaign could generate demand before the allocation is available.
- Decision deadline: 08:45 UTC, leaving time to change and verify the setup before the original send.
- Interim instruction: Hold the 10:00 UTC send. Maya confirmed at 08:18 UTC that it was no longer pending in the sending setup.
Impact review
- Inventory: Jordan confirmed at 08:25 UTC that allocation was complete and could remain reserved through the proposed window.
- Staffing: Support lead Priya confirmed coverage at 13:00 UTC; a planned break rotation required adjustment.
- Related timing: The operations lead checked that the revised send would not conflict with another scheduled campaign.
- Implementation: Maya confirmed that the later time could be entered and checked before the decision deadline.
- Unresolved issues: None recorded at the decision point.
Authorised decision
- Decision: Approve 16 June 2026 at 13:00 UTC.
- Authorised by: Elena at 08:35 UTC, recorded against TC-17.
- Reason: Inventory readiness was confirmed and support coverage could accommodate the move.
- Fallback: If implementation cannot be verified, retain the hold and escalate to Elena; do not restore 10:00 UTC by assumption.
Updated calendar confirmation
- Calendar update: Maya entered 13:00 UTC as timing revision 2 at 08:40 UTC and retained the original time in the change history.
- Sending setup: Maya entered the revised time and checked that no separate 10:00 UTC send remained pending.
- Independent check: Priya compared the campaign reference, date, time zone, calendar time, and sending setup at 08:44 UTC.
- Final notice: “SUMMER-STOCK-16, revision 2: send time confirmed as 16 June 2026, 13:00 UTC. The previous 10:00 UTC instruction is superseded. Calendar and sending setup checked. TC-17 authorised by Elena.”
- Acknowledgements: Inventory and support leads acknowledged the final notice.
- Final timing status: Revised and confirmed. Actual delivery remains a separate outcome to establish later.
6. Close the gap between approval and implementation
The most vulnerable point is often after approval. People hear “the change is approved” and assume someone else has updated the schedule. Treat approval as permission to implement, not proof that implementation is complete.
Use a short closing sequence: record the decision, update the authoritative calendar, update the sending setup, compare them, and issue one final notice. Where practical, have a second person perform the comparison. If that is not possible, require the schedule owner to make a deliberate check against the decision record rather than relying on memory.
The final notice should include the campaign reference, new date and time zone, revision, superseded time, and confirmation that the setup was checked. Send it through the agreed operational channel and link back to the authoritative record.
Notify everyone whose arrangements changed, not just the requester. A technically correct send time can still leave staff working to the old plan. Missing acknowledgement from a critical team should be resolved before marking the timing fully confirmed.
7. Recover explicitly when the process breaks
If the calendar and sending setup disagree: treat the timing as unconfirmed. Establish whether the send is still pending and whether a hold is possible. Reconcile both records against the authorised decision, then issue a corrected confirmation. Do not guess based on which screen was edited most recently.
If the decision-maker is unavailable: use the named backup. If neither responds by the deadline, apply the recorded fallback. Escalating repeatedly in different chats should not create implied approval.
If sending has already begun: do not describe the campaign as fully rescheduled. Establish what has already been sent and what remains pending. Any decision about the remainder needs its own timing instruction; do not automatically create a replacement send.
If someone changes the time without a recorded decision: first establish the current state and prevent conflicting instructions. Then document whether the authorised decision-maker accepts the change or requires another action. Preserve the discrepancy in the record rather than rewriting history to make the process appear orderly.
8. Test the rule on the next scheduled campaign
Start with one campaign. Before its lock point, complete the authoritative timing record, name the decision-maker and backup, and write the fallback for a late request. Ask the affected leads to identify the current send time from that record without relying on chat history.
After the campaign, review observable measures: how many requests arrived after lock, how many were approved, how long confirmation took, and whether any calendar-versus-setup mismatch occurred. Also check whether staff and inventory teams received the final instruction before acting.
If exceptions are frequent, investigate the dependency causing them rather than simply tightening the rule. If requests are reasonable but cannot be reviewed in time, move the lock or improve the handoff. The useful outcome is a timing decision that people can locate, implement, and verify—not a freeze label that everyone works around.
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