Unidirectional Flushing Run Data Collection Form

This template is used to document a single unidirectional flushing run from start to finish. It captures the run identification, valve actions, flushing performance, water quality measurements, and any exceptions or completion notes. The result is a consistent record you can review later for operations, troubleshooting, and audit trail purposes.

It fits both planned flushing activities and corrective flushing after water quality concerns, as long as the work follows a defined run sequence. If your team performs routine zone flushing on a schedule, this form gives you a repeatable record for each event. If the work is an emergency response, you may want to add incident-specific fields or a separate escalation log.

The operator or crew lead who actually performs the flushing run should complete it, with review by a supervisor if your process requires sign-off. That person is usually best positioned to record valve sequencing, actual velocity, residual readings, and exceptions while the work is happening. If multiple people are involved, assign one owner for the final submission to avoid conflicting entries.

Record it every time a unidirectional flushing run is performed, even if the run is short or produces no notable issues. Consistent logging helps you compare runs across zones and spot recurring low-residual areas, valve problems, or sediment release patterns. If your utility uses a separate work order system, this form can sit alongside it as the field record.

Common mistakes include leaving out the actual velocity, mixing up target and actual units, and writing vague valve notes that do not show the sequence used. Another frequent issue is recording only the final chlorine residual without noting the measurement type or the turbidity reading. Clear, field-level entries make the form useful later when someone needs to reconstruct the run.

Yes. You can add fields for crew name, work order number, map sheet, sample location, or supervisor approval if those are part of your process. If you use conditional logic, you can show exception details only when a run status indicates a problem or when the operator marks an anomaly. Keep the form focused on data you will actually use so it stays quick to complete in the field.

No, it is a field data collection form, not a replacement for operational systems or laboratory reporting. It works well as the human-readable record that complements SCADA trends, work orders, and water quality results. If you integrate it with other systems, use it to capture the operational context that automated tools often miss.

After submission, the record should be routed to the operations team or supervisor for review, with exceptions flagged for follow-up. If your process includes corrective action, the submission should trigger a work order, investigation, or repeat flush as needed. A clear post-submit path helps ensure the form is not just archived but actually used.