The short answer: a Process Flow Diagram (PFD) communicates the process—major equipment, principal streams, and key operating data. A Piping and Instrumentation Diagram (P&ID) communicates the implementation intent—piping, valves, instrument tags, signals, control loops, and safeguards needed to design, operate, and maintain the system.
The cleanest test is the reader’s decision. If they need to understand what the process does, start with a PFD. If they need to know what to install, isolate, operate, or troubleshoot, the missing detail belongs on a P&ID. Neither drawing replaces piping layouts, isometrics, loop diagrams, datasheets, logic narratives, or the project’s approved design basis.
Standards check: last reviewed August 20, 2026. ISA now lists ISA-TR5.1.04-2026 specifically for instrumentation and control content on PFDs and P&IDs. ISO 10628-1:2014, which defines classification, content, representation, and drafting rules for chemical and petrochemical flow diagrams, was reviewed and confirmed current in 2026.
What the 2026 ISA report changes—and what it does not
ISA’s public standards notice describes ISA-TR5.1.04-2026 as guidance for developing instrumentation and control content on PFDs and P&IDs that stays consistent and understandable from design through operation and maintenance. That is a useful new authority for the boundary this guide explains.
It does not mean every PFD now needs every instrument, or that every organization must draw identical P&IDs. A technical report supplies application guidance; the project still needs a declared drawing standard, content matrix, tag convention, lifecycle state, and owner. ANSI/ISA-5.1-2024 remains the cited ISA basis for depicting and identifying instrumentation and control functions. ISO 10628-1 remains the broader process-diagram reference for chemical and petrochemical applications.
The practical change for a drawing team is simple: stop deciding content by how much space remains on the sheet. Decide it by the drawing’s job and document that boundary.
A four-step decision procedure
- Name the reader’s decision. Process understanding and balance review point toward a PFD. Isolation, safeguards, line definition, controls, construction interfaces, or troubleshooting point toward a P&ID or a downstream document.
- List the facts that decision requires. If the reader needs only major equipment and principal streams, do not add a forest of valves. If the reader must identify a drain, trip, tie-in, or signal path, the PFD is no longer sufficient.
- Choose the drawing family before placing symbols. A dense PFD is not automatically a P&ID. The title block, legend, tags, and content rules have to agree with the claimed deliverable.
- State the boundary. Record the standard, project convention, issue purpose, revision state, battery limits, and which facts live in other documents.
What belongs on a PFD
A useful PFD normally includes:
- major process equipment and stable equipment IDs;
- principal process streams and flow direction;
- stream numbers and a corresponding material balance where the project uses one;
- key operating temperature, pressure, flow, and composition data; and
- only the control concept needed to explain process behavior.
A PFD deliberately omits implementation detail. It does not become “more complete” by shrinking every valve and instrument onto the same sheet. That usually makes the process story less legible while still failing to provide a controlled P&ID.
PFDs are commonly useful for process selection, heat and material balance review, early design communication, training, and explaining operating cases. A project may show a major control concept—such as level control on a feed tank—when it is essential to understanding the process. That does not obligate the PFD to show every transmitter, hand valve, signal type, or maintenance bypass.
What belongs on a P&ID
A useful P&ID adds the detail required to define piping and control intent:
- equipment nozzles and equipment interfaces;
- process, utility, start-up, shutdown, drain, vent, bypass, and relief lines within scope;
- line identifiers, sizes, classes, spec breaks, and flow direction;
- manual, actuated, check, relief, and specialty valves;
- instrument bubbles, functional identifiers, loop numbers, and signal types;
- control valves, interlocks, trips, alarms, and safeguards at the required design maturity; and
- tie-ins, battery limits, vendor boundaries, and references to related documents.
A P&ID is still schematic. It defines connectivity and function, not the scaled three-dimensional route. It may show that line 2"-PW-101 connects a tank, isolation valve, pump, control valve, and downstream boundary; it does not tell a fabricator the pipe’s exact coordinates, slope, support locations, or weld sequence.
Worked example: T-101 and P-101A
Consider a feed tank T-101 supplying pump P-101A.
On the PFD, show the feed stream entering T-101, the tank and pump IDs, the product stream leaving the pump, flow direction, and the operating or balance data needed to explain the process. If tank level control is essential to the operating story, show the control concept at the level of detail the PFD convention allows.
On the P&ID, preserve that same topology, then add the implementation facts: the tank nozzle boundary, suction isolation valve HV-101, pump interfaces, discharge line identification, flow transmitter, flow indicating controller FIC-101, control valve FV-101, signal types, pressure indication, drains, vents, bypasses, relief path, and tie-ins that exist in the approved scope.
Do not invent a line class, valve type, fail position, alarm setpoint, or instrument range just to make the drawing look finished. Mark missing design inputs as unresolved and route them to the responsible discipline.
PFD vs P&ID comparison
| Question | PFD | P&ID |
|---|---|---|
| Primary job | Explain process and balances | Define piping and control intent |
| Equipment | Major equipment | Equipment, nozzles, interfaces |
| Lines | Principal process streams | Process, utility, drain, vent, bypass, relief |
| Valves | Only process-critical valves, if useful | Valves needed to implement and operate the design |
| Instrumentation | Essential control concept | Tags, loops, signal types, alarms and trips |
| Typical readers | Process design, review, training | Engineering, hazard review, operations, maintenance, construction |
| Not sufficient for | Construction or isolation planning | Physical pipe routing and dimensions |
Common failure modes
- Using a PFD for a detailed hazard review: the team discusses safeguards that are not actually represented on the controlled drawing.
- Using a P&ID as a piping layout: connectivity is mistaken for physical routing, dimensions, or accessibility.
- Calling every process drawing a flowchart: a generic flowchart cannot carry the equipment, line, valve, instrument, and signal vocabulary expected in process engineering.
- Copying symbols without a project legend: a familiar-looking bubble or line style is assumed to mean the same thing across owners, regions, and software libraries.
- Letting tags drift between drawings: equipment IDs or stream names change on the P&ID but not on the PFD and balance documents.
- Hiding uncertainty: missing sizes, classes, fail states, ranges, or alarm logic are silently filled with plausible-looking values.
- Overloading one sheet: process explanation, piping definition, loop wiring, logic, and physical layout compete until none of them is reviewable.
Pre-issue review checklist
Before issuing either drawing, verify:
- the title and deliverable type match the actual content;
- the standard, owner convention, issue purpose, and revision state are named;
- equipment and stream IDs agree with the process basis and related drawings;
- every line and symbol style used on the sheet appears in the legend or controlling standard;
- battery limits, vendor packages, tie-ins, and off-page connectors are unambiguous;
- unresolved design facts are visibly unresolved, not guessed;
- the PFD remains readable as a process story;
- the P&ID contains the detail required by its current design phase; and
- reviewers know which facts belong in isometrics, loop diagrams, datasheets, cause-and-effect charts, logic narratives, or operating procedures.
Limitations
This boundary is durable, but the exact content is project-specific. Industry, owner, licensor, jurisdiction, and lifecycle requirements may add or remove items. The cited public ISA pages describe the standards’ scope; they do not replace access to the full documents or the project’s licensed copies. ISO 10628-1 applies to chemical and petrochemical process diagrams and explicitly does not cover electrical engineering diagrams.
An AI-generated drawing is a draft until qualified people verify topology, tags, specifications, safeguards, and interfaces. A visually valid P&ID can still be operationally wrong.
Start with structured facts
The best input is not “draw a water process.” Write an equipment-and-connection list with the drawing purpose, tag convention, lines and utilities in scope, required instruments and safeguards, boundary points, and explicit unknowns. Then use ChatDiagram’s P&ID maker to draft and revise the topology conversationally.