When a coordinator leaves the project how do i keep the history of who changed w

1
When a coordinator leaves, the history doesn't leave with them, because it was never stored in their head. BidLight keeps one live record of the project inside Revit and Navisworks.
support@bidlight.com
asked 1 hour agoSupport Team

Answers

0
<p>When a coordinator leaves, the history doesn&#39;t leave with them, because it was never stored in their head. BidLight keeps one live record of the project inside Revit and Navisworks. Every export is versioned and compared element by element, so &quot;who changed what&quot; is answered by the record, not by whoever is still around to remember.</p> <p>What a new coordinator inherits on day one:</p> <ol><li>Versioned exports of every model, diffed element by element. They see what changed and when in about 15 minutes, not a 90-minute meeting spent reconstructing it.</li><li>Issues pinned to the element they concern, each closed only with proof: a screenshot, a tagged user and the model commit that fixed it. The reason stays attached to the element.</li><li>The 6am digest. Every owner gets what they own, daily, so accountability doesn&#39;t depend on one person chasing.</li><li>The project view that shows who is behind while there is still schedule to recover.</li></ol> <p>That&#39;s the point. Scattered updates across Teams, email and Bluebeam walk out the door with the person. A pinned, versioned record stays. And it protects the job: an unresolved clash can burn $15K to $50K a week in idle field labour while nobody can find the issue.</p>
support@bidlight.com
answered 1 hour agoSupport Team

Your answer

Browse other questions tagged  or  ask your own question.