When a Drawing Comment Can Be Closed

Establishing Definitive Criteria for Review Resolution

Maintaining a clean set of markups is not just about aesthetics; it is a fundamental requirement for risk management in the AEC industry. When a reviewer places a cloud on a sheet, it represents an unresolved risk or a technical discrepancy that must be addressed before the next project milestone. The process of closing these comments often becomes a bottleneck during intensive coordination phases, leading to confusion about which changes are actually final.

The Three Pillars of Closure

A drawing comment does not simply vanish once a designer makes a modification. It follows a structured path from identification to verification. For a comment to be officially closed, it must meet one of the following conditions:

• Physical Verification: The specific design change requested is visually confirmed in the current sheet revision. This involves checking the geometry, dimensions, and annotations against the original markup.
• Regulatory or RFI Reference: The issue is addressed through a formal Request for Information (RFI) or a change in local code compliance. The closure note should explicitly link to the RFI number or the specific code section.
• Coordination Resolution: The clash or discrepancy is discussed in a multi-discipline meeting, and a consensus is reached that the current condition is acceptable as-is. In this case, the comment is closed with a summary of the decision.

Ownership and Authority

One of the most common failures in change management is the unauthorized closure of comments. Only the original author of the markup, or a designated Project Lead, should have the permission to move a status from "Resolved" to "Closed". If a contractor simply deletes a markup without consultant verification, the project loses its audit trail, which can lead to significant disputes during the construction phase.

"A closed comment is a promise that the design intent has been fully satisfied and the risk has been mitigated."

Maintaining the Audit Trail

Closing a comment is not just a checkbox exercise; it serves as a legal and technical record of the coordination process. In platforms like Bluebeam Revu 21, the status history is permanently attached to the markup. When a comment is moved to 'Closed', the system records the timestamp and the user ID. This metadata is invaluable when disputes arise regarding why a certain pipe was routed through a specific corridor or why a fire-rated partition was relocated. Project managers must insist that every closure includes a brief comment explaining the resolution, rather than leaving a blank status change.

FAQ: Common Hurdles in Review Workflows

Can a comment be closed if the design change is rejected?
Yes, but the status should reflect this. If a proposed change is rejected for technical or budgetary reasons, the comment is closed with a note explaining the logic behind the rejection. This prevents the same issue from being flagged in subsequent reviews.

Who has the final say on MEP clash closures?
In most BIM-heavy projects, the Lead Coordination Engineer has the authority to close clash-related comments once the 3D model shows zero interference. However, architectural sign-off is still required if the resolution affects ceiling heights or aesthetic finishes.