DrawingDeskWhy “done” is not the end of the conversation
A comment can disappear from an open list without the underlying issue being solved. Perhaps a drawing changed but the related detail did not, or a response said “done” without identifying what was revised. Closing comments is a small verification process, not an administrative click. It should leave enough evidence for someone outside the immediate conversation to understand the original concern, the response and the basis for acceptance. That context becomes especially valuable when a decision is questioned weeks later or a similar condition appears elsewhere in the project.
Reply where the issue was raised
Keep the response attached to the original markup whenever the review tool allows it. The location, wording and reply then remain one connected record. Avoid moving the real discussion into an email thread that future recipients of the reviewed PDF cannot see. If an external decision is necessary, summarise it back in the comment. A useful reply names the revised sheet or detail and describes the change: “Moved access panel 300 mm east on reflected ceiling plan revision C” gives the reviewer something specific to inspect.
Separate answers from evidence
An explanation may be technically reasonable, but it is not always proof that the drawing now reflects it. Treat the response as a guide to verification. Open the stated revision, return to the marked location and check the affected relationships. If the decision was to make no change, confirm that the reason addresses the original concern and is recorded clearly. This approach keeps the exchange constructive: the responder explains the solution, while the reviewer confirms that the issued information and the agreed solution match.
Look beyond the exact marked spot
Many changes have neighbours. Moving a door affects clearances and elevations; raising a duct may affect access and ceiling zones. Before resolving the comment, follow the immediate consequences through related views and schedules. This does not require reopening the entire review, but it does require enough curiosity to ensure the correction has not simply moved the conflict. If a new issue appears, create a fresh, focused comment rather than stretching the original discussion until its status becomes impossible to read.
Close clearly and preserve the trail
Use a small set of unambiguous outcomes such as resolved, accepted with no change, superseded or still open. Add a final note when the reason for closure is not obvious, then retain the markup and replies in the review record. Resolution should reduce noise in current work without erasing history. A well-closed comment tells a compact story: what the reviewer noticed, how the team responded, what evidence was checked and why the item no longer needs attention. That is far more useful than a clean list with no memory.
Teams can make this habit easier by agreeing what evidence is sufficient for common types of issue. Some items need a revised detail, while others may be closed through a recorded design decision. Clear expectations reduce unproductive back-and-forth without weakening review quality. Closure then becomes a shared professional judgement supported by visible information, rather than a status controlled by whoever clicks last.