Procedure · Writing
The cautious writer's reflex is to add: an edge case, a regulatory reminder, a precaution. By the end, the document covers everything and guides nobody. The GMP guide asks for the opposite: documents that are clear, unambiguous, and written to be followed.
Two readers
An operator who executes, an auditor who verifies. They are not looking for the same thing, they do not read at the same moment, and they do not have the same time. Writing one document for both means failing both.
A procedure swells because it carries content that is not addressed to whoever executes it: the regulatory framing, the justification of choices, the revision history, the vanishingly rare cases. All of that content is legitimate — elsewhere. Leaving it in the body of the text means asking the operator to sort it out themselves, at the workstation, under time pressure.
The belief that costs you
"If it isn't written in the procedure, we are not covered."
That sentence drives documentation bloat, and it rests on a reasoning error. What covers you is that the practice is controlled and demonstrable — not that a sentence exists somewhere. Worse: a procedure your operators cannot fully apply exposes you more than a short one that holds. It creates a permanent gap between what is written and what is done, and that gap is exactly what an auditor looks for.
The method
A procedure is written at the workstation, not at a desk. One hour of observation reveals the real order of operations, the switching points, and the two or three places where the error actually happens. That material should structure the text — not the layout of the standard.
The principle rarely changes; the parameter changes often. Mixed into one document, they force you to reopen the whole text for a single value. Separated, a revision touches only what moves — and the procedure stops ageing badly.
The GMP guide asks for an imperative style. "Care should be taken to ensure that" indicates neither who acts, nor when, nor how you would observe it. "The operator checks X before Y" does. This writing discipline alone removes a large share of interpretation ambiguities.
Have the text executed by someone who did not write it, without helping them. Anything requiring a spoken explanation is an ambiguity to fix. The test costs half an hour and it beats three rounds of review in the approval loop.
Our conviction
A long text consumes attention before it is even applied. And attention is a finite resource: whatever a paragraph of superfluous caution consumes will not be available at the moment of the critical action. Writing short is not a stylistic convenience, it is a risk control decision — and it is argued as such in front of an auditor.
What you leave out
It reassures the writer and does not help the person executing. Its place is in the higher-level document, which links the requirement to the internal arrangement — once, not in every procedure.
Why this threshold, why this interval: valuable, and it belongs in the validation file or the risk analysis. The operator needs the value, not its history.
Handling inline a case that occurs once a year weighs down the reading three hundred times a year. A dedicated procedure, called by a cross-reference, serves both situations better.
Some know-how does not write down usefully. A short video sequence attached to the document grain conveys in thirty seconds what two pages describe badly — and updates just as fast.
None of this content is deleted: it is moved to where it serves. That is the difference between lightening a system and impoverishing it, and it is what an auditor will check if the question arises.
Frequently asked
The gap between the text and the workstation is measured in one day of observation. It often explains most of your deviations.
