01 — As-Is
From what people say to lanes and steps.
Talk or type during an interview or workshop, send patchley into a Microsoft Teams, Zoom, Webex or Google Meet call, upload one PDF or DOCX of up to 50 MB with an optional focus, a recorded interview as MP3 or WAV, or an existing BPMN file. The diagram builds up while people talk, so they see it and correct it.
Roles become lanes, decisions become gateways with their paths, and the systems and documents people mention are attached to the step where they belong.
02 — One step, up close
Each step knows who does it, with what, and what is checked.
Open a step and you see what the diagram holds about it: the role from its lane, the system it runs in, the documents it uses. Control steps are marked in blue, so the checks in a process stay visible to everyone who reads it.
With responses switched on, patchley asks follow-up questions while you describe.
03 — Versions
Say what is wrong. Earlier versions stay available.
“The underwriter checks coverage before the handler registers the claim.” Say the correction or type it: patchley shows the change on the diagram, and you apply or reject it. New elements are outlined in green, changed flows in amber.
You can also edit on the canvas. Your own edits stay in place, every applied change creates a new version, and earlier versions stay available.
04 — To-Be
Design the target, with AI agents and a person who approves.
patchley designs the To-Be from the As-Is and its analyses. Lanes come from your org chart, including a lane for the steps an AI agent takes over, and the step where a person checks and approves is part of the diagram. Then change it by voice, like the As-Is.
Redesign a single process or a whole family of subprocesses, with the As-Is one click away.
05 — Related guides