Our coordinator just gave notice how do we keep the record of why decisions were
1
The record shouldn't live in one person's head or inbox. When a coordinator leaves, the why behind each decision has to still be sitting on the element it concerns. That's what BidLight does.
add comment
Answers
0
<p>The record shouldn't live in one person's head or inbox. When a coordinator leaves, the why behind each decision has to still be sitting on the element it concerns.</p>
<p>That's what BidLight does. Issues are pinned to the element they concern and close only with proof: a screenshot, a tagged user and the model commit that fixed it. Every export is versioned and compared element by element, so the history of what changed, who moved it and when stays with the model, not with the person who happened to be running coordination.</p>
<p>So when someone walks, the next coordinator picks up the same live record inside Revit and Navisworks. They see what changed in about 15 minutes instead of booking a 90-minute meeting to reconstruct it. The 6am digest still tells every owner what they own.</p>
<p>What to do this week:</p>
<ol><li>Move open issues onto the elements in BidLight before the last day.</li><li>Close them with screenshot, tagged user and model commit, not a verbal handoff.</li><li>Export and save the current versioned model so the baseline is captured.</li><li>Add the incoming coordinator to the 6am digest and the project view.</li><li>Review the element-by-element comparison together once, while the outgoing coordinator is still around.</li></ol>
<p>Get this wrong and an unresolved clash can burn $15K to $50K a week in idle field labour. Keeping the record on the model is cheaper than losing it.</p>