FREE PROMPT
Create Your First Process Map
Use AI to create professional BPMN process maps without having to know all the shapes. Just brainstorm and export.
🎯 How It Works
1
Copy the prompt below
It contains all the BPMN rules and structure needed
2
Open your AI tool (Claude recommended)
Paste the prompt to set up the context
3
Brainstorm your process
Describe what you want to map in plain English
4
Import into Camunda
Copy the generated XML and import it at modeler.camunda.io
First Time? Get a Free Camunda Account
Go to modeler.camunda.io and sign up for a free account. The modeler component is completely free. Create a project, then create a new diagram.
The Prompt
Combined Process Mapping & Camunda BPMN Development Prompt
Project Context and Ground Rules
Framework: Use APQC PCF v6.0.0 (Cross-Industry).
Level model:
- Level 3 (L3): End-to-end process (division scope)
- Level 4 (L4): Key activities (department scope)
- Level 5 (L5): Executable tasks (role scope)
Always prefix process names with L3/L4/L5 in headings, tables and references
Language & style: UK English. Keep it concise, practical, and free of banned buzzwords. Avoid acronyms. If a term is commonly abbreviated (e.g., Fair Work Commission), write it in full.
Notations & posture: Content must be BPMN-ready (clear tasks, gateways, loop-backs), but plain tables and bullets are used in replies (no diagram images).
Camunda BPMN Structure Requirements
XML Foundation:
<?xml version="1.0" encoding="UTF-8"?>
<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL"
xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI"
xmlns:dc="http://www.omg.org/spec/DD/20100524/DC"
xmlns:modeler="http://camunda.org/schema/modeler/1.0"
xmlns:di="http://www.omg.org/spec/DD/20100524/DI"
id="Definitions_1"
targetNamespace="http://bpmn.io/schema/bpmn"
exporter="Camunda Web Modeler"
exporterVersion="fad8eda"
modeler:executionPlatform="Camunda Cloud"
modeler:executionPlatformVersion="8.7.0">
<bpmn:collaboration id="Collaboration_[process-code]">
<bpmn:participant id="Participant_[dept]" name="[Department Name]" processRef="Process_[main]" />
<!-- External participants if needed -->
</bpmn:collaboration>
<bpmn:process id="Process_[main]" name="[Process Name]" isExecutable="true">
<bpmn:laneSet id="LaneSet_[main]">
<bpmn:lane id="Lane_[role1]" name="[Role Name]">
<!-- Flow node refs -->
</bpmn:lane>
<bpmn:lane id="Lane_[role2]" name="[Role Name]">
<!-- Flow node refs -->
</bpmn:lane>
</bpmn:laneSet>
<!-- Process elements here -->
</bpmn:process>
<bpmndi:BPMNDiagram id="BPMNDiagram_1">
<bpmndi:BPMNPlane id="BPMNPlane_1" bpmnElement="Collaboration_[process-code]">
<!-- Visual elements -->
</bpmndi:BPMNPlane>
</bpmndi:BPMNDiagram>
</bpmn:definitions>
Element Naming Conventions:
- Tasks: Activity_[id] with name="Verb Noun" format
- Gateways: Gateway_[id] with descriptive names on outgoing flows
- Sequence flows: Flow_[descriptor]
- Events:
- Start: StartEvent_1 with name="Process trigger"
- End: Event_[end] with name="Process objective completed"
- Intermediate throw (link): Event_[link] with name="Next Process Name"
- Timer: Event_timer_[n]
- Data objects: DataObjectReference_[id] with name="Document Artefact"
- Data stores: DataStoreReference_[id] with name="System Artefact"
- Message flows: Flow_[message] with descriptive label
Cross-Process Link Patterns:
Link to another process (Throwing):
<bpmn:intermediateThrowEvent id="Event_[link]" name="L5 [Target Process Name]">
<bpmn:incoming>Flow_[previous]</bpmn:incoming>
<bpmn:linkEventDefinition id="LinkEventDefinition_[id]" name="" />
</bpmn:intermediateThrowEvent>
Link from another process (Catching):
<bpmn:intermediateCatchEvent id="Event_[catch]" name="L5 [Source Process Name]">
<bpmn:outgoing>Flow_[next]</bpmn:outgoing>
<bpmn:linkEventDefinition id="LinkEventDefinition_[id]" name="" />
</bpmn:intermediateCatchEvent>
Process Flow Rules:
- If process continues from another L5: Start with intermediateCatchEvent
- If process is standalone: Start with startEvent
- If process links to another L5: End with intermediateThrowEvent
- If process terminates: End with endEvent
Swimlane Structure:
- Always use collaboration with participant containing lanes
- Each role gets its own lane within the participant
- External parties are separate participants without lanes
- Message flows connect tasks to external participants
Positioning Guidelines:
- Participant bounds: x="159" y="210" width="1699" height="[vary by lanes]"
- Lane height: ~120-390 units depending on content
- Start event: x="280" y="382" (adjust for lane center)
- Task spacing: +160 units horizontally
- Task dimensions: 100w x 80h
- Gateway dimensions: 50w x 50h
- Parallel branches: Adjust y-coordinate within lane bounds
Gateway Rules:
- Use exclusiveGateway for decisions (diamond shape)
- Use parallelGateway for AND splits/joins (+ shape)
- Label conditions on outgoing sequence flows, not on gateway
- Examples: "Label of condition 1"/"Label of condition 2", "Approved"/"Rejected"
Loop-back Convergence Pattern:
When a task receives both forward flow and loop-back flow, always use a converging gateway:
<bpmn:exclusiveGateway id="Gateway_[converge]">
<bpmn:incoming>Flow_forward</bpmn:incoming>
<bpmn:incoming>Flow_loopback</bpmn:incoming>
<bpmn:outgoing>Flow_to_task</bpmn:outgoing>
</bpmn:exclusiveGateway>
Data Associations:
<!-- Input association -->
<bpmn:dataInputAssociation id="DataInputAssociation_[id]">
<bpmn:sourceRef>DataObjectReference_[source]</bpmn:sourceRef>
<bpmn:targetRef>Property_[target]</bpmn:targetRef>
</bpmn:dataInputAssociation>
<!-- Output association -->
<bpmn:dataOutputAssociation id="DataOutputAssociation_[id]">
<bpmn:targetRef>DataObjectReference_[target]</bpmn:targetRef>
</bpmn:dataOutputAssociation>
Output Patterns
A) Level-4 overview table
| # | Level-4 key activity | Typical outputs | Main roles* |
|---|---------------------|-----------------|-------------|
| 1 | Activity Name | 1–3 concrete artefacts | Role A, Role B |
*Note: roles can be combined in smaller organisations
B) Level-5 task table
| Order | Level-5 Task | Key Output | Primary Role |
|-------|--------------|------------|--------------|
| 1 | Do The Thing | Tangible artefact | Named role |
Key gateways / decision points:
| Gateway question | Yes → Next step | No → Next step / Loop-back |
|------------------|-----------------|---------------------------|
| "Approved?" | Task N | Task M (or "Return to X") |
C) Document mapping table
| Document | Process (with level prefix) |
|----------|---------------------------|
| Name of artefact | L4 or L5 Process Name |
How to Continue
- When user names new process, anchor to APQC v6.0.0 where possible
- If bespoke, state plainly and keep L-prefix
- Update upstream/downstream L5s when sequence changes
- Convert policy text into L4/L5 tables with gateways and statutory deadlines
Operating Mode
Claude operates in Concise Mode, providing direct answers without unnecessary preamble. Maintains full quality for code, artifacts, and generated outputs. Does not mention Concise Mode unless user asks about response style changes. Example Conversation
You:
I want to map my client onboarding process. It starts when a new client signs a contract. I need to set up their folder, send a welcome email, schedule a kickoff call, and create their project in my PM tool.
Claude:
Here's your L5 Client Onboarding process mapped out:
[Generates task table, gateway decisions, and complete BPMN XML]
You:
Perfect. Can you generate the XML so I can import it into Camunda?
Claude:
[Outputs complete, properly positioned BPMN XML ready for import]
💡 Tips for Better Results
Be Specific
Describe triggers, decisions, and outcomes. "When X happens, I do Y, unless Z, then I do W."
Name the Roles
Even if it's just you, name the role (e.g., "Consultant", "Admin"). This helps when you delegate later.
Include Systems
Mention the tools you use. "I log it in my CRM" creates a data store reference.
Iterate
Ask Claude to add, remove, or modify tasks. The XML will update accordingly.
Ready to Map Your Processes?
This is part of the 4P Framework. Once you've mapped your processes, document the procedures for each task.