Two coordinators left mid job how does the next person see why a sleeve moved an

1
The record stays with the project, not the person. That is the whole point of running BidLight inside Revit and Navisworks. Whoever picks it up next sees the answer in the model: 1.
support@bidlight.com
asked 22 hours agoSupport Team

Answers

0
<p>The record stays with the project, not the person. That is the whole point of running BidLight inside Revit and Navisworks.</p> <p>Whoever picks it up next sees the answer in the model:</p> <ol><li>Open the issue pinned to that sleeve. Every issue sits on the element it concerns, not in someone&#39;s inbox.</li><li>Read the close. An issue closes only with proof: a screenshot, the tagged user and the model commit that fixed it. That is your why, with a name and a date on it.</li><li>Compare the export versions. Every export is versioned and diffed element by element, so you see exactly what moved between revisions. Which revision the pour was built to is right there, element by element.</li><li>Check the 6am digest. It tells each owner what they own, so nothing quietly drops when a seat goes empty.</li></ol> <p>No forensic meeting to reconstruct history. The coordination meeting sees what changed in about 15 minutes instead of a 90-minute session spent working out who moved the duct.</p> <p>The money case is simple. A clash caught in the model runs about $50. The same clash found in the field runs $5,000 to $50,000, and every week it sits unresolved can burn $15K to $50K in idle field labour. A record that survives staff turnover is what keeps those numbers down.</p>
support@bidlight.com
answered 22 hours agoSupport Team

Your answer

Browse other questions tagged  or  ask your own question.