Closing a review comment should leave a clear trail from the reviewer’s question to the response, revised document and closure decision. When comments disappear between spreadsheets, the team may repeat work or lose the reason a change was accepted. Keep the comment’s identity stable even when the document revision changes.

Capture the original instruction

Create one comment number and record the document ID, revision, section/page, reviewer and exact requested action. Preserve the original review file or email. If the comment is ambiguous, ask a focused clarification question and link the answer rather than paraphrasing it into a different requirement.

Use separate fields for the proposed response and the reviewer’s decision. This prevents a response written by the contractor from being mistaken for acceptance by the client.

Route the question to its owner

Classify the action by who can answer it: document author, supplier, contract administrator, designer or other technical owner. The coordinator can maintain the log and assemble references but should not make a technical commitment on someone else’s behalf.

In a hypothetical equipment-manual review, Comment C-027 asks for a revised isolation description. The supplier provides text, the responsible technical reviewer confirms the wording, and the manual author incorporates it into Revision D. The register links each step. It does not simply say “done” beside the original comment.

Check the response is findable

Before resubmission, verify that the cited revision exists and the referenced section actually contains the change. If the response says “see drawing”, include the drawing number and revision. This basic check reduces avoidable review loops without judging technical adequacy.

After resubmission, use a status such as “response issued—awaiting reviewer”. Close the item only when the authorised review outcome is recorded, or when a documented project rule permits another closure route. Retain rejected responses and reopening history so future readers can understand the sequence.

For reporting, distinguish open questions, responses being prepared, responses issued and comments resolved. Those categories are more useful than a single percentage complete that combines different stages.

Business Queensland’s procedure guidance emphasises usable instructions and clear responsibilities. Apply the same idea to the review log: name the next person and the next action. The result should make it easy for a new team member to continue the work without reconstructing the history from scattered inbox messages.