BPMN Example: From Simple Hello World to Real-World Process Diagram

By Nikhil Gupta

BPMN Example: From Simple Hello World to Real-World Process Diagram

BPMN diagrams visualize the steps, roles, and flow of a business process in a format that both analysts and engineers can read. This article walks through two concrete BPMN 2.0 examples: a minimal "Hello World" flow and a realistic leave approval workflow, covering both the visual process diagram and the underlying XML structure.

Quick Answer: What an Example BPMN Process Should Show

Business Process Model and Notation (BPMN) is a graphical standard that serves as a universal language for business stakeholders and technical developers. A good example BPMN diagram does three things: it names each step, it shows who is responsible, and it makes the order of work explicit. Without a concrete example, non-technical users tend to misread gateways or overlook swimlanes, and the diagram fails its primary purpose.

BPMN notation is designed to be understandable regardless of the software used to create it. That means an example drawn in one tool should look and behave the same way in another. BPMN also helps align stakeholders by providing a clear and visual representation of processes, turning what would otherwise be an ambiguous email thread into a shared image of how work actually flows.

Vevos is an AI-powered platform that generates BPMN 2.0 diagrams from plain-language descriptions. Instead of dragging symbols onto a canvas, a user types a process description and receives a standards-compliant model, complete with XML. The rest of this article shows what those diagrams look like, element by element.

BPMN Basics in the Context of an Example

Every business process, from employee onboarding to invoice routing, can be drawn as a BPMN diagram. The diagram captures who does what, in what order, and under what conditions. BPMN diagrams include flow elements like events and gateways, which handle the beginning and branching of work, plus tasks that represent the work itself.

The core elements you will see in every example in this article:

A BPMN diagram can represent multiple participants using pools and lanes, and a process diagram reads left to right until the process ends in an explicit end event. Every example diagram in this article is both a visual model and an executable definition in XML format. With Vevos, users describe these elements in natural language and the platform generates the BPMN 2.0 model automatically.

Structure of a BPMN 2.0 XML Process

BPMN 2.0 defines processes using XML format, following a specification published by OMG in January 2011. The BPMN XML consists of a <process> element and a <bpmndi:BPMNDiagram> element. The <process> element holds the logical flow; the DI (diagram interchange) element holds graphical coordinates so tools know where to render each shape.

The <process> element carries attributes like id, name, and isExecutable. In addition, it may reference a targetNamespace via an http URI such as http://www.omg.org/spec/BPMN/20100524/MODEL. Inside the process definition, there are three conceptual sections:

  1. Header/meta-information: process ID, name, documentation

  2. Node definitions: <startEvent>, <task>, <exclusiveGateway>, <endEvent>; each BPMN node has specific parameters defined in XML

  3. Connections: <sequenceFlow> elements with sourceRef and targetRef attributes linking nodes

BPMN 2.0 allows manual XML writing or using a process designer. Business users typically focus on the diagram, while engines and platforms like Vevos rely on the XML to automate execution.

Hello World Example BPMN Process

The "Hello World" process is the smallest meaningful BPMN example that remains executable. It contains one start event, one task labeled "Print Hello World," and one end event, all connected by sequence flows inside a single pool named "Demo Application" with no lanes.

The XML structure looks like this:

A workflow engine executes this by triggering on the start event, running the task implementation (for instance, logging "Hello World" on 2026-09-30), then reaching the end event where the process ends. Every element is connected explicitly; no orphan nodes exist.

The image features simple geometric shapes, such as circles and rectangles, connected by arrows on a clean white surface, illustrating a basic workflow process diagram. This representation includes various elements that signify tasks, events, and pathways, showcasing the steps and participants involved in a business process.

Step-by-Step: Reading a BPMN Process Diagram

Many people see BPMN as "boxes and arrows." Reading a process diagram becomes systematic once you know three things: scope, flow, and identity.

Scope. Start with the pool name and process title. These tell you what organization and what process you are looking at. Identify the start event (thin circle) and all end events (thick circles).

Flow. Follow the sequence flow arrows from the start event forward. When you hit a gateway, read the conditions on each outgoing path. Gateways illustrate decisions within a BPMN diagram; an exclusive gateway means "exactly one path," while a parallel gateway means "all paths at once." Each step along the way corresponds to a task or sub-process.

Identity. Every diagram element maps back to an XML node with a matching id and name. If the diagram shows a user task called "Review Request" with id task3, the XML contains <userTask id="task3" name="Review Request"/>. When using Vevos, the platform auto-generates both the clean diagram and consistent XML IDs, reducing manual errors and mismatches.

Real-World Example BPMN: Leave Application Process

