What makes a good SOP?
Hand it to a trained operator on their first day in the suite. If they can do the task the same way you would, and an auditor can later check that they did, it is a good SOP.
That takes three things in every step: a trigger (when), a limit (how much, how long, how often) and an owner (who). Format matters less than people think, and a neat template full of "as needed" still gets cited.
Which words should you avoid when writing an SOP?
These are the words the SOP Checker marks. Most of them are fine in a training slide. In a controlled procedure they hand the decision to whoever is on shift. "Should" and "may" read as optional, so required steps use "must" or "shall".
| Word or phrase | Why it gets flagged |
|---|---|
| as appropriate | Who decides what is appropriate? State the condition. |
| as needed | Define the trigger that makes it needed. |
| as necessary | Define the trigger that makes it necessary. |
| if necessary | Name the condition, or the step is optional. |
| if required | Say what requires it. |
| where applicable | List where it applies. |
| when applicable | List when it applies. |
| if applicable | List when it applies. |
| periodically | Give a frequency: daily, each batch, every 6 months. |
| regularly | Give a frequency. |
| routinely | Give a frequency. |
| frequently | Give a frequency. |
| occasionally | Give a frequency or a trigger. |
| in a timely manner | Give a deadline, such as 30 calendar days. |
| timely | Give a deadline. |
| promptly | Give a deadline. |
| as soon as possible | Give a deadline. |
| adequate | Give the acceptance criterion that makes it adequate. |
| adequately | Give the acceptance criterion. |
| sufficient | Give the number or limit. |
| appropriate | Name the specific method, form or person. |
| properly | Describe the correct way, step by step. |
| suitable | Name the specification that makes it suitable. |
| reasonable | Give the limit. |
| approximately | Give a range with limits, such as 20 to 25 °C. |
| etc. | An open list cannot be followed or audited. List every item. |
| and/or | Say which: both, either, or one of them. |
| should | Use "must" or "shall" for a requirement; "should" reads as optional. |
| may | Optional wording in a GMP step. Use "must" if it is required. |
| could | Optional wording. State what is required. |
| normally | Say what happens in the abnormal case too. |
| usually | Say what happens when it is not usual. |
| typically | State the requirement, not the habit. |
| generally | State the requirement and its exceptions. |
| where possible | Say what to do when it is not possible. |
| if possible | Say what to do when it is not possible. |
| try to | A GMP step is done or not done. Remove "try to". |
| responsible person | Name the role, such as QA Manager. |
| TBD | An approved document cannot contain open items. |
| to be determined | An approved document cannot contain open items. |
What sections does an SOP template need?
Most GMP SOP templates carry these sections, in roughly this order. The checker reports which ones it cannot find in your text.
| SOP section | Check |
|---|---|
| Purpose or objective | Flagged when no heading or label for it is found. |
| Scope | Flagged when no heading or label for it is found. |
| Responsibilities | Flagged when no heading or label for it is found. |
| Definitions or abbreviations | Flagged when no heading or label for it is found. |
| Procedure | Flagged when no heading or label for it is found. |
| References | Flagged when no heading or label for it is found. |
| Records or documentation | Flagged when no heading or label for it is found. |
| Training | Flagged when no heading or label for it is found. |
| Revision or change history | Flagged when no heading or label for it is found. |
| Approval signatures | Flagged when no heading or label for it is found. |
| Effective date | Flagged when no heading or label for it is found. |
How does FDA write up a weak SOP?
Investigators cite procedures that are missing, unclear or not followed. For drugs that is usually 21 CFR 211.100(a) for production and process control or 211.22(d) for the quality unit. In the Atlas Form 483 dataset (774 drug inspections citing Part 211, January 2025 to September 2026), 211.22 shows up at 352 inspections and 211.100 at 224.
Does my document get uploaded?
No. Your browser does all the work. The text you paste and the file you open stay on your computer, the checker reads them in memory, and closing the tab wipes them. Atlas never receives a word of it.
We also switched off session recording and analytics on the tool itself, so nothing you type reaches a tracking script. You can check this yourself: open the network tab in your browser's developer tools, run a check, and watch nothing leave. Your company's rules on where confidential documents can be opened still apply.