The practical route for the query “ebook production plan” is specific: divide the first production into prep, build, and QA days by deliverable rather than by hours. The controlled case is one finished manuscript, an unfinished cover, and a three-day production card. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for prep-day source, build-day settings, QA artifact, return path, pre-release hold. The excluded range is stated separately: drafting schedules, retailer applications, and advertising.
Decision: Divide the first production into prep, build, and QA days by deliverable rather than by hours
Make the authoritative input and its state visible before work spreads across copies. The register must still identify prep-day source and pre-release hold when the next session begins.
The article-specific evidence card has these fields: prep-day source, build-day settings, QA artifact, return path, pre-release hold. Do not count the following excluded range as evidence: drafting schedules, retailer applications, and advertising.
One case, one authority, one result
Use a first-book schedule with one finished manuscript and an unfinished cover. Day one freezes source and assets; day two records metadata and order and creates one identified EPUB; day three inspects structure and reader display separately. Waiting for an asset is not completion, and defects return to source or settings rather than to a hand-edited package.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to divide the first production into prep, build, and QA days by deliverable rather than by hours. Name the source, working copy, and delivered or reopened result so that another editor can locate each one without relying on a filename such as final.
Actions to record in sequence
Use the following product-independent sequence on the named sample. It is an acceptance method, not a claim that Rune Studio has already completed this particular case.
- 1. Freeze manuscript and available assets on prep day. Attach the observed prep-day source evidence to this step.
- 2. Enter metadata and order on build day. Attach the observed build-day settings evidence to this step.
- 3. Export one uniquely named EPUB. Attach the observed QA artifact evidence to this step.
- 4. Separate package and reader checks on QA day. Attach the observed return path evidence to this step.
- 5. Return defects to source or settings and rebuild. Attach the observed pre-release hold evidence to this step.
How to mark the run
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Prep-day source — expected state: written before the run; hold the row if waiting for an unfinished asset is counted as completion.
- Build-day settings — expected state: written before the run; hold the row if reader inspection is skipped on build day.
- QA artifact — expected state: written before the run; hold the row if the generated package is hand-repaired.
- Return path — expected state: written before the run; hold the row if waiting for an unfinished asset is counted as completion.
- Pre-release hold — expected state: written before the run; hold the row if reader inspection is skipped on build day.
Stop conditions and repair routes
A second pass is meaningful only when its source and changed condition remain identifiable. Keep the earlier result and append the retest instead of replacing the failed row.
- 1. Waiting for an unfinished asset is counted as completion; return to the named source.
- 2. Reader inspection is skipped on build day; preserve the failed artifact.
- 3. The generated package is hand-repaired; change only the responsible condition.
Where Rune Studio may reduce handoffs
Current product documentation covers capabilities relevant when you need to keep manuscript, order, metadata, navigation, cover, and colophon in one production record. That scope can justify a trial, but it does not show that one finished manuscript, an unfinished cover, and a three-day production card passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you divide the first production into prep, build, and QA days by deliverable rather than by hours. Use another tool or destination check for the excluded range stated here: drafting schedules, retailer applications, and advertising.
Conclusion
For the search phrase “ebook production plan,” the conclusion is to divide the first production into prep, build, and QA days by deliverable rather than by hours. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for prep-day source, build-day settings, QA artifact, return path, pre-release hold.
Begin here: write one deliverable for each of the three days. If waiting for an unfinished asset is counted as completion, stop at that row and return to its source. Check the Rune Studio product page for the current Mac feature scope before applying the same acceptance card to a product trial.
