The final print PDF deserves its own review

Freeze a candidate before checking it

The final PDF deserves its own review. It is a new production object, not merely a smaller copy of the layout file. Export settings, font handling, linked images and last-minute corrections can introduce differences. Give the candidate a clear version name and record the date so everyone knows which file is being examined.

Keep the printer's supplied specifications beside the review. They establish the required page dimensions, bleed, colour handling and other delivery details. Do not assume that a preset with an impressive name is automatically suitable. If a requirement is unclear, resolve it with the receiving production service before approving the file.

Separate a technical pass from a reading pass. Looking for missing fonts while also checking a quotation encourages both kinds of error to slip past. The passes may involve different people, but they must refer to the same candidate PDF. Otherwise one reviewer can approve a file that another person has already replaced.

Check the document as an object

Confirm the page count, trim size, orientation and order. Look at the first and last pages, blank pages and transitions between front matter, chapters and end matter. A single missing blank page can alter intended left- and right-hand positions throughout the book. Verify that any deliberate blank pages are deliberate in this exported version.

Check bleed where artwork reaches an edge, and confirm whether crop marks or other printer marks are requested. More marks are not necessarily better. Examine covers and interior files separately when the service requires them separately, and make sure the final cover template corresponds to the final interior specification.

Use a suitable preflight profile to identify missing fonts, inappropriate image resolution and other technical issues. Adobe describes preflight as a way to monitor production problems such as missing links and overset text. These checks are useful evidence, but the profile must reflect the job. A clean report from an irrelevant profile can be reassuring without being meaningful.

Look for what automation cannot interpret

Read headings and their following paragraphs. Inspect page numbers, running heads, captions and cross-references. A caption can be perfectly formatted beneath the wrong picture. A running head can contain an old chapter title. Neither problem necessarily produces a technical warning, because the file is mechanically valid.

Review special characters and formatting that often expose conversion problems: italics, accents, mathematical symbols, ligatures, bullets and unusual punctuation. Search for known editorial markers, unresolved comments and placeholder text. If a book uses several languages, include representative passages from each rather than assuming one successful page proves all fonts are covered.

Inspect images at both a normal reading view and a closer diagnostic view. Check that the final crop preserves the intended subject and that a low-resolution preview has not replaced the source. Tables need row-by-row review, especially after they have been split. Notes should remain connected to their markers and readable at final size.

Sample strategically, then read completely where needed

A quick visual sweep of every page can reveal empty frames, sudden spacing changes or a displaced image. It does not substitute for reading the text. Choose the appropriate editorial review for the stage: a corrected proof may need verification of every marked change plus a broader layout review, while an unproofread export needs more extensive reading.

Print representative pages at actual size. Include dense pages, chapter openers, image pages and the smallest text. Screen zoom can hide a cramped note style or make margins feel more generous than they will in the physical book. A production proof is especially valuable when paper and image reproduction are central to the result.

Close corrections in a controlled loop

Record each issue with its page, location and required change. Apply corrections in the source, export a new candidate and verify the corrected location. Then inspect nearby text for reflow and repeat any technical checks affected by the change. A small edit can move a line, a page break or a note.

Keep the accepted PDF separate from earlier candidates and save the associated source version. Before sending it, open the actual file from the delivery location rather than a remembered copy in a recent-files list. Confirm its name, size and page count. The approval should belong to a specific file that can be identified later, not to a general impression that the book was checked.