Skip to content
Glossary · Line List

What is a Line List?

A line list (also called a piping line list, line schedule, or line designation table) is the tabular master record of every piping line in a process unit or facility. Each row represents a single line and carries the critical engineering attributes: line number, nominal diameter, pipe specification, insulation, design and operating pressures and temperatures, fluid service, the source P&ID reference, and from-to connectivity. Unlike P&IDs and isometrics, which are graphical drawings, the line list is an engineering data table — the structured, tabular complement to the graphical record.
Last reviewed:

On any project of meaningful size, the line list is the document engineers reach for when they need to answer a question that the drawing alone can't answer fast enough: what spec is this line, what is its design pressure, where does it start and end, what is the test pressure and medium, what insulation does it need. The drawings show the connections; the line list specifies the engineering.

What a line list contains

  • Line number — encoding service, size, material, area, and a sequential number per the client's numbering convention.
  • Nominal diameter — the size designation that drives every component selection in the corresponding pipe spec.
  • Pipe spec / material class — the governing specification that defines materials, ratings, and component types.
  • Insulation — type and thickness, where required (heat conservation, personnel protection, freeze protection, acoustic).
  • Design pressure and temperature — the limits the line is built to.
  • Operating pressure and temperature — the conditions the line normally sees in service.
  • Fluid service — the medium the line carries (process fluid name, utility, relief, drain).
  • Test medium and pressure — how the line is hydrotested or pneumatically tested before commissioning.
  • From / to — the origin and destination of the line, expressed as equipment tags or off-page connector references.
  • P&ID reference — the drawing number and revision where the line is schematically depicted.
  • Remarks — heat tracing, sloping, special NDT, NACE compliance, or any other notes that don't fit a column.

The line list as the reconciliation layer

The line list is the document that ties together the P&ID (where lines are shown schematically), the isometric (where lines are shown spatially), and the piping material specification (which governs what components are used in each line). A line that exists on a P&ID should appear on the line list; a line on the line list should have corresponding isometrics; the spec on the line list should match the spec on the isometric BOM.

Discrepancies between these three sources indicate either a documentation error or an undocumented field modification. On brownfield work, those discrepancies are the most common single cause of unplanned cost on revamp projects.

Line lists in engineering workflows

Line lists are produced during FEED and updated through detailed engineering. They are used by:

  • Piping designers — to set up the 3D model and resolve routing decisions against the spec, design pressure, and design temperature for every line.
  • Procurement — to aggregate material requirements by spec and size, feeding the bid package and downstream purchase orders.
  • Stress engineers — to identify the lines that require formal stress analysis based on diameter, temperature, and service.
  • Construction — to sequence spool fabrication, hydrotest packages, and field installation.
  • Operations — to answer line-level engineering questions long after the project closes out.

From-to lists

A from-to list is a subset or variant of the line list that focuses specifically on the origin and destination of each line. “From” and “to” are defined as equipment tags or off-page connector references. From-to lists are particularly important in brownfield work, where understanding how existing piping connects across units is the first step in any modification scope.

Your documents, your data

Start with ten of your own documents.

Definitions are context. The fastest way to see what Armeta does for the workflow this term sits inside is to run it on your actual engineering documents.