<p>An issue in BidLight closes only with proof. No proof, no close. That is how you verify the fix actually landed in the model.</p> <p>Here is the flow:</p> <ol><li>The issue stays pinned to the element it concerns, in Revit or Navisworks. It does not float free in email or Teams.</li><li>To close it, the owner attaches a screenshot of the corrected element.</li><li>They tag the user who made the change.</li><li>They record the model commit that fixed it. That is the versioned export the system already diffed element by element.</li><li>The record shows who closed it, when, and against which commit. Anyone on the team can check it later.</li></ol> <p>So when a clash gets marked done, you are not trusting a message. You are looking at the element, the person, and the commit. If the fix never made it into the model, the proof is not there and the issue does not close.</p> <p>That is the difference between a clash caught in the model and one that surfaces in the field. About $50 to fix it early against $5,000 to $50,000 in the field. An unresolved clash can burn $15K to $50K a week in idle field labour. Closing with proof is how you keep it from getting that far.</p>