What should i know about the gap between the coordination model and the field wa
1
Model changes turn into field costs when nobody tracks them: the model moves first, and the field pays for it later. Take a week. Monday, a sleeve moves 6 inches.
add comment
Answers
0
<p>Model changes turn into field costs when nobody tracks them: the model moves first, and the field pays for it later.</p>
<p>Take a week. Monday, a sleeve moves 6 inches. Tuesday, a duct bank reroutes around a column. Wednesday, a riser penetration changes. By Friday you have three changes to price and no record of who moved what, when or why.</p>
<p>BidLight keeps one live record inside Revit and Navisworks. You publish straight from the model, every publish is a versioned snapshot, and any two revisions compare element by element by category. You see what changed instead of comparing PDFs side by side.</p>
<p>How to close the gap:</p>
<ul><li>Publish from Revit or Navisworks after each change.</li><li>Compare revisions and price only what actually moved.</li><li>Pin issues to the affected elements, with sheet and revision attached.</li><li>Check your 6am digest for the issues you own.</li><li>Close issues only with proof: screenshots, sign-off and the linked model commit.</li></ul>
<p>That matters because a clash caught in the model costs about $50, against $5,000 to $50,000 once it reaches the field.</p>