SOPs, Document Control & Shift Handoffs

Water and wastewater facilities depend on clear procedures and reliable communication. Operators may work different shifts, equipment may be taken out of service, temporary operating conditions may be established, and process changes may occur between one operator leaving and another arriving.

Standard Operating Procedures, controlled documents, and effective shift handoffs help ensure that important information is not lost and that work is performed consistently. Good document control also prevents employees from relying on outdated procedures that no longer match the facility, equipment, permit, or operating strategy.

What Is a Standard Operating Procedure?

A Standard Operating Procedure, commonly called an SOP, is a written procedure that explains how a defined activity should be performed.

An SOP may address:

• routine equipment operation;
• startup and shutdown;
• sampling;
• laboratory procedures;
• chemical handling;
• maintenance activities;
• emergency response;
• process-control actions;
• recordkeeping;
• other recurring operational tasks.

The purpose of an SOP is to make the expected procedure clear, repeatable, and consistent.

SOPs Reduce Variation

Without a written procedure, different operators may perform the same task differently.

That variation can create problems such as:

• inconsistent treatment performance;
• missed safety steps;
• incorrect sampling;
• equipment damage;
• poor documentation;
• confusion during emergencies.

A well-written SOP reduces unnecessary variation while still allowing appropriately certified operators to use professional judgment where required.

An SOP Should Be Specific to the Facility

A generic procedure from another plant may be useful as a reference, but it should not automatically be adopted as the operating procedure for a different facility.

Facility-specific SOPs should reflect:

• actual equipment;
• actual piping and valves;
• local operating ranges;
• chemical systems;
• instrumentation;
• permit requirements;
• safety procedures;
• staff responsibilities.

A procedure that names equipment or controls that do not exist at the plant is not useful during actual operation.

Basic SOP Structure

A practical SOP commonly includes:

• title;
• purpose;
• scope;
• responsible personnel;
• safety precautions;
• required tools or materials;
• step-by-step procedure;
• operating limits or trigger values;
• required records;
• conditions requiring escalation;
• approval information;
• revision date or revision number.

The exact structure can vary, but users should be able to identify what the procedure covers and how to perform it correctly.

Process-Control SOPs Have Special Requirements

Pennsylvania operator-certification rules give process-control SOPs a specific regulatory role.

When an SOP is used to allow an operator to implement predetermined process-control actions, it must operate under the operator-certification framework.

Such SOPs should clearly identify:

• the operator in responsible charge;
• the personnel authorized to use the SOP;
• the treatment process covered;
• the operating triggers;
• the actions associated with those triggers;
• when the operator in responsible charge must be contacted.

These requirements are covered in more detail in the Pennsylvania SOPs and Process Control article.

Current Procedures Must Be Available

Operators should be able to obtain the current approved procedure where the work is performed.

DEP guidance recommends that current SOP copies be readily accessible to the personnel actually performing the activity.

Availability may be provided through:

• a controlled paper manual;
• an approved electronic document system;
• workstation access;
• another controlled system that provides the current version.

A procedure that exists only in an office file but cannot be accessed during an operating problem provides little practical value.

Document Control

Document control is the system used to ensure that employees use the correct version of an approved document.

Controlled documents may include:

• SOPs;
• operating manuals;
• sampling plans;
• emergency-response procedures;
• laboratory procedures;
• maintenance instructions;
• inspection forms;
• checklists;
• permit-related procedures.

The main goal is simple: workers should not accidentally follow an obsolete procedure.

Identify the Document Clearly

A controlled document should be easy to identify.

Useful identification may include:

• document title;
• document number;
• revision number;
• effective date;
• page number;
• approving person;
• approval date.

This information helps operators confirm that they are using the current approved version.

Revision Control

Operational documents must sometimes be revised because equipment, regulations, permits, procedures, or operating experience change.

A controlled revision process should answer:

• What changed?
• Why was it changed?
• Who approved the change?
• When does the new version become effective?
• What happens to the old version?

Without revision control, several conflicting versions of the same procedure may remain in use.

Remove Obsolete Copies

When a new version becomes effective, obsolete working copies should be removed or clearly marked so they are not accidentally used.

Old copies may need to be retained for historical or regulatory reasons, but archived documents should be clearly distinguished from current operating copies.

For example, an archived procedure might be labeled:

Superseded - For Historical Reference Only

The purpose is to preserve history without creating operational confusion.

Electronic Document Control

Electronic SOP systems can make procedures easier to search and distribute, but they also require controls.

Good electronic document control includes:

• restricted editing permissions;
• revision history;
• approval records;
• controlled publication of current versions;
• backup;
• protection from accidental deletion;
• clear identification of obsolete documents.

