How do I collect and export comments from a PDF review?

Start in the PDF application’s comments or annotations panel, and make that list your working inventory. In Acrobat desktop, the Comments list can be sorted by page, author, date, type, unread status, or color, and filtered by comment type or status. [S1] If your PDF app uses different labels, look for its equivalent comments panel and check its help for available export options.

Before exporting, decide what you need to do with the comments. If you’re reviewing them yourself, sorting by page can make it easier to check notes alongside the document. If you’re dividing work among people, sorting by author or filtering by type may help you prepare separate review passes. Keep the original PDF unchanged while you make the list, so you can return to its page and surrounding material when an annotation is unclear.

Treat those as two different needs. A comment data export such as FDF or XFDF contains comment data; it is not the PDF itself. [S2] A comment summary is intended to present comments in a readable summary format; Acrobat desktop’s Comments list offers options to create a summary or export a summary to Word. [S1]

A practical approach is to create a readable summary for the review log, while keeping the commented PDF as the document you consult for context. If you also need a separate comment data file, export that as an additional deliverable. In Acrobat desktop, the Comments list’s Options menu provides export choices for all or selected comments, and summary options. [S1] Availability can vary by Acrobat experience; selected-comment export is not available in Acrobat Reader. [S2] Check the choices shown in your version before planning a workflow around a particular option.

Use the exported list as an index, not as proof that every note has been understood in context. For each entry, go back to the PDF, locate the page, and inspect the nearby text, image, or marked area. Record a short context clue in your review log, such as a heading or the first few words of the referenced passage. Then mark whether the page and context match.

This check matters especially when comments are imported or moved between documents: Acrobat’s help notes that comment placement corresponds to the source file, so using a mismatched PDF can put comments out of place. [S2] The export tools establish that comment data or summaries can be created; they do not guarantee correct contextual interpretation. [S1] If a note’s target is ambiguous, mark it for clarification rather than guessing.

Yes. First, save or identify the exact reviewed PDF you will use as the reference. Open its comments list, sort or filter the entries for the review you’re doing, and export a readable summary or the comment data you need. Then verify every entry against that same PDF and fill in a log like this:

ID | Page | Reviewer | Comment | Context clue | Action | Check 01 | 4 | [name] | Clarify the heading | “Project scope” heading | [owner to decide] | Matched 02 | 7 | [name] | Update this figure | Figure caption begins “Quarterly…” | [owner to decide] | Needs context check

The example is illustrative: replace bracketed fields and wording with your actual review details. Use a stable ID so you can refer to a comment in discussion, and keep the comment’s wording distinct from your proposed action. For each row, record a page number, a brief context clue, and a check status such as Matched, Needs clarification, or Not located. If a comment cannot be matched, recheck the source PDF and flag it; don’t silently assign it to a nearby passage.