<p>Every change reopens something. A VE swap can undo the coordination you already closed, and the new conflict may not show up until a crew meets it.</p> <p>Treat the change as a new revision:</p> <ul><li>Publish the model after the VE decision. It becomes a versioned snapshot.</li><li>Compare it to the last coordinated revision, element by element, by category.</li><li>Check which previously closed issues now involve a changed element.</li><li>Pin new issues to the affected elements and tag owners.</li><li>Let the 6am digest carry them the next morning.</li></ul> <p>What you are protecting is the work already done. Closed issues keep their screenshot, tagged user and model commit on record, so you can see exactly which ones the change touches.</p> <p>Skip the comparison, and the conflict turns into rework or idle time. An unresolved clash can burn $15K to $50K a week in idle field labor.</p> <p>The comparison takes about 15 minutes. It is the cheapest insurance on the job.</p>