<p>Yes. Stay in Navisworks. BidLight runs inside it, so you publish straight from the federated model and close issues there too.</p> <p>How it works on a real job:</p> <ol><li>Open your federated model in Navisworks like you always do.</li><li>Publish from the model. That export gets versioned automatically.</li><li>BidLight compares it to the last version element by element, so you see what actually changed in about 15 minutes instead of a 90-minute meeting.</li><li>Pin each issue to the element it concerns, right where you found it.</li><li>Close it only with proof: a screenshot, a tagged owner and the model commit that fixed it.</li><li>The 6am digest tells every owner what they own that day, so nobody chases updates across Teams, email and Bluebeam.</li></ol> <p>For Revit users, the same record runs inside Revit. Publish from the model, compare versions, pin and close. Teams working in Procore or ACC still get the output where they need it.</p> <p>Why it matters on cost: a clash caught in the model costs about $50. The same clash found in the field runs $5,000 to $50,000. An unresolved one can burn $15K to $50K a week in idle field labour. Closing issues where you already model keeps them from surfacing on site. No tool switch required.</p>