How do i prove that an issue was actually fixed not just marked closed
1
An issue closes only with proof. In BidLight, that means three things attached to the element: a screenshot, a tagged user, and the model commit that fixed it. No proof, no close.
add comment
Answers
0
<p>An issue closes only with proof. In BidLight, that means three things attached to the element: a screenshot, a tagged user, and the model commit that fixed it. No proof, no close.</p>
<p>Here is the flow:</p>
<ol><li>The issue is pinned to the element it concerns in Revit or Navisworks. It does not float in email or Teams.</li><li>The fix gets published as a new version. Every export is versioned and compared element by element, so the change is visible.</li><li>The person who made the fix is tagged. The model commit is linked.</li><li>A screenshot shows the resolved condition. That is the proof.</li><li>Only then does the issue close. The record stays with the element.</li></ol>
<p>The 6am digest tells every owner what they own, so nothing gets marked closed to clear a list. The project view shows who is behind while there is still schedule to recover.</p>
<p>That proof matters on the job. A clash caught in the model costs about $50. The same clash found in the field costs $5,000 to $50,000. An unresolved one can burn $15K to $50K a week in idle field labour. Proof stops the issue from coming back as an RFI or a change order.</p>