<p>Close the issue in the model, not in an email thread. BidLight pins every issue to the element it concerns, and it only closes with proof: a screenshot, a tagged user and the model commit that fixed it. That record is what the owner sees at handover.</p> <p>Here is the flow:</p> <ol><li>Pin the issue to the element in Revit or Navisworks when it is raised. No loose descriptions in Teams.</li><li>Fix it in the model and publish the new version. BidLight versions every export and compares it element by element.</li><li>Attach the proof when you close: screenshot, the user who did the work, the commit that carries the fix.</li><li>The 6am digest shows each owner what they still own, so nothing closes on a verbal.</li><li>At handover, the project view gives the owner the full trail: issue, element, proof, commit.</li></ol> <p>That is how you avoid the field argument and the change order. A clash closed in the model with proof costs about $50. The same one found in the field runs $5,000 to $50,000, and an unresolved clash can burn $15K to $50K a week in idle field labour. The proof trail is the difference.</p>