When a coordinator leaves the job how do i keep the record of what changed and w
1
The record lives in the model, not in someone's head. That is the whole point of how BidLight works. When a coordinator walks, nothing walks out with them. Here is how it holds up on a real job: 1.
add comment
Answers
0
<p>The record lives in the model, not in someone's head. That is the whole point of how BidLight works. When a coordinator walks, nothing walks out with them.</p>
<p>Here is how it holds up on a real job:</p>
<ol><li>Every export from Revit or Navisworks is versioned. Nothing gets overwritten. The history of the model is the history of the job.</li><li>Versions are compared element by element. Anyone on the team can see what changed between two exports in about 15 minutes instead of sitting through a 90-minute meeting to work it out.</li><li>Issues are pinned to the element they concern, with a tagged user and the model commit that fixed it. A closed issue carries its own proof: a screenshot and the commit. The next person picks up the thread without a handover call.</li><li>The 6am digest goes to every owner daily, so ownership is written down and visible, not remembered.</li><li>The project view shows who is behind while there is still schedule to recover, so a gap in coverage surfaces early.</li></ol>
<p>The payoff is on the job. A clash caught in the model costs about $50. The same one found in the field runs $5,000 to $50,000. An unresolved clash can burn $15K to $50K a week in idle field labour. BidLight keeps that record pinned to the element, so it survives staff changes. Plans start at $260 per licence per year.</p>