<p>It came back because it was never really closed. Someone marked it done, but nothing tied that closure to the model. Then the next export landed with the clash still in it, and Monday the field found it the hard way.</p> <p>The fix is proof. On BidLight an issue is pinned to the element it concerns, and it closes only with a screenshot, a tagged user and the model commit that fixed it. Every export is versioned and compared element by element, so if that clash is still in the model it shows up right there, not on site.</p> <p>That matters because a clash caught in the model costs 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 while crews wait.</p> <p>So the Monday surprise is a record problem, not bad luck. Pin it, prove it, and let the element-by-element comparison confirm it stayed fixed before the next version goes out.</p>