Process & BPMN in Word: readable gateways, swimlanes that survive paging
`process-map-vsdx-docx` covers BPMN-like flows in procedure annexes. Dense swimlanes break across pages, gateway IDs shrink unreadably, and flattened BPMN art blocks audits. Decide which IDs must remain searchable in Word text versus acceptable static art, and proof in print preview for both projector and paper. Split or duplicate context on cross-page flows instead of expecting Word to preserve connector semantics automatically. Maintain paired hashes for diagram and textual procedure versions.
Process maps: define gateway/swimlane QA, fix cross-page breaks, keep IDs searchable
- Ungroup overly deep nests before upload, ensure gateway/event labels exceed print minima, and add textual anchors for cross-page references so branches are still understandable after export.
- In Word show formatting marks and walk page breaks so primary paths are not severed; if swimlanes are illegible on paper, widen spacing or split subprocesses in Visio before reconverting—do not merely shrink pictures.
- Stamp version ids in headers or covers and bind RACI or clause numbers in the manifest; any process change must refresh both .vsdx and DOCX hashes—never text-only updates without the diagram.
VSDX to DOCX (process/BPMN) FAQ
Swimlane grids turn to mud in Word—where to fix first?
Return to Visio to reduce decorative lines, raise contrast, or split subprocesses; tweaking brightness in Word rarely fixes print legibility.
Message flows become static—will auditors object?
Declare the annex a time-stamped static snapshot and retain editable masters plus export logs to prove intentional presentation, not silent tampering.
Want automatic cross-refs between numbered clauses and shapes—supported?
Expect manual captions/SEQ fields; pilot one page before scaling so field updates do not corrupt the whole doc.
Mixed EN/CN labels wrap badly—mitigation?
Widen text boxes and harmonize paragraph styles in Visio; after export tune East Asian typography and grids, or split languages across pages to reduce squeeze.
Track Changes on—will illustrations get marked deleted?
Accept baseline revisions before embedding finals, protect diagram sections, and train reviewers not to blanket accept moves that collapse layouts.