If you've ever opened a flowchart template and wondered why some shapes look slightly different across tools, you're probably staring at the difference between two competing standards. The ISO 5807 flowchart standard vs ANSI flowchart symbols debate affects anyone who creates process diagrams for software, engineering, or business workflows. Picking the wrong one or mixing them can confuse your audience, slow down reviews, and create documentation that looks inconsistent across teams.

What is the ISO 5807 flowchart standard?

ISO 5807 is an international standard published by the International Organization for Standardization. It defines symbols, conventions, and rules for creating flowcharts that document computer programs and data processing systems. First released in 1985, it was designed to give documentation teams a shared visual language especially for software-related workflows.

Under ISO 5807, you'll find standardized shapes for processes, decisions, input/output, connectors, and terminal points. The standard also covers how to label these shapes, how to structure flow direction, and how to handle annotations. If you work in European or international engineering environments, you've likely seen ISO 5807 symbols in technical manuals and system documentation.

What are ANSI flowchart symbols?

ANSI flowchart symbols come from the American National Standards Institute, specifically the ANSI X3.5 standard published in 1970. These symbols became the default flowchart notation in the United States, particularly in business process mapping and early software development.

ANSI defines shapes like rectangles for processes, diamonds for decisions, parallelograms for input/output, and rounded rectangles (or ovals) for terminal points. Many U.S.-based organizations adopted these symbols long before ISO 5807 existed, which is why they still dominate in American business and education settings.

How are ISO 5807 and ANSI flowchart symbols actually different?

At first glance, the two standards look quite similar. Both use basic geometric shapes to represent steps in a process. But the differences matter when you're producing formal documentation or working across international teams.

Shape specifications

• Process boxes: Both standards use rectangles, but ISO 5807 specifies exact proportions and spacing guidelines more precisely.
• Decision diamonds: ANSI uses a simple diamond. ISO 5807 defines the diamond similarly but adds rules for labeling branches and handling multiple exit paths.
• I/O operations: ANSI typically uses a parallelogram. ISO 5807 includes a wider range of input/output symbols, including ones for document and manual input.
• Connector symbols: ISO 5807 provides more detailed connector conventions for linking flowcharts across multiple pages something ANSI handles less formally.
• Annotation symbols: ISO 5807 includes a dedicated annotation symbol (an open rectangle with a folded corner) for adding comments. ANSI leaves annotations less structured.

Scope and detail

ANSI X3.5 is a shorter, simpler standard. It gives you the basic shapes and says, essentially, "use these." ISO 5807 goes further by covering layout rules, naming conventions, and how to handle complex branching. If ANSI is a sketch toolkit, ISO 5807 is a full drafting specification.

Geographic usage

ANSI symbols are still the default in most U.S. organizations, educational institutions, and business process documentation. ISO 5807 is more common in European, Asian, and international engineering contexts. If your organization operates globally, you may encounter both which is where the trouble starts.

You can learn more about the different flowchart notation standards explained in our dedicated breakdown.

When should you use ISO 5807 instead of ANSI?

Choose ISO 5807 when:

• You're documenting software systems for international audiences.
• Your organization follows ISO compliance requirements.
• You need detailed annotation and multi-page connector support.
• You're working with engineering teams in Europe or Asia.

Choose ANSI symbols when:

• Your audience is primarily U.S.-based and already familiar with ANSI notation.
• You're creating internal business process maps without formal compliance needs.
• Simplicity matters more than strict specification adherence.
• You're working in an educational or training context where ANSI is the taught standard.

Can you mix ISO 5807 and ANSI symbols in one flowchart?

You technically can, but you shouldn't. Mixing standards creates confusion. A reader familiar with ANSI might misinterpret an ISO-specific symbol, and vice versa. This is one of the most common mistakes teams make especially when different team members contribute to the same document using different tools or templates.

Pick one standard per project and stick with it. If your organization doesn't have a policy, establish one. Document which standard your team uses and make sure your flowcharting tools are configured to match.

Our guide on standards-compliant software for flowcharting can help you choose tools that enforce consistent notation.

What are the most common mistakes people make with these standards?

1. Assuming they're interchangeable. While the shapes overlap, the labeling rules, spacing guidelines, and connector conventions differ. Treating them as the same leads to sloppy documentation.
2. Ignoring the standard entirely. Many people draw flowcharts freestyle, picking shapes that "look right." Without a standard, your diagrams become harder for others to read and maintain.
3. Using outdated symbols. Both standards have evolved. ANSI X3.5 was last revised decades ago, and ISO 5807:1985 is still the current version, but some tools pull from older or non-standard shape libraries.
4. Not training the whole team. If three people use ISO shapes and two use ANSI, your merged document will look inconsistent. Onboarding should include a quick rundown of which standard you follow.
5. Overcomplicating simple flows. ISO 5807's detail is valuable for complex systems, but applying its full specification to a five-step process is unnecessary overhead.

How do modern flowchart tools handle these standards?

Most modern diagramming tools Lucidchart, Microsoft Visio, draw.io, and similar platforms offer templates based on both ANSI and ISO shapes. However, they don't always enforce the full standard. A tool might give you the right shapes but not the right labeling conventions or spacing rules.

When evaluating a tool, check whether it offers dedicated ISO 5807 or ANSI X3.5 template sets, not just a generic "flowchart" library. Also look for features like auto-alignment, connector routing, and multi-page linking these help you follow the more detailed parts of the standard without extra effort.

For a deeper comparison of these two approaches, see our article on ISO 5807 vs ANSI flowchart symbols.

Quick checklist: choosing between ISO 5807 and ANSI

• Know your audience. International teams lean ISO; U.S.-focused teams lean ANSI.
• Check for compliance requirements. Some contracts or regulatory frameworks specify which standard to follow.
• Audit your current diagrams. Look at your existing flowcharts and identify which standard (if any) they follow.
• Set a team standard. Document your choice and share it with everyone who creates flowcharts.
• Configure your tools. Set up templates and shape libraries that match your chosen standard.
• Avoid mixing. If you discover mixed symbols in a document, take time to convert everything to one standard.
• Keep it practical. Use the full standard for complex system documentation. For quick internal diagrams, the basic shapes from either standard are usually sufficient.

Next step: Pull up your most recent flowchart and identify whether it follows ISO 5807 or ANSI notation. If you can't tell, that's your sign to standardize. Pick one, document the decision, and update your templates. Fifteen minutes of setup now saves hours of confusion later.