An employee-onboarding diagram shows what HR, IT, and a hiring manager must do. It exists only as a PNG. A new security check needs to be added, but placing another box on the image leaves an uncomfortable question: who owns it?
A swimlane diagram is more than a sequence of boxes. Lane boundaries express responsibility, and cross-lane arrows express handoffs. Recovering a maintainable version means preserving both.
Disclosure: this guide is prepared by the LayerBack team. The onboarding changes below are a teaching example, not a claim about a specific organization's policy.
Source: LayerBack's existing official case. This is not a new conversion test or proof of editability; inspect the actual output file.
Inventory responsibilities before converting
Make a short inventory from the source image:
Lane: HR
Owned steps: collect information; confirm start date
Handoff: send approved request to IT
Lane: IT
Owned steps: provision access; verify device
Handoff: notify hiring manager
Lane: Hiring manager
Owned steps: approve role needs; confirm readiness
This is illustrative. Use the actual labels and ownership agreed by your process owner. If a step lies on a lane boundary, clarify its owner rather than relying on a converter to resolve the ambiguity.
Keep the full diagram in the input
Retain lane headings, containers, branch labels, and handoff arrows. A cropped screenshot that hides the lane names may still produce boxes but lose the information that makes them a cross-functional process.
If the source is rotated or compressed, obtain a clearer export when possible. For a very large diagram, separate logical sections only when you can explicitly record how they connect. Do not pretend independently recovered fragments automatically preserve the whole process.
Source: LayerBack's existing official case. This is not a new conversion test or proof of editability; inspect the actual output file.
Recover and inspect the lane structure
LayerBack's PNG-to-Visio page includes an official onboarding swimlane example and downloadable outputs. Its reconstruction workflow can recover diagram shapes and lane containers; still inspect your own result rather than assuming it will match the sample.
Open the VSDX or draw.io output and check the lane headings, each step's placement, and cross-lane endpoints. Move one ordinary step and inspect the lines. Do not infer that a recovered container has every behavior of the original editor's specialized swimlane feature.
Add the new step with an explicit owner
Suppose the change is “Confirm security training before access activation.” Decide which team owns the check and who receives its result. Place the node in that owner's lane, replace the obsolete handoff, and label any rejection route.
Now read the diagram by responsibility rather than only left to right. Ask HR, IT, and the manager what triggers their work and what they must deliver. A path can be visually connected while leaving a handoff undefined.
Review exceptions and publish the source
Check delayed approvals, missing documents, and rejected access requests if those exceptions are in scope. Have the owner verify names and conditions before sharing.
Save the original PNG, the reviewed drawing, and the ownership note. Export a reading copy for the handbook, and retain the editable file in the agreed project location. That prevents the next policy update from starting with another screenshot.
Small text, dense crossings, and custom icons may need manual correction. Reconstruction recovers what is visible, not hidden business rules.
Website conversion and preview are currently free; unlocking a diagram for download or editing requires sign-in and 10 credits. Confirm pricing, then recover one swimlane image and check its responsibility handoffs before changing the layout.
Top comments (0)