Separate the messages from the recipient records
This original illustrative campaign has two planned messages for an already authorized attendee list. The demonstration contains no email addresses. Its event and message details are fictional preparation inputs, not a real campaign or a legal-compliance determination.
Message M1: A preparation reminder with a confirmed materials page in the fictional source packet. The subject and body still need approval.
Message M2: An arrival reminder that needs a venue destination. The venue URL is [PENDING], so its directions cannot be checked yet. Approval is also unrecorded.
The planned send windows and time zone remain [TEAM TO SUPPLY] for both messages. Do not turn an approximate “before the workshop” into a specific send time without the team's input. The GoodDay campaign planning description separates ownership, timelines, dependencies, and campaign states; this readiness schedule is an original adaptation of that preparation task.
Give each message a separate readiness row
| Check | M1: preparation reminder | M2: arrival reminder |
|---|---|---|
| Audience definition | Authorized attendee-list reference; recheck current campaign selection in sending platform. | Same definition; confirm whether any exclusions differ. |
| Event facts | Compare date/time and materials instructions with source packet. | Compare date/time, venue and arrival instructions with confirmed event record. |
| Subject/body | Draft needed; approval unrecorded. | Draft needed; leave venue-dependent text unresolved. |
| Destination | Materials-page destination supplied in fictional packet; actual link check still to record. | Venue URL pending; destination check blocked. |
| Approver | [NAME AND DECISION TO CONFIRM] | [NAME AND DECISION TO CONFIRM] |
| Planned send window | [DATE, TIME, ZONE TO SUPPLY] | [DATE, TIME, ZONE TO SUPPLY] |
| Current status | Planned; not sent; not ready for approval-free release. | Planned; not sent; venue and approval unresolved. |
Use source references and actual check results in the working schedule. “Link supplied” is different from “destination opened and content verified.” Keep that distinction even when the body draft looks finished.
Work back from each agreed window
Once the team supplies a window, set a draft handoff, event-fact check, destination check, proof/test review in the existing sending workflow, and approval checkpoint before it. Assign each task to a role and confirm the actual time available. Do not invent a universal number of days for these tasks.
M1 can progress through a materials-link check while its content is reviewed. M2's venue-dependent review must wait for the actual destination, or an authorized content change that removes the unresolved claim. Copying M1's green status onto M2 would conceal that dependency.
Record planned, ready for platform setup, scheduled, and sent separately. Use scheduled or sent only when the existing sending system supplies that evidence. A calendar target is neither a scheduling confirmation nor a delivery result.
Make the readiness decision explicit
Ask: “Which exact message version, audience selection, destination evidence, and approval permit the next step?” If the answer has a blank, name the owner of that unresolved input and the next check. Keep recipient details in the authorized platform rather than copying them into a review page.
Do not add open rates or clicks to this preparation example. Those results require actual campaign data with defined periods and denominators; they cannot be inferred from a schedule.
Copy an operational planning prompt
Draft an email campaign preparation schedule in US English.
Campaign and distinct message purposes: [inputs]
Authorized audience definitions/references, without addresses: [inputs]
Confirmed event/content facts and source references: [inputs]
Message assets and destination links with actual check status: [inputs]
Planned windows with date/time/time zone: [inputs or unknown]
Task owners, approvers, and approval evidence: [inputs]
Existing sending-system record format: [format]
Create a separate message readiness row and preparation handoffs for drafting, factual checks, destination checks, proof/test review, approval, and authorized platform setup. Show prerequisite evidence and unresolved gaps. Use only supplied windows/time zones; distinguish planned from ready, scheduled, and sent. Require platform evidence for scheduled/sent claims. A shared campaign label must not copy one message's readiness onto another.
Do not invent audience authorization, addresses, event facts, URLs, approvals, sends, delivery metrics, or compliance conclusions. Retain [PENDING] and use [NEEDED: input] for gaps. Return a review schedule, not a sending automation. Any optional HTML copy is sanitized and dated; no sending, synchronization, address collection, or automatic tracking.
Resolve the venue destination and record each approval before moving its message to the next step. Perform actual scheduling and sending in the authorized platform, keeping the message version, audience selection, window, and evidence together in that system.
Optional: inspect a sanitized readiness sheet in NOS
NOS can save and render a prepared HTML comparison of M1 and M2 without recipient data. Use that optional review to see why the arrival reminder still has an open prerequisite; retain sending, audience, and approval records in their authoritative tools.