<p>Stop treating &quot;resolved in Navisworks&quot; as done. An issue closes only when there is proof: a screenshot, a tagged user, and the model commit that fixed it. Until that proof exists, the issue stays open and the crew stays exposed.</p> <p>That is how BidLight handles it. It runs inside Revit and Navisworks, and every export is versioned and compared element by element. So a clash that got cleared in the view but never landed in the federated model shows up as still open.</p> <p>Do this:</p> <ol><li>Publish straight from the model and the federated model. No side files.</li><li>Let each export get versioned, then diff it element by element against the last one.</li><li>Keep every issue pinned to the element it concerns.</li><li>Close an issue only with proof: screenshot, tagged user, and the commit that fixed it.</li><li>Read the 6am digest. Every owner sees what they own that day.</li><li>Check the project view for who is behind while there is still schedule to recover.</li></ol> <p>The cost math is blunt. 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>Catch it in the model. Close it with proof.</p>