Comments and track-changes: keep callouts off gateway IDs, and reserve topology edits for .vsd masters
`annotate-visio-docx` targets Word-centric review with comments, track changes, and review threads. After .vsd→DOCX, diagrams are often pictures or exploded shapes—bubbles that cover gateways or port labels cause bad decisions. Structural questions belong back in Visio on the master .vsd with a fresh export; do not hand-edit pixels in Word. Agree minimum Word versions and font embedding, and at each round ship both a clean baseline and a marked copy with logged hashes. Move settled conclusions into body text or issue tables so knowledge is searchable, not trapped in bubbles.
Annotation workflow: standardize Word markup display; large diagram edits require .vsd rework and reconversion before closing threads
- Before review starts, mandate Word build and default zoom; reviewers work locally with track changes or comments—do not sign off from lightweight online previews alone; keep bubbles off critical labels, using a margin “open issues” table when needed.
- After each merge, publish a clean baseline for the next round; any topology change goes back to Visio on .vsd and reconverts—do not nudge pictures in Word and call it final.
- Broadcast the single authoritative final hash and retire old links; if signed scans return, store them beside the final hash—no silent overwrites without a signed baseline.
VSD to DOCX (annotations) FAQ: bubble clutter, accept-all layout collapse, clean vs marked copies
Too many comment balloons hide the main path and gateway numbers—how do we de-escalate without losing history?
Periodically migrate agreed points into body text or tables and delete stale bubbles; keep the hero diagram readable and park historical chatter on appendix pages.
Accept All Changes shifted floating pictures—tool fault or missing process?
Common process failure: roll back to the prior clean baseline or reconvert from .vsd, and add “layout review before accept all” to the checklist—Word is not kind to large floats.
Should we ban Compatibility Mode to cut markup versus layout disagreements?
Prefer modern docx and aligned Word versions; compatibility mode amplifies screen versus print differences and fuels repeat review cycles.
After reconverting .vsd, comment anchors drift—how do we preserve thread context across rounds?
Before big geometry changes, export a numbered comment summary and remap by id after reconversion; old anchors rarely survive new layouts.
Can enterprise search rely on keeping Word comment bubbles alone?
No—write decisions into body text or a controlled change log; clean saves may strip bubbles, leaving no retrievable rationale.