Transcript to BPMN
From a recorded walkthrough to a BPMN 2.0 model.
Somewhere in your drive is a recording of the one person who actually knows how the process works, explaining it. Backlog.cloud turns that transcript into a validated process model: lanes for each role, tasks in sequence, gateways carrying the exact conditions that were spoken, rendered as a diagram and exported as standard BPMN 2.0 XML. Anything the speaker left vague becomes a question, not an invented branch.
The input already exists
The hard part happened in the meeting. The transcript is proof.
If you are here, you probably do not need convincing that process mapping matters. You have a concrete job: a 40-minute recording of the AP lead explaining invoice approval, and a stakeholder pack that needs a process diagram in it by Friday. The traditional route is to replay the recording at 1.5x speed with a diagramming tool open, pausing every time someone mentions a threshold, and losing an afternoon to it.
The transcript already contains the model. Every task, every handoff, every "if it is over that amount" is sitting in the text. What the afternoon of manual redrawing actually does is extract structure from prose, and that is precisely the work Backlog.cloud automates. Paste the transcript or upload the recording, and the extraction produces lanes, tasks, gateways and events, each one traceable to the sentence it came from.
The rest of this page is one worked example, end to end, so you can judge the output against the input yourself. If you want the artefact described in general terms instead, that lives on the BPMN process models page. For how to run the workshop that produces a transcript like this, see process mapping workshops.
One transcript, end to end
Ten lines of walkthrough become an invoice approval model
A fictional accounts-payable walkthrough: one person describing, one asking the questions a decent analyst asks. This is the entire input. No template, no cleanup, no markup. Watch what each sentence turns into.
Stage 1: the transcript, as pasted
Callum (BA): Take me through what happens when an invoice turns up. Start from the very first touch.
Dee (AP team lead): Everything lands in the shared AP inbox, whether the supplier emails it or sends it through the portal. A clerk keys it into the finance system and checks two things: the supplier exists in the master file, and there is a PO reference on the invoice.
Callum (BA): What if there is no PO reference?
Dee (AP team lead): Then it does not get processed. It goes straight back to the supplier with a standard email asking them to resubmit with the reference. That is the end of it until they do.
Callum (BA): And when there is one?
Dee (AP team lead): The clerk runs a three-way match: the invoice against the purchase order and the goods receipt. If it matches within tolerance, the clerk approves it for payment there and then. No sign-off above them.
Callum (BA): What counts as within tolerance?
Dee (AP team lead): Under 50 pounds variance, or under two percent of the invoice value, whichever is smaller.
Callum (BA): And outside tolerance?
Dee (AP team lead): It comes to me and I take it up with the buyer. Sometimes we get a credit note, sometimes I approve it anyway if it is close. Honestly it depends on the supplier and my judgement on the day.
Lane: AP clerk
- startEventInvoice received · Shared AP inbox, email or portal
- userTaskKey invoice into finance system
- userTaskCheck supplier master record and PO reference
- exclusiveGatewayPO reference on invoice? · No: return to supplier. Yes: continue to matching
- userTaskReturn invoice to supplier for PO reference
- endEventInvoice returned, awaiting resubmission
- userTaskRun three-way match against PO and goods receipt
- exclusiveGatewayMatch within tolerance? · See conditions below
- userTaskApprove invoice for payment
- endEventInvoice approved for payment
Lane: AP manager
- userTaskResolve variance with buyer · Outside-tolerance route only
The gateway, conditions verbatim
exclusiveGateway Match within tolerance? has two outgoing flows, each carrying the condition as it was spoken:
Within tolerance → Approve invoice for payment
"Under 50 pounds variance, or under two percent of the invoice value, whichever is smaller."
Outside tolerance → Resolve variance with buyer (AP manager lane)
"It comes to me and I take it up with the buyer."
One gap, kept honest
Dee never said how variance resolution ends. "Sometimes we get a credit note, sometimes I approve it anyway" describes judgement, not a defined route, so the manager lane does not get an invented credit-note branch and an invented override branch. It gets a question.
Open question: what are the defined outcomes of variance resolution, and is there an authority limit on manager approval of out-of-tolerance invoices?
The extracted elements are not drawn freehand. They form a process graph that is validated before anything renders: both gateways must have their outgoing flows, every flow must connect real elements, every task must sit in a lane, and the process must start and end. A deterministic layout algorithm then positions everything, lanes stacked and flow running left to right, so the same graph always produces the same picture.
In the dashboard the model appears as a rendered SVG diagram you can read in the review queue, labelled as-is because that is what Dee described: the process as it runs today, judgement calls and all. A to-be variant of the redesigned process is generated separately, so the current state and the target state never blur into one diagram.
Downloading compiles the graph to BPMN 2.0 XML conforming to the OMG specification at omg.org/spec/BPMN/2.0.2, so it opens in any tool that reads the standard.
What the XML contains
- bpmn:processThe executable process definition itself
- bpmn:laneSetOne lane per role: AP clerk, AP manager
- bpmn:userTaskEach step, verb-first, in the lane of whoever does it
- bpmn:exclusiveGatewayBoth decisions, with named outgoing flows
- bpmn:sequenceFlowEvery connection, conditions on the branching flows
- bpmndi:BPMNDiagramDiagram interchange, so the layout travels with the file
Count what made it in. Two entry channels collapsed into one start event, because Dee said they converge in the inbox. Both tolerance rules on the approval flow, exactly as spoken. One honest open question where the transcript ran out of facts. Nothing in the model exists without a sentence behind it.
Where the transcript comes from
Live call, old recording, or text you already have
The meeting bot, live in the workshop
Paste a Zoom, Microsoft Teams or Google Meet link and the bot joins the process mapping session, transcribing as the walkthrough happens. Because the meeting is typed as a process mapping workshop, the extraction listens for actors, sequences, conditions and handoffs rather than backlog items. On the Team plan, calendar auto-join means nobody even pastes the link.
A recording from before you had the tool
Upload the audio or video of a walkthrough that already happened, whether that is last month's workshop recording or a narrated screen capture of someone clicking through the finance system. It gets transcribed and processed identically. Old recordings are often the best input, because the person explaining had no idea a model would come out of it and just described the truth.
A pasted transcript
If you already have text, paste it: the export from your meeting platform, an interview transcript, typed-up notes. Speaker labels help the lane assignment but are not required. The example above is exactly this route, and it is the fastest way to judge the output on your own process today.
What to expect, honestly
A strong first pass plus a question list, not magic
The model is only as complete as the walkthrough. Ten sharp lines produced the example above, but a transcript where nobody asked "what counts as within tolerance?" would have produced a gateway with an unquantified condition and a clarification attached to it. That is the design working, not failing. An invented threshold in a finance process is a small disaster waiting for an audit.
Expect a first pass from a real, messy transcript to be a usable draft with somewhere between two and a handful of open questions. Take the questions back to the person who knows, get answers, regenerate. That loop is what a good analyst does over a week of follow-ups. Here it runs in minutes per cycle, and the questions arrive already written.
One boundary worth knowing before you start: the process model does not push to a work management platform, because a diagram is not a backlog item. It lives with the project in the dashboard and exports as BPMN 2.0 XML. Everything else the same transcript yields, and a good walkthrough also surfaces requirements, pain points and action items, goes through the review queue and pushes to your platform as normal.
FAQ
Transcript to BPMN, answered
- What file formats can I start from?
- Paste text directly, in any shape: a raw transcript, a speaker-labelled export from Zoom, Microsoft Teams or Google Meet, or your own typed notes. Or upload the source itself: audio and video recordings are transcribed for you, and a photo of a whiteboard works too. There is no required template. The example on this page is exactly the kind of loosely formatted dialogue that works.
- How are gateways inferred from the transcript?
- From conditional language, anchored to the sentence that contains it. "If it matches within tolerance" produces an exclusive gateway whose outgoing flows carry the stated conditions, in this case the 50 pounds and two percent rules exactly as spoken. A gateway is only created when someone actually described a decision. The extraction never adds a diamond to make the diagram look more complete.
- What happens if the description is rambling or out of order?
- That is the normal case, and it is fine. People describe processes with detours, corrections and "oh, unless" clauses, and the extraction reassembles the sequence from the whole transcript rather than reading it line by line. What it will not do is paper over genuine gaps. If the speaker never said what happens after a step, that surfaces as a named clarification question, not a guessed arrow.
- Can I edit the model afterwards?
- Two ways. Inside Backlog.cloud, answer the open questions in a follow-up conversation or an amended transcript and regenerate, which keeps every element grounded in something that was actually said. Or download the BPMN 2.0 XML and edit it in any modelling tool that speaks the standard, since the export includes layout information and opens cleanly elsewhere.
- Is the export real BPMN 2.0 XML?
- Yes. The download is BPMN 2.0 XML conforming to the OMG specification at omg.org/spec/BPMN/2.0.2, including diagram interchange so positions travel with the file. It is not an image pretending to be a model. It opens in standard BPMN tooling with lanes, tasks, gateways and flows intact.
- Does it work from a video recording?
- Yes. Upload the video of the walkthrough, a screen recording with narration included, and it is transcribed and processed the same way as pasted text. Audio-only recordings work identically. If the walkthrough has not happened yet, the meeting bot can join the call live instead.
- Does the process model push to Jira or the other platforms?
- No, and that is deliberate. A process model is not a backlog item, so there is nothing sensible to create in a work management platform from it. It lives with the project in the dashboard as a rendered diagram and leaves as BPMN 2.0 XML. Requirements, action items and other artefacts extracted from the same transcript push to your platform as normal, after review.
Keep going
Related workflows and resources
BPMN process models
The artefact in full: elements, validation, as-is and to-be variants.
Process mapping workshops
How to run the session that produces a transcript worth modelling.
BPMN guide
The notation in plain language: lanes, tasks, gateways, events.
Transcript to requirements
The same transcript, extracted into a structured requirements document.
Discovery meetings
Where process walkthroughs sit in the wider discovery practice.
Meeting to backlog
The wider workflow: one conversation, twelve artefact types.
That recording is a process model already. Extract it.
Create a free account, paste the transcript or upload the recording, and review the model it produces: lanes, gateways with spoken conditions, and BPMN 2.0 XML out. 3 free generations, no card.