.png)
Convert texts or transcripts into editable BPMN-style flowcharts with decision points, swimlanes, sub-processes, and linked documentation and resources.
Plain sentences, or the transcript of a meeting recording you have uploaded.
AI drafts the flowchart - Â steps, gateways, and branches with clean auto-layout.
Add swimlanes, subprocesses, run validation, attach owners, tools, SOPs, and training.
Describe your process in plain sentences or use the extracted transcript from a meeting recording you uploaded, and Wikidoc lays out the BPMN-style flowchart.
Texts become process nodes and branches
Auto-layout keeps spacing, alignment, and flow direction clean
Edit the description and re-generate, or tweak nodes directly
Everything you'd expect from a dedicated flowchart tool, inside the same workspace as your documentation.
All common node types provided
Auto-detect disconnected nodes, unlabeled branches, and dead ends
Node search to jump around big diagrams instantly
Real processes are fractal. Collapse the detail into subprocess nodes and let readers drill down only when they need to.
Link a map inside a map - a subprocess node opens its own full diagram
Navigate up and down the hierarchy without losing your place
Reuse shared subprocesses across parent processes
A diagram that answers "then what?" - who owns this process, which SOP explains step 3, what tool it runs on, and which training covers it.
Attach SOPs, training modules &Â programs
Name process owners from your org members
List the tools the process runs on, with links
Your diagrams go where your work goes - slide decks, wikis, docs-as-code repositories, or print.
PNG for slides, SVG for lossless scaling, and PDFÂ for print-ready output
Mermaid for markdown and docs-as-code workflows
JSON for data interchange and backup
Process maps change. Wikidoc keeps the receipts, the same governance your documents get.
Version history with restore for every map
Approval workflow with named approvers; self-approval blocked
Threaded comments pinned to the map, with replies and resolution
The member journey mapped including trial, join, freeze, cancel, complaint, so the answer at the front desk is the same at every studio.
Describe Friday service in plain words and get the diagram: swimlanes for kitchen, bar, and floor, with the handoffs that actually go wrong made visible.
The engagement end to end including intake, conflict check, scoping, review, sign-off, billing, with an owner on every step and the workpaper SOP linked to it.
Consultation through aftercare as one map, with the consent form and patch-test checklist attached to the steps that need them.
Olivia
Small Business Owner
Type or paste a plain-language description of the process - or start from the transcript of a meeting recording. Wikidoc's AI identifies the steps, decisions, and branches, and lays out a BPMN-style flowchart automatically. From there you edit it like any diagram.
Start and end events, process steps, decision gateways, subprocesses, swimlanes, groups, free-floating annotations, and image nodes. Nodes support custom shapes and colors, and a validation panel flags disconnected nodes and broken paths.
PNG for slides and wikis, SVG for lossless scaling, PDF for print, Mermaid for docs-as-code workflows, and JSON for data interchange. Read-only views let anyone in the org browse a map without edit rights.
Yes. Each map has an attachments panel that links SOP documents, subprocess maps, training modules, training programs, owners (org members), and the tools used in the process - turning the map into a hub for everything about that process.
Yes. Every map keeps full version history with restore, supports an approval workflow with named approvers (self-approval is blocked), and has threaded comments with replies and resolution.
