<p>Because the close wasn&#39;t tied to the model. Someone marked it done in Teams or email, the model kept the old geometry, and the field built what the model still said. That is how a fixed-looking clash comes back on Monday.</p> <p>BidLight closes an issue only with proof: a screenshot, a tagged user and the model commit that fixed it. If the element in Revit or Navisworks hasn&#39;t actually changed, the issue stays open. No proof, no close.</p> <p>Here&#39;s the loop that stops the repeat:</p> <ol><li>Issue is pinned to the element it concerns, not to a chat thread.</li><li>Every export is versioned and compared element by element, so the fix shows up as a real change.</li><li>The owner closes it with the screenshot, their name and the commit that fixed it.</li><li>The 6am digest puts it back in front of that owner if it isn&#39;t closed.</li><li>The project view shows who is behind while there is still schedule to recover.</li></ol> <p>The cost of getting this wrong is not small. A clash caught in the model runs about $50. The same clash found in the field runs $5,000 to $50,000. An unresolved one can burn $15K to $50K a week in idle field labour.</p> <p>Close with proof, not with a message.</p>