Setting up a flow path correctly means putting every valve in the path into its right state, and for anything more complex than a single line that is easy to get wrong from memory. A valve lineup checklist is the documented answer: a sheet that names every valve involved in a specific operation and states whether it should be open or closed, so the operator can set and verify the whole path against a written list rather than trusting recollection. This guide explains what a lineup checklist contains, how it is used for operations like product transfers and tank switches, and how valve-position telemetry in SCADA can cross-check the manual sheet.
Valve Lineup Checklist in one line: A valve lineup checklist is a document that lists every valve in a flow path for a specific operation, such as a product transfer or a tank switch, together with the state each valve must be in, open or closed. The operator uses it to set and then verify the lineup valve by valve, checking each off, so the whole path is confirmed correct before the operation begins. It turns a complex alignment into a written, checkable list, and SCADA valve-position telemetry can cross-check it to catch a misaligned valve before flow starts.
A valve lineup checklist captures, in writing, exactly how every valve in a flow path must be set for a particular operation. Each valve is identified specifically by its tag or clear description, and against it the checklist states the required position, open to make part of the path continuous or closed to block an unwanted branch, drain, or cross-connection. The result is a complete specification of the lineup for one operation: not a general list of the system's valves, but the precise open-or-closed pattern that directs fluid along the intended route and nowhere else.
The checklist is specific to the operation, because the same physical system supports many different lineups. Filling tank A from a truck requires a different pattern of open and closed valves than filling tank B, and a transfer from one vessel to another differs again, so a facility often has a distinct lineup checklist for each defined operation. Having the correct pattern written down for each case removes the need to reason it out afresh every time, which is where errors creep in, and gives every operator the same authoritative reference for how a given operation should be aligned.
In use, the checklist is worked through methodically, valve by valve, with each item set and then checked off as confirmed. That check-off is what distinguishes a lineup checklist from a mental intention: it forces the operator to positively account for every valve on the list, so none is overlooked and there is a record that each was set and verified. Because the list includes the valves that must be closed as well as those that must be open, it guards against both a broken path and an unwanted one, which are the two ways a lineup goes wrong.
The classic use of a valve lineup checklist is a product transfer, where fluid is moved from one point to another and must go to the right destination without diverting or contaminating anything on the way. Before the transfer starts, the operator uses the checklist to open every valve that makes the intended path continuous and to close every valve that could send product somewhere it should not go, then verifies the whole pattern. Only when the checklist is complete and confirmed does the transfer begin, so the alignment is proven before any product moves rather than discovered wrong once it is flowing.
Tank switching is a particularly important case, because it involves changing which tank is receiving or supplying while an operation continues, and a mistake can overfill a tank or draw from an empty one. The lineup checklist for a tank switch spells out the sequence and end state of the valves so the flow is moved from one tank to another cleanly, opening the path to the new tank and closing the path to the old one in the right order. Because overfilling or misdirecting product during a switch has real safety and environmental consequences, having the exact valve states written down and checked off is a strong safeguard for these operations.
Beyond the immediate operation, the completed checklist is a record that the lineup was done correctly. It shows which valves were set and confirmed, by whom, for that operation, which supports handover between shifts and gives an audit trail if a question arises later about how a transfer was aligned. Treating the checklist as both a working tool during setup and a record afterward gets full value from it, so it protects the operation as it happens and documents that the protection was applied.
Where valves report their position electronically, SCADA can cross-check the manual lineup checklist against what the field is actually reporting, adding an independent layer to the confirmation. A checklist is completed by a person, and a person can tick a valve as correct while the valve is actually in the wrong state, either by misreading it or by operating the wrong one. When those valves send position feedback to SCADA, the reported positions can be compared with the checklist's required states, and any disagreement, a valve the checklist says should be closed but that reports open, is flagged before flow starts.
Process readings extend the cross-check beyond just position sensors. Even for valves that do not report their position, the pressures and flows that appear once a path is pressurized can reveal whether the lineup is really as intended, since a path that should be open but reads no flow, or a section that should be isolated but shows pressure, points to a valve that is not where the checklist claims. Using both reported positions and process behavior gives a fuller check on whether the physical alignment matches the documented one, catching misalignments that a paper check alone might pass.
A cloud SCADA platform such as Merobix makes this cross-check practical across many sites and available to more than just the person at the valve. Because reported valve positions, levels, and flows are shown on shared live displays and retained as trends, an operator setting up a transfer, and a supervisor watching centrally, can both see whether the field agrees with the intended lineup before the operation is committed, and can keep watching as it proceeds. If a tank switch is starting and a valve position or a level trend does not match the planned lineup, the mismatch is visible immediately rather than after product has gone the wrong way. The manual checklist remains the operator's primary discipline, especially for the manual valves telemetry cannot see; the SCADA cross-check turns the reported part of the lineup into an automatic, always-watching second confirmation that catches a misaligned valve before a transfer starts.
A valve lineup checklist is the document that lists every valve in a flow path and the state it must be in for a specific operation, used to set and verify the lineup. A line walkdown is the physical act of walking the system to confirm valve positions in the field. In practice the walkdown is often how an operator verifies the states the checklist specifies, so the two work together: the checklist says what the lineup should be, and the walk confirms it in the field.
Because a lineup goes wrong in two ways: a valve that should be open being closed breaks the intended path, and a valve that should be closed being open creates an unwanted path that can divert product, overfill a vessel, or cross-contaminate streams. Listing both the required-open and required-closed valves guards against both failures. Checking off every valve, in either state, forces the operator to positively account for the whole path.
For valves that report their position, SCADA compares the reported open or closed state against what the checklist requires and flags any disagreement before flow starts. Process readings extend this even to valves without position sensors, since unexpected pressure or missing flow can reveal a valve that is not where the checklist claims. This gives an automatic, independent second confirmation of the alignment that a manual check alone might miss.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.