How do i stop walking into the gc meeting weeks after a slip started
1
The slip is already real. What is missing is the record that shows it before the GC meeting.
add comment
Answers
0
<p>The slip is already real. What is missing is the record that shows it before the GC meeting. BidLight keeps one live record of the project inside Revit and Navisworks, so you see who is behind while there is still schedule to recover.</p>
<p>How to set it up on your next job:</p>
<ol><li>Publish straight from the model. Every export becomes a version, so nobody is comparing PDFs side by side.</li><li>Diff element by element on each new version. You see what moved, not a 90-minute meeting spent finding out. Teams get to what changed in about 15 minutes instead of 90.</li><li>Pin issues to the element they concern. They close only with proof: a screenshot, a tagged user and the model commit that fixed it.</li><li>Turn on the 6am digest. Every owner gets a daily note of what they own, so a slip shows up in their inbox the morning it starts, not three weeks later at the GC table.</li><li>Watch the project view for who is behind. That is your early warning while there is schedule left to recover.</li></ol>
<p>Why it matters to the job: a clash caught in the model costs about $50. The same one found in the field costs $5,000 to $50,000. Every week a clash sits unresolved stops the work behind it, and that idle field labour burns $15K to $50K a week.</p>
<p>That is the whole point. You walk into the meeting with the record, not the surprise.</p>