From classic ISO notation symbols to BPMN 2.0 standard elements. A practical guide to document and optimize your company's processes.
Designing an effective flowchart requires using the right symbols. The choice of node type is not just aesthetic: it determines how the process is interpreted, facilitates communication between departments, and ensures compliance with quality standards like ISO 9001 or EFQM. This guide covers the elements available in Mapaflow and the BPMN 2.0 standard nodes toward which the platform is evolving.
Classic notation, based on the ISO 5807 standard, is the universal language of flowcharts. Easy to learn and widely recognized, it is the perfect starting point for documenting processes in any organization.
Marks the entry or exit point of the process. Every diagram must have at least one start node and one or more end nodes. Represented by an oval or rounded rectangle.
Use cases
Represents a task, action, or activity performed by a person, system, or department. It is the most common node in any diagram.
Use cases
Indicates that this activity is developed in a separate diagram. Keeps the main flow clean and allows navigation to details when needed.
Use cases
Fork point where the flow divides according to a condition (Yes / No, Approved / Rejected). Two or more alternative paths emerge from it.
Use cases
Represents a preparatory step before a main action: setting parameters, initializing variables, or preparing materials. It is a step that enables the next activity.
Use cases
Indicates that the process generates, consumes, or requires a physical or digital document. Makes it easy to identify documentation that must accompany each activity.
Use cases
Represents data storage in a system (database, file, ERP). Clearly distinguishes action nodes from information persistence nodes.
Use cases
Activity performed by a person without support from automated systems. Highlights bottlenecks and improvement points in automation processes.
Use cases
Links parts of the diagram that cannot be directly connected due to space or complexity. Very useful in large, multi-page diagrams.
Use cases
Adds comments, clarifications, or additional instructions to any part of the diagram without altering the process flow.
Use cases
BPMN (Business Process Model and Notation) is the international standard for modeling business processes, developed by the Object Management Group (OMG) and adopted by excellence frameworks like EFQM. It offers greater precision and expressiveness than classic notation, and is essential for organizations seeking ISO certification, operational excellence, or process automation.
Marks where a process or subprocess begins. In BPMN there are multiple start event types: message, timer, signal, etc. A thin circle with no fill is the most basic.
Use cases
Ends the process flow. Can be a simple end, error end, cancel end, or compensation end, each with different implications for the process.
Use cases
Occurs during process execution. Can represent message receipt, time wait, recoverable error, or signal between processes.
Use cases
Indivisible unit of work performed by a person or system. In BPMN, tasks are classified by type: Manual, User, Service, Script, Send, or Receive.
Use cases
Groups a set of activities forming a secondary process. Can be collapsed (showing only the summary) or expanded (showing the detail inside the same diagram).
Use cases
Fork where only one path is activated, based on a condition. Equivalent to the classic Decision node but more precise: clearly defines that routes are mutually exclusive.
Use cases
Splits the flow into multiple paths that execute simultaneously. All paths must complete before the process continues. Key for modeling parallel work.
Use cases
Allows one or more paths to activate simultaneously based on conditions. More flexible than XOR: combines conditional branching with possible parallelism.
Use cases
Pools represent organizations or participants in the process. Lanes are Pool subdivisions representing departments, roles, or systems. Clearly shows who does what.
Use cases
Represents communication between two distinct participants (between Pools). Differs from sequence flow (within a Pool) because it crosses organizational boundaries.
Use cases
The choice between classic notation and BPMN depends on the audience, process complexity, and the goal of the diagram.
If you work with ISO 9001, EFQM, or integrated management systems, flowcharts are a fundamental tool for documenting, auditing, and improving processes. Classic notation lets you create that documentation quickly, in a way understandable to the entire organization. With BPMN, you can also precisely represent inter-department interactions, control points, and exception events — key elements in any audit.
A well-built diagram is a management tool, not just documentation. It lets you identify bottlenecks, duplications, and non-value-adding activities. Mapaflow's global map gives you a high-level view of all company processes, while each node can link directly to the ERP, work instructions, or associated KPIs.
Create your first diagrams with classic nodes and evolve toward BPMN when you're ready.