Vapour Return System Operation Checklist

It covers the operational checks needed to confirm vapour-return line alignment, valve position, pressure control, and displaced-vapour handling during loading or onboard compression. The checklist is meant to verify that the system is ready before transfer starts and remains stable while it runs. It is not a design review or maintenance overhaul. Use it as a task checklist for the operator or DRI responsible for the transfer.

Run it before any loading, unloading, or compression activity that depends on vapour return for tank pressure control. It can also be used during shift handoff if the system stays in service across multiple operators. If the operation is non-routine, higher-risk, or involves a changed routing plan, treat the checklist as critical and complete it before the first transfer step. Do not use it as a substitute for a pre-job hazard review when one is required.

The operator or technician directly responsible for the transfer should complete it, with the DRI assigned by site procedure. In many facilities, a second person verifies key steps such as valve lineup, pressure indication, and isolation status. If your workflow uses shift supervisors, they can review completion, but the person on the equipment should perform the actual checks. Keep assignment_type flexible at import time so the tenant can choose the right owner.

It is designed to support operational discipline that aligns with OSHA-style pre-shift and pre-task inspection patterns and with site procedures for pressure-control equipment. Depending on your operation, it may also support environmental, fire-safety, or terminal-transfer requirements. The template itself does not encode a legal standard, so your site should map each checklist item to its own SOP, permit, or compliance control. If your facility handles regulated vapours, add the local reporting and escalation steps that apply.

Common failures include leaving a valve misaligned, using the wrong return path, missing a blocked vent or closed isolation, and starting transfer before pressure is stable. Another frequent issue is treating the checklist as a formality and not verifying each item at the equipment. This template helps avoid compound, ambiguous checks by keeping each item independently answerable. It also reduces the chance that a blocking condition is ignored because the operator assumed someone else had already handled it.

Yes. You should tailor the line names, valve tags, pressure limits, alarm checks, and escalation steps to your specific vapour-return system and product. Some sites will need extra items for onboard compression, inerting, or tank-specific routing. Keep each checklist item atomic so it can be answered yes, no, or N/A without interpretation. If you add site-specific limits, make sure they are reviewed by the appropriate operations or safety owner.

An ad-hoc walk-through depends on memory and often misses edge cases, especially when the operator is under time pressure. This template turns the walk-through into a repeatable task with a clear DRI, a defined sequence, and a verification step for each critical condition. That makes it easier to hand off between shifts and easier to audit after an incident or near miss. It also helps teams standardize what 'ready for transfer' actually means.

Yes. It works well alongside loading permits, shift handoff tasks, incident follow-up, and maintenance work orders. You can link it to a Kanban board for prioritization, set recurrence for routine inspections, or attach it to a runbook for transfer operations. If a failed item blocks the transfer, route it into a corrective task rather than leaving it buried in the checklist.

Treat the failure as blocking if it affects pressure control, vapour containment, or safe transfer alignment. Stop the operation if required by your SOP, notify the DRI, and document the corrective action or escalation path. Do not mark a failed safety-related item as complete without a verification step showing the issue was resolved. If the item is non-blocking, note the exception and assign follow-up work immediately.