A flowchart is a diagram that uses standardized symbols, connectors, and arrows to represent the sequence of steps, decisions, and data flows within a process. It is used to visualize how work moves from start to finish, including who does what, when decisions are made, and how information or materials flow between activities.
Typical use in industrial and regulated environments
In manufacturing and other regulated operations, flowcharts commonly represent:
- Business processes such as order intake, engineering change, or nonconformance handling
- Production and inspection workflows, including rework and escalation paths
- Interactions between systems such as MES, ERP, PLM, QMS, and data repositories
- Compliance-relevant processes such as document control, training, or audit response
Flowcharts are often used during audits and assessments to explain how process inputs, outputs, responsibilities, and handoffs fit together. They can support, but do not replace, underlying procedures, work instructions, or system configurations.
Structure and notation
A flowchart typically includes:
- Process steps (activities or operations) shown as rectangles
- Decisions (branches such as yes/no, pass/fail) shown as diamonds
- Start and end points shown as ovals or rounded rectangles
- Connectors and arrows showing the direction of flow and sequence
- Inputs/outputs or data stores where information enters, leaves, or is recorded
In operational settings, additional annotations may show roles or departments, system boundaries, or risk and control points. When aligned with standards such as ISO 9001, the same flowchart can often serve as part of the documented description of a process.
Operational meaning
Practically, a flowchart is used to:
- Design or improve a process before implementing it in MES, ERP, or QMS
- Identify handoffs, bottlenecks, and failure points for continuous improvement work
- Clarify responsibilities between functions such as engineering, production, quality, and supply chain
- Provide a visual aid for training and for explaining processes to auditors or customers
The level of formality and detail can vary, from high-level overviews to detailed step-by-step flows used for system configuration or procedure development.
Common confusion
- Flowchart vs. process map: In many organizations, these terms are used interchangeably. “Process map” sometimes implies a higher-level view, while “flowchart” often suggests more detailed step sequencing, but there is no universal distinction.
- Flowchart vs. value stream map: A flowchart focuses on the logical sequence of steps and decisions. A value stream map emphasizes material and information flow, lead time, and waste across the entire value stream.
- Flowchart vs. work instruction: A flowchart shows the path and decision points. A work instruction describes how to perform each specific step, often with detailed parameters, tools, or acceptance criteria.
Connection to ISO 9001 context
Within an ISO 9001 quality management system, flowcharts are a common way to describe and communicate processes, their sequence, and their interaction. While not typically a formal requirement by themselves, they are often used as visual evidence that processes are defined, controlled, and understood across functions and systems.