How do i prove a clash was actually fixed in the field and not just closed in th
1
A clash is only fixed when the field says so. BidLight gives you the trail to prove it. 1. Publish straight from the model in Revit or Navisworks.
add comment
Answers
0
<p>A clash is only fixed when the field says so. BidLight gives you the trail to prove it.</p>
<ol><li>Publish straight from the model in Revit or Navisworks. Every export gets versioned, so you have a record of what the model said and when.</li><li>Diff element by element. You see exactly which element moved, which changed, which got deleted. Not side-by-side PDF comparison.</li><li>Watch the issue close against a real change. When someone marks it resolved, the diff shows whether geometry actually moved or somebody just clicked close.</li><li>Check the daily digest by 6am. Every morning you get a record of what you own, so a closed issue with no element change stands out.</li><li>Hand the GC the export history. Two hours in the coordination meeting finding out who moved a duct becomes a two-minute lookup. Who changed what, when, why.</li></ol>
<p>That matters because every week a clash sits unresolved stops the work behind it. $15K to $50K in field labor standing idle, every week. Three weeks of that costs more than BidLight costs for the year.</p>
<p>You are not proving it with a screenshot. You are proving it with a versioned record the whole team can read.</p>