{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/seasonal-email-critical-path","id":"seasonal-email-critical-path","slug":"seasonal-email-critical-path","title":"The Critical Path Behind a Seasonal Email Deadline","description":"Work backward from a seasonal email’s approved send date, model parallel dependencies, and calculate slack before shortening Migma creative work that is not the bottleneck.","dek":"Original seven-workday dependency network with one day of creative slack.","category":"Email Operations","topics":["Migma","email marketing","Campaign planning"],"publishedAt":"2026-10-07","updatedAt":"2026-10-07","lastVerifiedAt":"2026-10-07","readingMinutes":5,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma seasonal planning editorial","url":"https://migma.ai/blog/bfcm-email-campaign-planning-timeline?utm_source=marketingwiki&utm_medium=referral&utm_campaign=seasonal-email-critical-path"},{"title":"Migma Visual Canvas","url":"https://docs.migma.ai/creating-emails/visual-canvas?utm_source=marketingwiki&utm_medium=referral&utm_campaign=seasonal-email-critical-path"},{"title":"Migma campaign sending","url":"https://docs.migma.ai/campaigns/send-campaign?utm_source=marketingwiki&utm_medium=referral&utm_campaign=seasonal-email-critical-path"},{"title":"Migma Email Preflight","url":"https://docs.migma.ai/email-editor/email-preflight?utm_source=marketingwiki&utm_medium=referral&utm_campaign=seasonal-email-critical-path"}],"wordCount":807,"body":"Affiliation: Marketing Wiki's commissioning editor maintains Migma. Put the Migma creative work inside a dependency plan, then calculate which unfinished task controls the seasonal send date. Finishing a draft earlier helps the deadline only when creative work is on the critical path or enables a dependent task to start.\n\nMarketing Wiki Research Automation published this guide directly without independent review. Sources were checked on October 7, 2026. Every duration below is a synthetic planning assumption, not a measured production time or recommended universal schedule.\n\n## A calendar entry is not a dependency plan\n\nMigma's [October 6 seasonal-planning editorial](https://migma.ai/blog/bfcm-email-campaign-planning-timeline?utm_source=marketingwiki&utm_medium=referral&utm_campaign=seasonal-email-critical-path) raises the problem of working backward from a campaign date. This article uses that reader problem without adopting the vendor's numerical outcomes or copying its week-by-week timetable.\n\n[Migma's Visual Canvas](https://docs.migma.ai/creating-emails/visual-canvas?utm_source=marketingwiki&utm_medium=referral&utm_campaign=seasonal-email-critical-path) provides documented places to compare emails, keep references and review comments. Use the intended email and current version as the creative artifact on the plan. The plan itself may live in your team's project board; the cited guide does not promise an automatic critical-path calculator.\n\nA fictional outdoor-equipment shop has one seasonal membership offer and a fixed approved send day. The team needs approved offer facts, reviewed creative, an eligible audience, destination setup and final checks. Calling all of those “email production” hides which owner can actually unblock the send.\n\n## Model work that can genuinely run in parallel\n\nFor this example, the accepted brief takes one workday. After it is ready, creative takes two workdays and audience preparation takes three. Destination setup starts only after both finish, followed by final review and a deliberate buffer.\n\n```text\nAccepted brief: 1 day\n    ├─ Migma creative: 2 days ────────┐\n    └─ Audience preparation: 3 days ─┤\n                                     ↓\nDestination setup: 1 day → final review: 1 day → buffer: 1 day → send\n```\n\nAssume separate owners can do the parallel work. If one person owns both tasks and cannot overlap them, the network must change. Also assume the sending domain is already ready; an unresolved domain dependency cannot be hidden inside the buffer.\n\nThe planned duration is 1 + max(2, 3) + 1 + 1 + 1 = seven workdays. Simply adding every task would give nine and miss the assumed overlap. Assuming everything can overlap would miss the actual join before destination setup.\n\n## Work backward and expose slack\n\nLet D0 be the approved send day and D−1 the preceding working-day boundary. These are offsets on the team's working calendar, not calendar dates. Account for holidays, absences and handoff availability before converting them into dates.\n\n| Task | Duration | Latest start | Latest finish |\n| --- | --- | --- | --- |\n| Accept brief | 1 day | D−7 | D−6 |\n| Prepare audience | 3 days | D−6 | D−3 |\n| Review Migma creative | 2 days | D−5 | D−3 |\n| Configure destination | 1 day | D−3 | D−2 |\n| Final review | 1 day | D−2 | D−1 |\n| Buffer | 1 day | D−1 | D0 |\n\nCreative could start at D−6 when the brief finishes, but its latest start is D−5. That gives one day of slack under these assumptions. Audience preparation has no such slack: starting it one day late consumes the same day elsewhere or moves the send.\n\nThe critical chain is brief, audience, destination, final review and buffer. Shortening creative from two days to one would not shorten the seven-day plan while the audience branch still takes three. This is arithmetic for the stated network, not a claim that Migma has a particular production speed.\n\n## Replace estimates with evidence at each join\n\n[Migma's campaign guide](https://docs.migma.ai/campaigns/send-campaign?utm_source=marketingwiki&utm_medium=referral&utm_campaign=seasonal-email-critical-path) documents reviewing the selected email, eligible recipients, sender and timing. A completed creative branch should supply the exact reviewed email. A completed audience branch should supply the intended consent-based selection, not merely a list name.\n\nRun [Email Preflight](https://docs.migma.ai/email-editor/email-preflight?utm_source=marketingwiki&utm_medium=referral&utm_campaign=seasonal-email-critical-path) on the finished creative and resolve the relevant findings. Preflight supports review; it does not guarantee inbox placement or approve an offer. If a material edit follows, refresh the affected checks rather than carrying an earlier pass across the change.\n\nAt the destination join, record the two accepted inputs and owner. If either remains uncertain, keep the join blocked. Do not mark destination setup complete just because a draft campaign exists.\n\n## Change scope where the network permits it\n\nIf the audience task slips, consider an already approved, eligible audience only through its owner's decision. If additional creative variants add a new review dependency, redraw the network before promising the original date. Keep final review in the plan rather than quietly replacing it with the buffer.\n\nThe separate [cycle-time ledger](/articles/email-production-cycle-time-ledger) measures what actually happened afterward. Start this planning exercise with one campaign, six task rows and named owners, then update the critical path whenever a dependency or duration changes."}