Are design changes silently wrecking your budget
1
Compare every revision as it is published. A change that is visible in the model is a conversation. A change found on site is rework. The gap is large. A clash caught in the model costs about $50.
add comment
Answers
0
<p>Compare every revision as it is published. A change that is visible in the model is a conversation. A change found on site is rework.</p>
<p>The gap is large. A clash caught in the model costs about $50. The same clash found in the field costs $5,000 to $50,000.</p>
<p>Here is a routine that catches changes early with BidLight:</p>
<ul><li>Publish from Revit, or the federated model from Navisworks, after each change.</li><li>Compare the new snapshot to the previous one, element by element, by category.</li><li>Pin an issue to each element that affects another trade's work.</li><li>Tag an owner and let the 6am digest carry it to them.</li><li>Close the issue only with a screenshot, a tagged user and the linked model commit.</li></ul>
<p>The comparison takes about 15 minutes. It replaces a 90-minute meeting, and the people who need to know are told the next morning without anyone chasing.</p>
<p>You will not catch every change this way, but you will catch the ones that matter before the crew does.</p>