<p>Close the issue only with proof, and the proof lives on the element. That is how you show an inspector the fix happened before the wall went up.</p> <ol><li>Pin the issue to the element it concerns in Revit or Navisworks. Not a Teams thread. The element itself.</li><li>Fix it in the model and publish a new version straight from Revit or the federated model.</li><li>Attach the screenshot of the resolved condition.</li><li>Tag the user who made the fix.</li><li>Record the model commit that fixed it. The issue closes only when all three are there.</li></ol> <p>The export is versioned and compared element by element, so you can show what changed between the version with the clash and the version without it. That is the record the inspector sees: before, after, who, and which commit.</p> <p>Why it matters on the job: a clash caught in the model runs about $50. The same clash found in the field runs $5,000 to $50,000. The 6am digest also keeps the owner of that issue on it daily, so nothing sits open while there is still schedule to recover. You get a closed issue with proof, not a conversation to reconstruct later.</p>