Procedures Nobody Reads Are Procedures Nobody Follows
June 5th, 2027
There is a folder on every project that contains the procedures. It is usually well organized. It may even be approved. The only question is whether anyone opens it at the moment the work actually happens.
Too often the answer is no. The crew does the job the way they did it on the last project, the procedure gets signed afterward, and the document becomes a record of what should have happened rather than what did.
That is not a field problem. It is a writing problem.
Procedures Are Written for Two Audiences
Most procedures are written for the reviewer: the client, the auditor, the QA manager, the person who needs to see that the right subjects are covered. That is a real requirement. It is not the only one.
The other audience is the person doing the work at 2 a.m. with a torch, a radio and cold hands. That person needs to know what to do next, what to check, what to do if it is not right and when to stop.
If the document serves the reviewer and not the operator, it will pass review and fail in the field. The best procedures serve both. They are organized so a reviewer can find the requirements and a technician can find the next action.
Start Where the Worker Starts
Many procedures begin with scope, references and definitions. That is logical to the author and useless to the person standing at the panel.
The field document should begin with the first thing the worker needs: the system, the prerequisite, the isolation, the lineup, the permit. Then it should walk through the job in the order it will actually be done.
Put the reference material where it is needed, not all at the front. If a torque value belongs at step seven, put it at step seven. A reader should not have to hold a page number in their head while doing the work.
One Action Per Step
Long paragraphs hide actions. A step that says "verify the system is ready, open the inlet valve, start the pump and monitor pressure" is four steps pretending to be one.
Break it up. Use short sentences. Put the check and the action in separate lines where they belong. Use the same words the site uses, not a different vocabulary that sounds more formal.
Where a value matters, give the value. "Open the valve slowly" is a hope. "Open the valve to 25 percent and confirm pressure is stable" is an instruction.
Say What to Do When It Goes Wrong
Most procedures explain the happy path and stop. Real work includes the moment when the reading is wrong, the pump will not start, the vendor is not on site or the permit has expired.
Add the stop points. Say what is normal, what is not, who to call and what not to do. A procedure that tells a technician to stop and escalate is more useful than one that assumes everything will go to plan.
This is also a safety document. The person reading it may be the only one in the room with the information to recognize that something is wrong. Give them the words to act on it.
Test the Procedure Before You Trust It
A procedure that has never been walked down is a draft with a cover page. Walk it with the people who will use it. Do it on the system, not in a meeting room.
You will find steps out of order, missing tools, wrong tag numbers, unclear hold points and assumptions that stopped being true during construction. Fix them before the work starts, while changing a document is still cheap.
Then check the version. A field procedure that has been superseded is worse than no procedure, because it looks authoritative while describing the wrong job.
Good Procedures Look Boring
Nobody remembers a good procedure. The work goes smoothly, the records are complete and the reviewer finds what they need. That is the point.
The document does not need to be long or impressive. It needs to be true, usable and in the hands of the person doing the work. Everything else is decoration.
At Volantis Group, Inc., we develop commissioning engineering and procedure documentation, from front-end studies and system audits through startup procedures and acceptance criteria. If your procedures need a field check before the next milestone, contact our team.
Posted in: Engineering & Procedure Development