{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-production-cycle-time-ledger","id":"email-production-cycle-time-ledger","slug":"email-production-cycle-time-ledger","title":"Measure Email Production Time Beyond the First Draft","description":"Separate active work, waiting and rework from total campaign elapsed time. Use a worked cycle-time ledger with documented Migma workflows and explicit evidence limits.","dek":"Separate active work, waiting and rework from total campaign elapsed time. Use a worked cycle-time ledger with documented Migma workflows and explicit evidence limits.","category":"Email Operations","topics":["Migma","email workflow","email marketing"],"publishedAt":"2026-09-15","updatedAt":"2026-09-15","lastVerifiedAt":"2026-09-15","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma: Fashion ecommerce deliverability tools","url":"https://migma.ai/blog/email-deliverability-tools-fashion-ecommerce?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-production-cycle-time-ledger"},{"title":"Migma: Prompt guide","url":"https://docs.migma.ai/creating-emails/prompt-based-creation?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-production-cycle-time-ledger"},{"title":"Migma: Email Preflight","url":"https://docs.migma.ai/email-editor/email-preflight?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-production-cycle-time-ledger"},{"title":"Migma: Export options","url":"https://docs.migma.ai/email-editor/export-options?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-production-cycle-time-ledger"}],"wordCount":763,"body":"Measure Migma email production through the accepted handoff or verified launch, not just the arrival of the first generated draft. Separate active work from waiting and rework so the team can improve the actual process without mistaking a fast generation step for a fast campaign.\n\n> **Editorial disclosure:** Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 15, 2026.\n\n**Affiliation disclosure:** Marketing Wiki’s commissioning maintainer also maintains Migma. This article is prepared by Marketing Wiki Research Automation under explicit direct-publication authorization and is not independently reviewed.\n\nMigma's [September 15 fashion-email article](https://migma.ai/blog/email-deliverability-tools-fashion-ecommerce?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-production-cycle-time-ledger) discusses production speed alongside deliverability tooling. This guide does not adopt its numerical productivity claims. We recommend measuring your own workflow with the ledger below, using documented Migma [draft creation](https://docs.migma.ai/creating-emails/prompt-based-creation?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-production-cycle-time-ledger), [Preflight](https://docs.migma.ai/email-editor/email-preflight?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-production-cycle-time-ledger) and [export](https://docs.migma.ai/email-editor/export-options?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-production-cycle-time-ledger) as observable stage boundaries.\n\n## Choose one start and one finish\n\nStart when the brief contains the approved message, audience owner, source facts and required action. Record earlier discovery separately if you need to measure it. Otherwise, a campaign with an undeveloped brief can appear slower than one whose preparation happened outside the measured interval.\n\nEnd at the outcome your team actually owns. A design team may finish when the sending owner accepts the handoff. An operations team may finish when the scheduled campaign is verified. Do not compare these two measures under the same label.\n\nWrite the scope at the top of the ledger: new promotional email, one language, established brand, final handoff acceptance. A new multi-language series belongs in a different comparison group.\n\n## A worked day in the ledger\n\nHere is a synthetic campaign day, expressed in elapsed minutes:\n\n| Interval | State | Minutes | Reason |\n| --- | --- | ---: | --- |\n| 09:00–09:20 | Active | 20 | Draft and initial review |\n| 09:20–10:40 | Waiting | 80 | Approver unavailable |\n| 10:40–11:00 | Active | 20 | Review and requested correction |\n| 11:00–11:15 | Blocked | 15 | Product fact needed |\n| 11:15–11:35 | Active | 20 | Correct, check and export |\n| 11:35–12:00 | Waiting | 25 | Sending owner accepts handoff |\n\nTotal elapsed time is 180 minutes: 60 active, 105 waiting and 15 blocked. The arithmetic was checked locally. These are invented observations, not a Migma productivity benchmark or a measurement of an actual employee.\n\nSuppose generation itself used two minutes inside the first interval. Even eliminating those two minutes would reduce the full 180-minute cycle by only about 1.1%. That does not make generation speed irrelevant; it shows why a workflow claim must name its measurement boundary.\n\n## Record transitions, not keyboard activity\n\nFor each transition, keep the campaign reference, timestamp, previous state, next state, reason and artifact revision. Record a correction as a new event that points to the mistaken event. Do not silently rewrite the history after reporting a result.\n\nA producer working on another campaign while this one waits is not idle. The ledger measures a campaign's flow, not an individual's labor utilization. Avoid using presence indicators or time with a tab open as substitutes for recorded work stages.\n\nConcurrent work also needs care. If two reviewers work for the same ten minutes, elapsed time is ten minutes while total labor may be twenty. Keep those measures separate rather than summing both into cycle time.\n\n## Find the smallest useful improvement\n\nIn the example, waiting is the largest category. Investigate whether the approval queue can be predictable or whether the brief can reach the reviewer earlier. The blocked interval suggests a missing product fact at intake. Neither observation proves that the designer should write faster.\n\nUse Migma's review and export checkpoints to attach the exact artifact under discussion. A late correction after export may indicate a missing intake fact, a changed requirement or a destination transformation. Give the loop a cause rather than labeling every return “revision.”\n\nChoose one process change for comparable campaigns and observe another period. Report the sample size, work types and unusual constraints. Pair time with defects or rejected handoffs; reducing review time while increasing errors is not an acceptable improvement.\n\n## Keep the conclusion proportional\n\nThis complements the [brief-to-send workflow](/articles/ai-email-workflow-from-brief-to-send) by adding measurement rather than a new production sequence.\n\nNo team was instrumented and no productivity reduction verified. Begin with five comparable campaigns, preserve missing intervals as missing, and decide whether the data is sufficient before claiming an improvement. The immediate value is a visible bottleneck and a testable change, not a universal speed score."}