Standard operating procedures that people actually follow

For finished pharmaceuticals, Section 211.100 requires written production and process-control procedures, including review and approval by the relevant organisational units and the quality control unit. The provision applies that control to changes as well as the initial procedure. An informal adjustment does not become the approved method merely because people repeat it.

The same section addresses execution. Its documentation and deviation requirement says performance is documented when it occurs and deviations from the written procedure are recorded and justified. That connects the instruction with the evidence of the actual work. A procedure should therefore identify the associated record and make the recording points understandable.

Other sectors have their own applicable rules. When developing an SOP, establish the regulatory and technical basis through the company's quality process. A familiar example from another operation can suggest questions, but it cannot settle applicability or become an instruction without review.

Begin with what the procedure controls and when it is used. Explain the scope, relevant roles and prerequisites before the steps. A reader needs to know whether the instruction applies to this activity, this equipment and this stage of the work. Overlapping procedures should have a clear connection so that staff do not need to guess which one takes priority.

Identify the materials, equipment and documents that must be available. Define the relevant status checks before work starts. These details prevent a person from reaching a critical step and discovering that the correct tool or approved record is missing.

Keep background separate from execution. A concise explanation of the reason for a control can improve understanding, but long technical discussions can hide the action. Put the decision where the reader encounters it and refer to supporting material when more detail is needed.

Use a clear action verb and identify what the person acts on. Replace vague instructions such as checking that everything is suitable with the actual checks and accepted conditions. If a result determines the next action, explain the decision and the escalation route. The reader should not need to invent a limit or interpret an undefined term during execution.

Arrange the steps in the sequence the approved task requires. Keep each action close to its associated check and record entry. If a step contains unrelated activities, separate them so that completion can be understood. Cross-references should identify the correct controlled instruction rather than rely on a local nickname.

Plain language does not mean removing precision. Equipment identification, units, operating limits and material descriptions need their exact approved meaning. Explain an unfamiliar term where it first matters, then use it consistently. A shorter sentence helps only if it keeps the requirement intact.

Technical review checks whether the method is correct and whether the controls address the process. A practical review also asks whether a qualified user can follow it with the actual layout, tools and record. A sequence that reads well at a desk may require awkward movement or conflict with the available work space.

Where the company's process permits, walk through the draft with the people who perform and supervise the task. Look for missing prerequisites, unclear acceptance criteria and moments when a person has to choose without enough information. Retain control of the draft so that a review exercise cannot be mistaken for authorisation to use it in production.

Reviewers should resolve disagreements before approval. Avoid leaving contradictory comments to be interpreted later by the operator. The final procedure needs a clear method and a dependable route for abnormal conditions, supported by the appropriate technical evidence.

Document control establishes which procedure is approved, when it applies and how obsolete versions are prevented from being used. The good documentation practice overview includes controls against inadvertent use of superseded documents. That concern applies at the workstation, including printed copies and instructions embedded in other work documents.

A useful system lets a person establish current status without relying on memory. Review the relationship between the SOP, the batch record, equipment instructions and training materials. If only one of those changes, staff may encounter conflicting instructions for the same activity.

Controlled retention of older versions serves a different purpose from making them available for current execution. Historical procedure records may be needed to understand past work. Their status should remain clear so that retained evidence cannot become an unofficial method for a new task.

A revision assessment considers what changed, which roles depend on it and what must happen before implementation. Changes to steps, acceptance criteria, equipment or the response to a deviation can affect qualification. A clear implementation plan connects the approved procedure with training, forms and system settings where relevant.

Choose training that matches the significance of the change. A new practical action may need demonstration and observed performance. A correction to wording may need a different approach under the company's system. Record the decision and rationale so that reviewers can understand why the selected response was suitable.

At implementation, verify that the right instruction is accessible and the associated records are consistent. A person should not finish training on a revision and then receive an earlier work document. See building a GMP training system for managing those connections.

Repeated questions, informal notes and recurring deviations can reveal that a procedure does not fit the work. Investigate those signals rather than assuming that the reader is careless. The problem may be an ambiguous step, missing status information, unrealistic sequence or an unaddressed change in equipment.

A useful SOP remains a living controlled instruction: technically sound, clear enough to follow and linked to evidence of execution. Review it when the process or evidence indicates a need. The CAPA page explains how recurring procedure failures can lead to broader investigation.