How do i make sure a clash that was closed in the model actually carries through
1
The clash closes in the model, so the field crew needs the same record you see. That only happens when everyone works off one live model, not exported PDFs and email threads.
add comment
Answers
0
<p>The clash closes in the model, so the field crew needs the same record you see. That only happens when everyone works off one live model, not exported PDFs and email threads. BidLight keeps that record inside Revit and Navisworks, so a closed issue stays closed and visible.</p>
<ol><li>Close the clash on the model, not in a separate tracker. The issue lives where the geometry does.</li><li>Close it with proof: a screenshot, a tagged user and the linked model commit that fixed it.</li><li>Publish from the model. BidLight versions every export and diffs it element by element, so the closure is recorded as a change, not a note someone typed.</li><li>Let the daily digest go out. Teams get a 6am digest of what they own, so the field sees the closed item that morning instead of finding out at the next meeting.</li></ol>
<p>That is the whole idea: one live record of the project inside Revit. The crew stops asking who changed what because the answer is already there, and the same problem does not come back on site.</p>