Bring PDF Review Comments Back Into the InDesign Treatment
Bring PDF Review Comments Back Into the InDesign Treatment
The operation is short. Open the InDesign document that produced the reviewed PDF, choose File > Import PDF Comments, and select the PDF the reviewer sent back. The comments arrive in the PDF Comments panel. The ones that are actual text edits — Adobe documents Accept for strikethrough, replacement and insertion text — can be applied to the source from there. Everything else you read and act on by hand.
That is the whole mechanism, and it is not where the trouble lives. A PDF is a snapshot, and a comment is anchored to a position inside that snapshot. The import works by finding the corresponding place in the InDesign file. If the file has moved on since the export, the anchor and the target can drift apart — and the panel may still present the result as though nothing were wrong.
So keep two questions apart for the entire job. Where does this comment belong? is a technical question the software helps you answer. Is anyone asking me to make this change? is an editorial question no import will ever settle. A note that lands exactly on the right sentence has been located, not approved. A note that lands nowhere has been located nowhere, which is not the same as being unimportant.
Treat the PDF and the source as one pair
Before you import anything, be able to say which InDesign file the reviewer was looking at. Not which project, not which job number — which file, at which point in its life.
Adobe's documentation for Import PDF comments is blunt about this: accurate comment placement requires the InDesign source to remain unchanged after the PDF was created. That precondition is doing far more work than it appears to. It is not a tip about tidiness. It is the condition under which the mapping means anything at all.
Version names help here, and so does a habit of keeping the exported state. If you duplicate the InDesign document before you export it, you have something to import into even weeks later. It is a small piece of housekeeping that costs one file copy and saves the whole afternoon described below.
A constructed example. A fictional designer finishes a 12-page campaign treatment for a fictional client, Meridian Coffee, and exports it on a Thursday as Meridian_Treatment_v3_review.pdf. The client's marketing lead marks it up over Thursday and Friday: a strikethrough across "bold" in the positioning line, an insertion of "and in-store audio" after "social" in the channel list, and a sticky note pinned to the schedule asking whether the shoot can hold until the new packaging ships. On Friday afternoon she also sends a short email asking for a wording change in the positioning line, and the designer makes it that evening — the line originally read "Meridian is a bold, everyday luxury," and it now reads "Meridian is an everyday luxury." The same evening, a page of new material goes in near the front, taking the treatment from 12 pages to 13 and pushing the schedule from page 8 to page 9. The marked-up PDF arrives Monday. The source has moved; the PDF has not.
This is not a contrived mess. It is an ordinary week.
Import into the matching document
When the pair is still intact, import into the source that produced the PDF: File > Import PDF Comments, then pick the reviewed file. Then open the PDF Comments panel and actually look at it. The import is the start of the review, not the end of it.
The version discipline matters most when feedback arrives from more than one place. Two exports of a treatment can look nearly identical on screen and differ by a paragraph. If notes from both come back, the panel gives you a list, and a list is happy to accept a comment into the wrong document. Name your exports so the pairing is visible in the filename, and when you have two reviewers, keep straight which PDF each one marked. A comment cannot tell you it was imported into the wrong source.
Mapped and unmapped are both worth reading
Adobe's panel provides filters for mapped and unmapped comments. The names are self-explanatory and slightly misleading.
Mapped means the software found a target it believes corresponds to the comment's anchor. It does not mean the target is the right one, and it does not mean the change is wanted. Repeated phrases are the classic failure: if "social" appears in your channel list and again in the budget table, a comment about the channel line has more than one place it could plausibly attach.
Unmapped means no target was found. That is genuinely useful information, because it tells you not to expect the panel to place the edit for you. What it does not tell you is that the reviewer's point is moot. The passage may have been reworded slightly, split across two text frames, or wrapped into a caption. The comment still wants an answer; it just wants one from a human.
Here is the rule that resolves the uncertainty rather than adding to it: treat any comment whose target you cannot point to in the source as unmapped, whatever the filter says. The filter is the software's opinion about location. The verification is yours. Read every comment in the mapped list and confirm it against the passage the reviewer was actually looking at in the PDF.
That check is quick when you do it deliberately. Put the reviewed PDF and the InDesign window side by side. For each mapped comment, find the marked text in the PDF, then confirm the panel is offering you the same words in the source. For each unmapped one, find the marked text in the PDF and locate its counterpart by hand — search the story, not just the page.
What the reviewer actually asked for
Not every comment is a text operation, and the difference predicts how much work is coming.
Strikethrough, replacement and insertion text are the three the import can apply for you, per Adobe's documentation. Those are the clean cases: someone crossed out a word, swapped one phrase for another, or added text at a specific point. Even then, applying the change is a decision, not a reflex.
A sticky note is a different animal. It has no text operation to apply. It says something like "Can we hold the shoot until the new packaging ships?" — a question about a schedule, attached to a page. The panel can carry it to you, and it can tell you roughly where it was pinned, but nothing in the software resolves it. You read it, you find out whether the shoot can move, and you edit accordingly.
Broad creative requests sit in the same category. "This section feels flat." "Can we see a version without the tagline on every page?" There is no Accept button that means anything for those, and there shouldn't be.
And a location is never an approval. The reviewer may be a person with no authority over the schedule page. A note may contradict an instruction that came in by email an hour later. Import puts the feedback in front of you; deciding which feedback governs the treatment is a separate job, done by people.
When the source has already moved
Back to Meridian. The designer imports the Monday PDF into a source that changed on Friday evening. Three things are now in play, and they need three different responses.
The strikethrough on "bold" has nothing left to strike. The word is gone. If the panel reports it as unmapped, that is consistent with the situation. If it reports it as mapped, the software has found something nearby, and accepting it would be a mistake. Either way the correct move is the same: credit the reviewer, note that the change is already in the file, and mark the comment already satisfied. Do not accept an edit just because the panel offers one.
The insertion in the channel list — adding "and in-store audio" after "social" — sits in a paragraph that has not moved. This is the case where the import should do its job. Verify it anyway, because the budget table on a later page also contains the word "social," and an insertion that lands in a budget line is worse than one that lands nowhere: it looks correct in the panel and is wrong in the document.
The sticky note on the schedule anchors to a page position, and the schedule moved from page 8 to page 9 when the designer added a page of new material. Sticky notes are not text edits, so there is nothing to accept. What the import can do is point you at the general area. What it cannot do is tell you that the schedule has shifted — you know that, because you shifted it.
That walkthrough is constructed to show the decision points; it is not a recorded import, and the filter statuses your own file produces will depend on your document. The point is the procedure, not a prediction. Read the panel, verify every mapped comment against the PDF, and route every doubtful one to manual comparison.
Two rules keep this honest when there is real work in flight. Don't overwrite newer edits to make room for an older comment. And don't decide a comment is obsolete because the file is newer than the PDF — recency of a file tells you nothing about whether a reviewer's question has been answered. The positioning line changed for one reason on Friday; whether that satisfies the strikethrough on Monday is a judgment about the words, not about timestamps.
Finish with a file and a list
The output of all this is not "the comments were imported." It is a revised source, a fresh export that someone can read, and a comment list where every item has a disposition: accepted, rejected, already satisfied by a change the source has since taken on its own, or deliberately left open with a name attached to it.
Keep three things together at the end — the reviewed PDF, the revised InDesign file, and the list. That set lets anyone trace a change back to the passage that prompted it and the instruction that governed it. It also makes the open questions impossible to lose, which is most of the value. The unanswered ones are the ones that quietly disappear between rounds.
The reviewed export should stay in the project. It is the record of what the reviewer saw, and without it a later argument about whether a suggestion was ever addressed has nothing to stand on.
If the feedback was messy in a way that goes past anchoring — contradictory notes, a request that changes the shape of the treatment, two people asking for opposite things — the sorting out is its own task, and it happens after this one. This step gets the comments into the file in the right places, with their status known. Someone still has to decide what the treatment should say.
Frequently asked questions
What does Import PDF Comments actually do, and what does it not settle?
It brings comments from the reviewed PDF into the InDesign PDF Comments panel. The import can apply strikethrough, replacement, and insertion text to the source. It does not decide whether a change is wanted or approved. A note that lands on the right sentence has been located, not approved, and a note that lands nowhere is still not necessarily unimportant.
Why does the InDesign source need to stay unchanged after the PDF is created?
A PDF is a snapshot, and a comment is anchored to a position inside that snapshot. The import works by finding the corresponding place in the InDesign file. If the source has moved on since the export, the anchor and target can drift apart even when the panel presents the result as if nothing were wrong. Accurate comment placement requires the source to remain unchanged after the PDF was created.
What do mapped and unmapped comments mean, and how should each be handled?
Mapped means the software found a target it believes corresponds to the comment. It does not mean the target is right or the change is wanted; repeated phrases can make a comment attach to the wrong place. Unmapped means no target was found, which tells you not to expect the panel to place the edit but does not make the reviewer's point moot. Treat any comment whose target you cannot point to in the source as unmapped, whatever the filter says. Verify mapped comments against the PDF, and locate unmapped ones by hand.
How should sticky notes and broad creative requests be handled?
A sticky note has no text operation to apply, so the panel can carry it and show roughly where it was pinned, but nothing in the software resolves it. Broad creative requests such as 'This section feels flat' are in the same category. Read them, find out whether the underlying facts support a change, and edit accordingly. A location is never an approval; the reviewer may lack authority over that page, or a later instruction may contradict the note.
What should be done when the source has moved since the reviewed PDF, and what should the final output be?
A strikethrough on a word that has already been removed has nothing left to strike, so mark it already satisfied rather than accepting an edit just because the panel offers one. An insertion in an unchanged paragraph should be verified, especially if the same word appears elsewhere. A sticky note anchored to a page position cannot tell you that the schedule moved from page 8 to page 9. Do not overwrite newer edits, and do not decide a comment is obsolete because the file is newer than the PDF. Finish with the revised source, a fresh export, and a comment list where every item has a disposition. Keep the reviewed PDF, the revised InDesign file, and the list together.