For Pennsylvania process-control SOPs maintained electronically, DEP guidance emphasizes protection against undetectable alteration and consistency with the approved official version.

Do Not Allow Uncontrolled Editing

If every operator can change the official SOP at any time, the facility no longer has a controlled procedure.

Operators may identify needed improvements, but changes should go through the facility's review and approval process.

Temporary operational instructions may sometimes be necessary, but they should be clearly identified, approved as required, communicated to affected personnel, and later incorporated into controlled documents if they become permanent.

Review Procedures Periodically

A procedure can become outdated even when nobody intentionally changes it.

Review may be needed after:

• equipment replacement;
• process modification;
• chemical change;
• permit revision;
• regulatory change;
• incident or near miss;
• repeated operating problem;
• staff feedback;
• major maintenance work.

Periodic review helps confirm that the document still matches actual facility conditions.

Operators Should Report Procedure Problems

An operator who discovers that an SOP is inaccurate, unclear, unsafe, or impossible to follow should report the issue.

The operator should not quietly create a personal version of the procedure and leave the official document unchanged.

Examples of problems that should be reported include:

• wrong valve identification;
• incorrect equipment number;
• outdated setpoint;
• missing safety step;
• unavailable chemical or equipment;
• conflicting instructions;
• changed permit requirement.

Training on Revised Procedures

Changing a document does not automatically change employee behavior.

When a significant procedure is revised, affected staff should be informed and trained as appropriate.

Operators should understand:

• what changed;
• why it changed;
• when the new procedure takes effect;
• whether old practices are still permitted;
• what records must be completed.

Training or acknowledgment may need to be documented for critical procedures.

Shift Handoffs

A shift handoff transfers operational responsibility from one operator or crew to another.

A good handoff provides the incoming operator with enough information to understand current plant conditions without rediscovering important problems independently.

Shift handoffs are especially important at facilities operating continuously.

What Should Be Communicated at Shift Change?

Important handoff information may include:

• equipment out of service;
• equipment operating manually;
• temporary piping or valve arrangements;
• alarms;
• abnormal process readings;
• laboratory results;
• chemical-feed changes;
• tank or reservoir conditions;
• high-flow or storm conditions;
• maintenance in progress;
• contractors onsite;
• pending samples;
• permit or compliance concerns;
• instructions from management;
• required follow-up actions.

The handoff should focus on information that affects what the incoming operator needs to know or do.

Pending Work Must Be Clear

Incomplete tasks are a common source of shift-change errors.

The outgoing operator should clearly identify:

• what remains unfinished;
• why it is unfinished;
• what action is expected next;
• the required completion time;
• who else is involved.

Do not assume the incoming operator will notice an unfinished task automatically.

Temporary Operating Conditions

Temporary configurations require special attention during handoff.

Examples include:

• a valve normally open that is temporarily closed;
• a pump placed in manual mode;
• a chemical pump operating at a temporary setting;
• a treatment unit removed from service;
• a temporary bypass line;
• an alarm intentionally disabled during maintenance.

These conditions can become dangerous when the next shift assumes the plant is in normal configuration.

Communicate the Reason for Important Changes

Knowing that a setting changed is useful. Knowing why it changed is even more useful.

For example:

Chlorine pump changed from 35% to 45% at 14:20 because entry-point residual dropped from 1.6 mg/L to 1.1 mg/L. Recheck scheduled for 15:00.

This entry tells the next operator:

• what changed;
• when it changed;
• why it changed;
• what follow-up is required.

Use Both Written and Verbal Handoffs for Important Conditions

A written log provides a permanent record, but significant conditions are often best communicated verbally as well.

Examples include:

• serious equipment failures;
• compliance risks;
• unusual temporary configurations;
• ongoing emergencies;
• complex maintenance;
• conditions requiring immediate follow-up.

Verbal communication allows the incoming operator to ask questions, while the written record preserves the information.

Incoming Operators Should Review the Plant

A handoff should not rely only on conversation.

The incoming operator should review relevant information such as:

• operating log;
• alarms;
• SCADA status;
• laboratory results;
• maintenance status;
• chemical inventories;
• critical process readings.

Where appropriate, the operator should also perform a physical walkthrough.

Walkthroughs Can Reveal Missed Conditions

A physical inspection may identify conditions not fully reflected in the log.

Examples include:

• leaks;
• unusual noise;
• odor;
• overflow;
• vibration;
• chemical container problems;
• equipment left in manual mode;
• unsafe housekeeping conditions.

Written records and direct observation should support each other.

Shift Handoff Is a Two-Way Process

The incoming operator should ask questions when information is unclear.

Useful questions include:

