<p>BidLight shows the 4-inch duct shift as an element-level change between two revisions, and the issue raised about it stays pinned to that duct until the fix is proven.</p> <p>Here is how it runs:</p> <ul><li>You publish from Revit, or from the federated model in Navisworks.</li><li>Every publish is a versioned snapshot. Any two revisions compare element by element, grouped by category, so the duct shows up under MEP as a change tied to the exact element, not a PDF you compare by eye.</li><li>The issue is pinned to that geometry and carries the sheet and revision it came from.</li><li>The owner sees it in their 6am digest of assigned issues.</li><li>Closing it needs proof: screenshots, user sign-off and the linked model commit that delivered the fix.</li></ul> <p>No hunting for the latest version. No two hours in the meeting figuring out who moved what. The meeting can end in 15 minutes instead of 90.</p> <p>The change and its fix live on the same record, so you stop paying for the same fix twice. A clash caught in the model costs about $50, against $5,000 to $50,000 in the field.</p>