Verify the Last Export After a Final Manuscript Correction

After a final manuscript correction, inspect the new export at the changed location and review any affected pagination, references, figures, or cover inputs. Identify the file that actually contains the accepted correction and update the release record. An earlier export’s approval does not automatically cover a replacement file produced afterward.

Describe the correction and its expected effect

Write down the accepted change before exporting again. Identify the source location, the intended replacement, and why it is needed. A specific note such as correct the second instruction in exercise four gives the reviewer a reproducible starting point. A message saying final fixes applied does not show what changed or which parts of the output need attention.

Assess whether the change is local or structural. Correcting a short label may leave the surrounding layout largely unchanged, while replacing a paragraph can move a table or alter page flow. The distinction guides the review scope. Do not assume that every late correction requires the same checks, but do not classify a change as harmless simply because it was requested close to publication.

Export from the accepted source and configuration

Confirm that the working project contains the correction and retains the accepted production settings. A collaborator may have several similar source files, some with the new wording and others with later layout adjustments. Resolve which file is authoritative before exporting. Otherwise, fixing one issue can accidentally restore older text or discard unrelated accepted changes.

Give the replacement output a clear identity and record which earlier export it supersedes. Keep the earlier file available for comparison without leaving both as equally plausible submission candidates. Avoid relying only on a filename that includes final. The release record should explain which output was produced from which accepted source and which review still needs to happen.

Inspect the changed location in the actual output

Open the replacement file independently of the editor and find the corrected passage. Confirm the complete accepted wording, not just the presence of a changed keyword. Read the surrounding sentences and inspect the visual presentation. A correction can be present while an adjacent line is missing, a caption becomes detached, or the layout introduces an awkward break.

Compare the location with the source when the output differs from expectations. Repair the maintained project and regenerate when necessary rather than making an undocumented patch to the final file. A reproducible result matters for future updates. If the accepted correction exists only in a manually edited export, the next normal production run may silently remove it.

Check the dependencies that could have changed

Review related references, exercise answers, figures, and summaries when the correction affects their meaning. For layout changes, inspect nearby page transitions and any page-based references that may have moved. If the new interior changes a production input used by the cover workflow, reopen the relevant cover checks using current requirements. The review should follow the actual consequences of the change.

Record which earlier approvals still apply and which were repeated. Unchanged editorial passages can retain useful review history, while a newly positioned diagram needs confirmation in its new context. This avoids both blanket reapproval without inspection and unnecessary repetition of every previous task. The evidence should show a reasoned relationship between the change and the checks performed.

Replace the release candidate deliberately

Once the new output passes its required checks, update the package inventory and handoff instructions to identify it as the accepted candidate. Remove ambiguity about which file the operator should use while preserving the earlier export in the working archive if needed. Confirm that any copied release folder or shared handoff location now contains the reviewed replacement rather than the file it superseded.

Continue with the applicable KDP preview and submission checks for the actual files and format. Keep the correction note, export identity, and review result together. If another change occurs afterward, repeat the relevant process instead of extending approval by assumption. The final verification should establish that the file selected for the next action contains the accepted work and has been reviewed for the consequences of its last revision.