PDF comments: what will actually appear on printed correspondence?

In a business workflow, a PDF can serve both for discussing content and for handing documents over to print production. That works until a file containing working notes is treated as production-ready material. A comment intended for the author may appear in the wrong place, while an annotation that matters may be missing on paper.

Opening the document and deciding that it looks right is not sufficient. Define the intended output, distinguish correction instructions from content for the recipient, and inspect a proof made through the actual process. This procedure addresses that boundary, rather than font embedding or separating letters into physical sheets.

1. Define the purpose of each mark

Before handing over the file, assign notes one of three roles: an instruction for the author, an internal approval record, or an element the recipient should see. Do not decide by colour alone. A yellow highlight can be a reviewer's instruction or an intentional emphasis.

Editorial example: a comment beside a payment deadline says 'change the date'. The approver should confirm the change in the final document text. The comment itself, or marking it as dealt with, is not evidence that the finished letter contains the correct deadline. Check the specific location in the version intended for the recipient.

2. Separate review material from production material

Keep the annotated review copy within the agreed working process. Supply one clearly identified, approved PDF for production. If some marks must remain on paper, describe them separately: type, page, intended appearance and purpose. Avoid instructions such as 'print it as it looks on screen'.

Do not assume that every visible element belongs to the page's underlying content. Adobe describes adding a comment to selected text or an image as a separate action. Ask about working notes when accepting a file, even if it does not look like a marked review version. Do not automatically remove marks without the content owner's decision.

3. Agree how comments will be printed

Current Adobe Acrobat documentation distinguishes Document, which excludes comments, from Document and Markups, which includes them in the printout. This is enough reason to avoid equating an on-screen view with production output.

Those option names refer to Adobe Acrobat. A provider may use other tools, so the agreement should describe the result: no working notes and all approved elements present. The operator confirms how the production process will achieve it. The document owner confirms what the recipient is meant to receive.

4. Build a small proof covering exceptions

Prepare a test without personal data: a page without notes, one with a working comment, and one with a mark that must print. If the batch contains different templates, choose examples covering each material variant. One correct page does not establish how all types of marks behave.

Compare the physical output with the approved expectation. Check for unwanted working notes, missing required elements and marks obscuring text. Inspect output produced through the process that will actually be used, rather than substituting a screenshot. Record the differences found and the decision on each one.

5. Link approval to a specific file and output

Record the supplied file's name and identifier, the date, the agreed rule for comments, the pages checked and the approver. Attach the approved proof or an agreed record of it. The purpose is to reconstruct the result that was accepted, rather than merely to collect messages saying 'OK'.

After a content or setting change that affects marks, stop relying on the earlier approval and agree the scope of another proof. Do not put a working comment list into the envelope simply because it was created during checking. A correction list and an insert for the recipient serve different purposes.

6. Give the provider a clear instruction

A useful instruction could say: 'Produce from the identified PDF without working comments; retain the mark on page 2 as shown in the approved proof'. Resolve any ambiguity before starting the batch. The provider should not have to interpret which notes call for content changes.

BackOffice Outsourcing provides document printing, personalisation, folding and envelope inserting. Agree the file handover and proof approval process when placing an order. Describe your document and intended printed output to establish a practical workflow. The pre-dispatch checks guide covers the wider batch review.

Sources and scope

• Adobe: Print comments
• Adobe: Add comments to selected text or images

Adobe documentation checked on 22 October 2026. The feature descriptions refer to Adobe Acrobat and do not imply that BackOffice Outsourcing uses it. The roles, example, test set and approval approach are editorial recommendations to agree for the particular job.