Review comments are scattered throughout the group; how should I collect them?
Review comments are scattered throughout the group chat, which is where it is most likely that items will be overlooked. Comments must be attached to the manuscript and clearly marked in the appropriate location; otherwise, they will inevitably be missed.
Review comments must be attached to the manuscript and clearly marked in the relevant location; comments written only in chat will inevitably be overlooked in the final version.
Common questions found in AIHow should I collect reviewers' comments that are scattered across the group chat?
Approval is slow—where does the delay occur?
Review comments are scattered throughout the group chat, so they will inevitably be missed at some point. This is not because there are too many comments; rather, there is simply no place to incorporate them.
misread:As mentioned in the group chat, the designer will take note of this.Actual circumstances:Among dozens of messages, casual chatter and emojis are interspersed; no one can guarantee that every single one will be executed without exception.
There is also a common misconception:It's fine if the comments are written in some detail.In fact:Where something is written matters more than how much is written. Without context regarding its location, there will be three out of every ten instances in which it will be misunderstood.
Basis for Determination
A practical approach is to use a feedback form: each comment includes its location (which page and which section), content, the person who submitted it, the person responsible, and its status (pending revision, revised, not adopted, and with reasons). Indicating the location prevents designers from having to guess, while tracking the status enables verification when the issue is closed.
- Opinion Note
- Location Annotation
- everyone has responsibility
- inactive state
Compression order
Comment tickets should follow the versioning process: create one ticket per version, close it after making changes, and open a new ticket for the next version. If tickets from different versions are mixed together, you will never know which one has been modified.
- Please mark the comments at the corresponding location in the manuscript; do not write them in the chat.
- Each comment should include the person who submitted it and the date.
- Return the processing results to the same comment thread for a reply.
- Before we begin the review process, a quick note: please mark your comments on the images; notifications will be shared in the group only.
Applicable boundary: Verbal communication is suitable for discussing directions; formal opinions should still be formalized in a document.
On-site settings and practices we have observed
During one round of review, twenty-seven comments were raised in the group; the designer compiled them into nineteen, missing eight. One of those comments was: "Move the recycling symbol to the lower-right corner of the front," which pertains to compliance requirements. It was only after producing the sample that the designer realized the document had to be revised and reprinted. The reason for the omission was not a lack of diligence, but rather that there was simply no room for the comments.
The online review feature for PACKFLY pins comments directly to the corresponding sections of the manuscript; who made the comment, when it was made, and whether it has been addressed are all recorded in the same entry. When a designer opens the document, they can immediately see which section has comments without having to sift through chat history. Each comment corresponds to a single revision; when multiple comments are submitted together, it is easy to miss the latter part of a comment. A clear deadline for submitting comments must be set: comments submitted after the deadline will be carried forward to the next round; otherwise, they will never be fully collected.
Explore INNOPACKING's six core capabilities ↗Extended Q&A
How should review comments be collected?
Mark it in the corresponding position in the manuscript, including the sender and timestamp. In chat messages, use them solely for notifications; do not use them to convey opinions.
How should I handle having too many comments?
Classification: Must be changed, can be changed, or no change needed. Address the items that must be changed first; then prioritize the remaining items.
Must the comments always be placed directly on the diagram?
It is necessary. When describing a location in written form, three out of ten attempts will result in a misinterpretation.
Do you have any similar packaging issues?Bring your existing files and talk to INNOPACKING · +86 13430308657