Turn complicated work into a clear, shareable process. Map decisions, responsibilities, approvals and handoffs with structured BPMN workflows.
01 · Model your workflow02 · Find gaps03 · Share the process
Request
×
Approved
YOUR PROCESS PROJECT
LOCAL
Preparing workspace…
WORKFLOW CANVAS
Swimlane process map
0 steps · 0 flows
Search step names and roles
Select a shape to edit it. Drag with a mouse or touch to reposition.
Event Activity Gateway→ Sequence flow
100% in-browser editing · Files remain on this device unless you export themKeyboard: Delete · Ctrl/⌘+Z · Esc · Arrow keys
A CLEARER WAY TO WORK
From a messy workflow to a documented process.
Start with a realistic example, model roles and handoffs, then share an editable or presentation-ready artifact.
01
Map the steps
Use events, tasks, and decision gateways to represent who does what and when.
02
Review the logic
Catch missing starts, unreachable activities, dead ends, and unlabeled gateway branches.
03
Export & hand off
Download a single handoff ZIP containing editable JSON, supported BPMN 2.0 XML, SVG, process documentation and review findings, or export files individually.
Supports a practical subset of BPMN 2.0 notation and interchange. Not a workflow execution engine, full BPMN validator, collaborative editor or process-mining service.
Using Business Process Studio
Choose a process template or add lanes and steps, connect flows and document responsibilities. Review advisory findings and save editable JSON or a handoff ZIP alongside supported diagram exports.
This descriptive single-pool subset does not execute processes, conditions or full BPMN semantics. Multi-pool collaboration, message flows and subprocesses are unsupported. Unsupported XML semantics are rejected rather than silently discarded; local browser storage is not a durable backup.
Choose an editable process, BPMN subset or documentation
Project JSON: preserve the supported single-pool model and lanes.
BPMN XML: exchange the deliberately restricted descriptive subset; unsupported semantics can be rejected.
SVG or PNG: share a visual process diagram.
Markdown or handoff ZIP: deliver supported documentation and project material for review.
Practice: document a fictional review process
Create lanes for the requestor and reviewer within one pool.
Add the steps for receiving, reviewing and closing a request, then connect and label their flows.
Inspect advisory findings and save JSON before exporting the diagram or exchange format.
This is an authored documentation exercise, not an executed workflow or a BPMN conformance test.
Business process questions
Will a gateway condition run the process or contact an approver?
No. This is descriptive modeling. Conditions and process steps are not executed, and diagramming responsibilities does not send tasks or approvals.
Can I import any BPMN collaboration diagram?
No. Multi-pool collaboration, message flows, subprocesses and full BPMN semantics are outside the supported subset. Keep the original exchange file and review rejection messages rather than assuming unsupported structures round-trip.