• What equipment is unavailable?
• What changed during the previous shift?
• What needs immediate attention?
• Are any samples due?
• Are there unresolved alarms?
• Are there unusual process conditions?
• Is any temporary procedure in effect?
• Has management or DEP been contacted about anything?

A rushed handoff that leaves uncertainty can create operational mistakes.

Do Not Rely Only on Memory

Operators may remember important events during a shift, but relying entirely on verbal memory is risky.

A written or electronic handoff record helps prevent loss of information when:

• the outgoing operator is absent;
• several shifts pass before follow-up;
• multiple employees are involved;
• an investigation occurs later.

Use Standard Handoff Categories

A standardized handoff format can improve consistency.

Useful headings might include:

• process status;
• equipment status;
• laboratory and sampling;
• maintenance;
• chemicals;
• compliance;
• safety;
• pending tasks;
• special instructions.

The goal is not paperwork for its own sake. The format should help operators remember critical information.

Document Critical Communications

Important communications should be documented when appropriate.

Examples include calls to:

• the operator in responsible charge;
• the system owner;
• maintenance personnel;
• laboratories;
• emergency responders;
• DEP;
• contractors.

The record may include the time, person contacted, issue discussed, and instructions received.

Emergency Handoffs

During an emergency, the incoming operator needs a concise description of the current situation.

The handoff should identify:

• what happened;
• current system condition;
• immediate hazards;
• actions already taken;
• notifications already made;
• equipment or processes affected;
• next required action.

Do not bury critical emergency information inside routine comments.

Document Control Supports Compliance

Controlled procedures help demonstrate that the facility has established and communicated consistent methods for important work.

This can support:

• regulatory compliance;
• operator training;
• quality assurance;
• incident investigation;
• maintenance;
• continuity between shifts.

However, having a written procedure is not enough. The procedure must be current, accessible, understood, and actually followed.

Common SOP and Handoff Mistakes

• Using an outdated SOP because an old paper copy remains at the workstation.
• Allowing uncontrolled changes to official procedures.
• Failing to identify the revision or effective date.
• Keeping the only current copy where operators cannot access it.
• Updating the electronic SOP but leaving obsolete paper copies in use.
• Changing equipment without updating the related procedure.
• Failing to train operators after an important revision.
• Assuming the next shift knows about temporary operating conditions.
• Failing to document unfinished work.
• Recording that a setting changed without explaining why.
• Relying entirely on verbal handoff.
• Relying entirely on the written log without discussing a serious abnormal condition.
• Failing to identify equipment operating in manual mode.
• Leaving unresolved alarms for the next shift without explanation.

A Practical Document-Control Routine

1. Assign a clear title or document identifier.
2. Identify the current revision and effective date.
3. Obtain required approval.
4. Publish the approved version where users can access it.
5. Remove or clearly mark obsolete operating copies.
6. Restrict unauthorized changes.
7. Maintain revision history.
8. Train affected staff when significant changes occur.
9. Review procedures after process, equipment, regulatory, or permit changes.
10. Archive superseded versions when required.

A Practical Shift-Handoff Routine

1. Review major events from the outgoing shift.
2. Identify equipment that is unavailable or operating abnormally.
3. Explain important process-control changes and why they were made.
4. Identify temporary configurations.
5. Review recent laboratory and process results.
6. Identify pending samples, maintenance, or compliance tasks.
7. Discuss unresolved alarms or abnormal conditions.
8. Document important communications.
9. Review the operating log together when practical.
10. Allow the incoming operator to ask questions.
11. Perform a plant or system walkthrough when appropriate.
12. Make sure responsibility for unfinished work is clear.

What to Remember for the Exam

• SOPs provide written instructions for performing recurring work consistently.
• Facility-specific SOPs should match actual equipment, processes, responsibilities, and operating conditions.
• Process-control SOPs used under Pennsylvania operator-certification rules require appropriate ORC oversight.
• Current SOPs should be readily accessible to the personnel performing the work.
• Document control helps prevent use of obsolete procedures.
• Controlled documents should identify the current revision or effective date.
• Obsolete operating copies should be removed or clearly marked.
• Electronic procedures should be protected from unauthorized or undetectable alteration.
• Important procedure changes should be reviewed, approved, and communicated to affected staff.
• Shift handoffs transfer operational responsibility and important information between operators.
• Handoffs should identify abnormal conditions, equipment status, process changes, maintenance, sampling, compliance concerns, and unfinished work.
• Temporary operating configurations must be clearly communicated.
• Important process changes should include both the action taken and the reason for the action.
• Serious conditions are often best communicated both verbally and in writing.
• Incoming operators should review records, alarms, process conditions, and equipment status rather than relying only on memory.
• A good handoff makes responsibility for pending work clear.