Review & sign-off: visible revisions, consistent zoom, single final hash
`review-visio-docx` covers Word-centric approvals with track changes. Different Word builds render revisions differently; pictures shift when “show markup” toggles. Agree whether comments sit beside figures or only in narrative paragraphs, and ship both clean and marked copies each round with registered hashes. Discourage wholesale formatting on illustration blocks to avoid accidental rasterization.
Word review cycles: standardize Word builds, export clean vs marked hashes each round
- Before review mandate minimum Word versions, default zoom, and font embedding; participants work from downloaded task DOCX with track changes—online preview is not the decision surface.
- Editors merge conflicts each round and publish a clean baseline for the next pass; structural art changes return to Visio masters, not pixel pushes inside Word.
- At release broadcast the sole valid hash and retire old links; signed scans must pair with the final hash without same-name overwrites.
VSDX to DOCX (review) FAQ
Revision colors differ across Word installs—legal risk?
It can confuse readers—declare a baseline build; disputes rely on server-merged clean hashes and audit logs, not local colors.
Question marks on the diagram—comment only or edit Visio?
Use comments for intent, but implement structural fixes in Visio and reconvert; Word-only tweaks do not update masters.
After accepting all changes pictures drift—whose fault?
Classic process gap—revert to last clean export or reconvert from Visio and add a pre-accept layout checkpoint to the playbook.
Stale DOCX in group drives—stop wrong builds?
Publish read-only release folders with hash-verified pulls; treat chat attachments as untrusted unless rehashed.
Signed scans disagree with final DOCX page counts—evidence?
Archive scan-only packages with page counts beside clean DOCX baselines; diff signature pages against renders when challenged.