What should i know about where your estimating hours actually went last month
1
Most of last month's coordination hours probably went to chasing changes rather than resolving them: comparing exports side by side, hunting for issues across Teams, email and Bluebeam, and sitting…
add comment
Answers
0
<p>Most of last month's coordination hours probably went to chasing changes rather than resolving them: comparing exports side by side, hunting for issues across Teams, email and Bluebeam, and sitting in meetings working out who moved a duct.</p>
<p>BidLight runs inside Revit and Navisworks. Every publish is a versioned snapshot, and any two revisions compare element by element, so you see what changed, who published it and when. Issues are pinned to elements, and each owner gets a 6am digest of what they own.</p>
<p>The numbers add up fast. About 11 hours a week go to working out which model version is current. A 90-minute coordination meeting is often spent finding out who moved what. With the comparison, that takes about 15 minutes.</p>
<p>Those hours go back to closing issues. An issue closes with a screenshot, a tagged user and the linked model commit, so it stays closed.</p>