Workflow vs business process: a sequence of tasks or the whole outcome

IBM defines a workflow as a system for managing repetitive processes and tasks that occur in a particular order. Within business process management, IBM says, a workflow can be a simple series of individual tasks, while a business process is more complex and consists of multiple workflows, information systems, data, people and their activity patterns. IBM adds that a workflow is usually drawn as a diagram or checklist.

Microsoft uses the word differently. Its Azure Logic Apps documentation defines a workflow as a series of operations that define a task, business process or workload, always starting with a trigger. In that usage, a workflow is the executable definition, and it can implement a whole business process. The sources disagree on scope, so say which meaning you intend when you write a requirement.

The Object Management Group’s Business Process Model and Notation (BPMN), version 2.0.2 published in January 2014, is the shared notation for process diagrams. The specification says it is meant for the people who design, manage and carry out business processes, while being precise enough to translate into software process components.

Take purchase to pay. The process runs from a request through a purchase order, goods receipt, the supplier’s invoice, payment and reconciliation. It has an owner, policies such as approval limits, several systems and measures such as days to pay. Each stretch of it, such as invoice intake or the weekly payment run, is a workflow with its own trigger, steps and end.

IBM describes three kinds of business process management by where the weight sits: integration-centric, with little human involvement; human-centric, built around people and typically approvals; and document-centric, built around one document such as a contract. It also gives five lifecycle stages: design, model, execute, monitor and optimise. The workflow sits mostly in the execute stage.

The finance controller owns the outcome: suppliers paid the right amount, on time, once. Four workflows serve it. Invoice intake reads each emailed invoice and matches it to a purchase order. Approval routing sends any invoice above a limit to the budget holder, much like Microsoft’s Logic Apps example that routes an order above a cost threshold to manual review. The payment run pays approved invoices each week. Exception handling sends mismatches to a clerk.

A change to one workflow, such as raising the approval limit, leaves the process intact. A change to the process, such as moving a supplier to prepayment, touches several workflows at once: intake, approval and the payment run all behave differently. That is why process owners and workflow builders need to talk before either changes anything.

Automating one workflow makes that stretch faster, but the process measure may not move if the real delay sits elsewhere. If invoices wait days for a budget holder, faster data extraction changes nothing that the supplier notices.

Microsoft describes process mining as a way to understand how processes actually run: it extracts event data from systems of record, visualises the process, and helps find root causes of delay and opportunities for automation. Looking at the whole process first tells you which workflow to automate.

These come up whenever the two levels are confused.

• Calling one automated workflow "the process" and ignoring the manual steps around it.
• Drawing the process as the policy says it runs, not as the event data shows it runs.
• Automating a workflow with nobody named to handle its exceptions.
• Mixing levels in one diagram, so that a single box means a whole department in one place and one API call in another.

Studio builds workflows: a trigger, steps that call models through Connect and tools through integrations, and approval steps that pause a run until a named person decides. Several Studio workflows can together cover parts of one business process.

Studio is not a process modelling or process mining tool, and it does not draw BPMN. Approvals exist in several parts of the platform and are not one unified inbox. Separation of duties is not enforced by the platform today: you enforce it by whom you assign to each approval step.

• Swfte Studio: build workflows with approvals
• Workflows on the Swfte platform
• How to set up human approval

Facts about other vendors and about the terms on this page were read on the pages below on 7 October 2026. Vendor plans, names and menus change, so check the vendor’s page before you rely on a detail.