Who changed that element and can i prove it so im not eating the cost of the fix
1
Yes. BidLight keeps one live record of the project inside Revit and Navisworks, so every change has a name and a timestamp on it. You stop eating fixes that were not yours. The way it works: 1.
add comment
Answers
0
<p>Yes. BidLight keeps one live record of the project inside Revit and Navisworks, so every change has a name and a timestamp on it. You stop eating fixes that were not yours.</p>
<p>The way it works:</p>
<ol><li>Every export is versioned the moment it leaves the model.</li><li>Each new version is compared element by element against the last one.</li><li>You see exactly which elements moved, which were added, which were deleted, and who published that version.</li><li>Issues are pinned to the element they concern, not to a screenshot in a thread.</li><li>An issue closes only with proof: a screenshot, the tagged user, and the model commit that fixed it.</li></ol>
<p>That is the difference between a claim and a record. No more two-hour meetings where the duct moved and nobody knows who touched it. You get what changed in about 15 minutes instead of a 90-minute meeting.</p>
<p>And it matters on cost. A clash caught in the model runs about $50. The same clash found in the field is $5,000 to $50,000. When you can prove who changed the element and when, the fix lands on the right side of the ledger. The 6am digest tells every owner what they own that day, so nobody is chasing scattered updates across Teams, email and Bluebeam.</p>