Test project duplication with disposable material before adapting an important book. Identify which text, assets, settings, and records are copied and which remain shared. Make a controlled change in the duplicate, inspect the original, and verify both exports. A new project name alone does not establish that every dependency is independent.
Define what the new edition needs to inherit
List the parts of the existing project that should carry forward: manuscript structure, approved artwork, reusable styles, source records, and relevant production settings. Then identify what must become independent, such as a revised title block, changed chapter content, or a different image placement. The desired relationship is a design choice, not something to leave to the duplication command's default behavior.
Keep publication identity decisions separate from the software test. Creating a project copy does not determine the appropriate KDP edition or update route. This test establishes how the authoring tool handles source material. Confirm publication setup requirements through the relevant current guidance when the new book or edition is ready to be planned.
Build a small disposable project with realistic dependencies
Create a test project containing a few paragraphs, a named style, an image, a caption, and a simple navigation reference. Add other features your real workflow depends on, such as a linked external asset or a source note. Use material you can safely modify and discard. Do not begin the experiment by changing the only approved copy of a production manuscript.
Record the initial files and their relationships. Note whether images are embedded, linked from a folder, or managed through a shared library according to the tool's actual behavior. Include a recognizable marker in the test text and image label so later changes are easy to trace. Preserve an export of the starting state for comparison.
Duplicate the project through the supported workflow
Use the application's documented duplication or copy process and record the options chosen. Inspect the new project's contents rather than relying only on its appearance in the project list. Confirm that the expected chapters, assets, styles, and notes are present and that the name clearly distinguishes the test copy from the original.
Check references outside the project itself. A duplicated layout may still point to an asset in a shared folder, or a copied document may still link to the same companion resource. Shared dependencies are not automatically wrong, but they need to be intentional. Record which resources remain common and what an edit to each could affect.
Make controlled changes and inspect both projects
Change one ordinary paragraph in the duplicate, then reopen the original and inspect the corresponding passage. Repeat with a relevant style or asset using a bounded test. If a shared resource is involved, observe the effect in both projects and compare it with the documented behavior. Do not infer independence for all elements from one successful text edit.
Restore the test state or use separate test copies between changes when needed to keep the results understandable. Record what changed, where it appeared, and which dependencies explain the result. If the behavior is unclear, resolve it before applying the process to the real book. A surprising shared change is a useful test finding, not something to conceal by renaming the output files.
Verify exported outputs and handoff contents
Export the original and duplicate under distinct filenames and open both results. Check that the intended text, images, and settings correspond to the correct project. Confirm that one export did not overwrite the other through a remembered destination. Include any editable handoff package the workflow requires in the same inspection.
Review carried-over publication details and labels. A new edition may inherit an old title, description, release note, or internal version marker even when its main text has changed. Record which fields need explicit revision before the project can become a release candidate. The duplication feature should save setup work without hiding the remaining editorial and production decisions.
Turn the findings into a repeatable edition workflow
Write a short procedure identifying the supported copy method, shared dependencies, fields to review, and export naming rules. Explain what the test actually covered and what remains untested. Keep the disposable test available if the tool or its workflow changes and needs another check.
When applying the procedure to a real project, preserve the original source and verify the new copy before substantial editing begins. Keep shared material shared only where that serves the intended relationship between editions. The completed test should let the team explain which changes are isolated and which can propagate, rather than treating every duplicated project as independent by assumption.
Frequently asked questions
Clear answers for this publishing decision.
Does a different project name prove the copy is independent?
No. Inspect text, styles, assets, external links, and export destinations. Some dependencies may remain shared under the tool’s actual copy behavior.
Should every dependency be copied?
Not necessarily. Shared resources can be appropriate when intentional and understood. Decide which changes should propagate between editions and test that arrangement.
Can I test duplication on the only final manuscript?
Use disposable representative material first, and preserve the original before applying the procedure to production work. Keep the experiment reversible.
Does duplicating a project decide its publication identity?
No. The software test concerns source handling. The appropriate publishing setup, edition, and update route require their own current checks.
How do I get from an idea and a brief to an editable manuscript I can finish?
Write the brief first, generate a structure you can edit, then draft and revise the manuscript in reviewable sections so one change never overwrites work you already approved.
Start a book project from a brief