In Business Process Model and Notation (BPMN), clarity is paramount. A process diagram is not just a drawing; it is a contract between business stakeholders and technical developers. The most critical element of this contract is the Task. A task defines a specific unit of work within a process, but it must also communicate how that work is performed.

This tutorial deconstructs the seven fundamental BPMN task types. We will explore the distinction between human work, automated system services, and message exchanges, ensuring you can model complex architectures with precision.

1. The Core Philosophy: What vs. How

Before diving into specific task types, it is essential to understand the dual nature of a BPMN task. The task description relies on two distinct components:

• The Task Name (What): Explains the business activity or the result of the work (e.g., “Charge Payment”).
• The Task Marker (How): Explains the execution method (e.g., Automated System vs. Human User).

By mastering these markers, you ensure that the diagram accurately reflects the operational reality of the system.

2. Automated System Work: Service Tasks

The Service Task represents work performed automatically by a system or service without direct human involvement. This is the “back-end” work of your process.

Key Characteristics

• Marker: A small gear symbol (⚙️).
• Execution: The process engine invokes an application, web service, API, or automated function.
• Constraint: Do not use a Service Task simply because software is involved. If a human performs the main work through an application, a User Task is more appropriate.

Real-World Examples

• Call a payment service.
• Retrieve a customer credit score.
• Create an invoice in an ERP system.
• Update a CRM record.

Example Flow

Consider an order processing sequence:

1. Validate Order
2. Service Task: Charge payment service
3. Confirm payment

3. Communication: Send and Receive Tasks

Processes often interact with external participants. BPMN distinguishes between the act of sending a message and the act of waiting for one.

Send Task

A Send Task represents the dispatch of a message to another participant, system, or process.

• Marker: An envelope/message symbol (✉️).
• Completion: The task completes immediately when the message has been sent.
• Crucial Distinction: It does not represent waiting for a reply. If you need to wait for a response, you must use a Receive Task or an Intermediate Message Catch Event.

Receive Task

A Receive Task represents a process activity that explicitly waits for a message to arrive.

• Marker: An envelope/message symbol (✉️).
• Behavior: The process remains at this task until the expected message arrives.
• Usage: Useful when message reception is a significant step. For event-oriented designs (waiting for one of several possible events), an Intermediate Message Catch Event is often preferable.

Example Flow: Send contract → Receive Task: Receive signed contract → Activate account.

4. Human Interaction: User vs. Manual Tasks

One of the most common modeling errors is conflating human work. BPMN separates tasks based on whether the work is digitally managed or purely physical.

User Task

A User Task represents work performed by a person with assistance from a software application. This is the standard for digital workflows.

• Marker: A person-shaped marker (👤).
• Context: The work occurs through a workflow system or business application.
• Requirement: The system must be able to assign, track, or manage the task.

Manual Task

A Manual Task represents work performed by a person outside a workflow engine or business application. These are physical or analog actions.

• Marker: A hand symbol (✋).
• Context: These tasks are not normally managed or completed by the process engine.

Decision Matrix: How to Choose

Action	Correct BPMN Task Type
Inspect physical goods	Manual Task
Record inspection result in quality system	User Task
Automatically validate recorded data	Service Task

5. Decision Logic: Business Rule and Script Tasks

Not all tasks are about data entry or sending messages; some are about calculation and logic.

Business Rule Task

This task evaluates business logic using a rules engine or decision service. It is vital for separating policy from process flow.

• Marker: A table/grid symbol (📋).
• Benefit: Allows policies to change without redesigning the entire process.
• Output: Typically returns a result (e.g., “Eligible”, “Ineligible”, “Requires Manual Review”).

Script Task

A Script Task represents executable logic performed directly by the process engine or execution environment.

• Marker: A document/code symbol (
• Usage: Best for small, self-contained pieces of logic (e.g., “Normalize text”, “Calculate total value”).
• Warning: Avoid using script tasks for large or business-critical logic. Use a Service Task or Business Rule Task for better governance and reusability.

Conclusion

Mastering BPMN task notation is about more than just drawing shapes; it is about defining the execution model of your business. By correctly distinguishing between Service Tasks (automated), User Tasks (digital human), and Manual Tasks (physical human), you create a blueprint that developers can implement without ambiguity.

To facilitate this level of precision in your enterprise architecture, we highly recommend using Visual Paradigm BPMN as your primary modeling tool. Its robust capabilities support complex notations and seamless integration with development environments.

Furthermore, to accelerate the design process and ensure compliance with best practices, leverage AI integration within Visual Paradigm. AI-driven assistance can help validate your task markers, suggest optimal process flows, and automatically generate documentation, ensuring your architectural diagrams are both technically accurate and strategically sound.