Consider a concrete example BPMN process diagram: an employee leave application for a fictional company called "ABC Company." There are three participants in this example BPMN process, each assigned to a lane inside a single pool.

The pool represents ABC Company. The three lanes map to three roles: Employee, Manager, and HR Department. The flow begins when an employee submits a leave request, continues with a manager review, and may involve HR for recording the leave and communicating the outcome before the process ends.

Gateways branch between "approved" and "rejected" paths, and each distinct path must terminate in an explicit end event. Based on a documented leave request model, a typical diagram of this type uses 1 start event, 2 end events, 2 user tasks, 1 business rule task, 1 service task, and 2 exclusive gateways. The example is realistic enough to map onto an actual HR workflow engine or an AI automation layer such as Vevos Conductor.

The image depicts three office workers collaborating around a conference table, reviewing documents together as part of a business process. They represent participants in a task, discussing elements of a process diagram to ensure all activities are approved and connected.

Detailed Walkthrough: Leave Application Flow Logic

This section narrates the leave application example as if you were running the process step by step.

Start event (Employee lane). The process begins when an employee creates a "Leave Request" record, for instance on 2026-10-01. This start event has no incoming flow; it simply fires.

Employee task: Submit leave details. The employee fills in dates, leave type, and reason. This is modeled as a user task tied to a form in the application. Once submitted, a business rule task checks the employee's leave balance automatically.

Manager task: Review request. The manager checks team availability and policy. The outcome sets a variable such as approvalStatus = approved or approvalStatus = rejected.

Exclusive gateway. The gateway reads approvalStatus. If rejected, flow routes to an "Inform Employee; Rejected" send task, then to an end event. If approved, flow routes to an "HR Record Leave" service task, then to a "Notify Employee; Approved" send task, then to a separate end event.

Every path from the gateway reaches a terminal state. No dangling flows exist.

Components of BPMN Used in the Examples

Both the Hello World and leave application diagrams use a consistent subset of BPMN elements. BPMN diagrams consist of four primary categories of elements: flow objects, connecting objects, swimlanes, and artifacts.

Events. Events represent occurrences that affect the flow of the process. The examples use start events (marking the beginning) and end events (marking where the process ends).

Activities. Activities represent work performed during the business process. The examples include basic tasks and user tasks. Flow Objects represent core actions within a BPMN diagram; each task label and icon should be clear enough that a new team member can read the diagram without a manual.

Gateways. Exclusive gateways route flow based on a single condition. A parallel gateway, not used in these examples, could model concurrent approvals. Sequence flows indicate the order of activities in a BPMN diagram, and message flows show communication between different participants in a process.

Swimlanes. BPMN diagrams include pools and lanes for organization. A pool represents a major participant in a process, while lanes are sub-partitions within a pool in BPMN. In the leave application, the pool is ABC Company and the lanes map to Employee, Manager, and HR Department. Data objects represent information required or produced by tasks in BPMN, such as the leave request form or the approval record.

For a full reference of BPMN symbols, including intermediate events and sub-process markers, see the Vevos cheat sheet.

From Example BPMN to Automation with Vevos

Example diagrams become useful when they can be executed, monitored, and improved in a real environment. BPMN enables automation of workflows by translating visual diagrams into executable code, and a standardized BPMN diagram creates a single source of truth for operational procedures.

Vevos lets a user type a natural-language description of the leave application process and automatically generates a BPMN 2.0 model and documentation. The platform's Conductor AI agents can then perform tasks such as sending notification emails, updating HR systems, or logging audit trails when specific BPMN tasks are reached. Process optimization can be achieved by visualizing workflows in BPMN, and BPMN diagrams can help identify inefficiencies or bottlenecks in business processes before they are automated.

Collaboration is provided through the platform: process owners, HR leaders, and managers review and comment on the same process diagram directly. Governance and compliance follow from having a single, versioned BPMN source of truth with clear definitions of when each process starts, what each step does, and how it ends.

According to Camunda's April 2026 report, 71% of organizations now use AI agents, but only 11% of agentic use cases reached production in the past year. The gap between prototype and production is exactly where structured BPMN orchestration adds value.

Next Steps: Designing Your Own BPMN Example

Example BPMN diagrams bridge the gap between informal process notes and executable workflows. A single well-built example teaches more about process design than reading the full specification.

Try this exercise: model your own approval process (expense approval, access request, or similar) starting from a written description. Use one pool, a few lanes, and only the core elements from this article: start and end events, tasks, and one exclusive gateway.

To skip the manual work, paste that plain-language description into Vevos and get a BPMN process diagram and XML you can refine visually. Moving from these concrete examples to full automation is incremental: start small, validate the process, and extend as the world of your business needs grows.

Related blog posts