Back to Blog
Blog

How do you split multi action procedure steps into usable field instructions?

How do you split multi action procedure steps into usable field instructions?

A lot of legacy procedures pack three or four actions into a single step, something like close the inlet valve, open the bypass, confirm pressure and…

A lot of legacy procedures pack three or four actions into a single step, something like close the inlet valve, open the bypass, confirm pressure and notify the control room. On paper that works because an experienced operator reads it as a sequence, but in a digital workflow it means one checkbox covers four actions and you have no record of which ones actually happened.

The gap shows up most clearly after something goes wrong, when an investigation asks whether the bypass was opened before the pressure was confirmed and the record only shows a single tick against the whole step. It also causes problems during the job itself, since an operator interrupted halfway through a combined step by a radio call or a shift change has no way to mark which parts are done, and the next person has to guess or start again.

Splitting it so each step holds one action with its own check makes the procedure easier to follow and gives you a real record of what was done. The split steps keep their original order, and any warning or caution that applied to the combined step stays attached to the specific action it relates to, so a caution about pressure sits on the confirmation step rather than at the top of a block of text. Where an action needs a reading, such as the confirmed pressure, the step can ask for the value itself instead of a simple tick.

Some care is needed with steps that genuinely belong together, like two valves that must be operated at the same time, where splitting them could suggest they can be done one after the other. Reviewers should look for those cases and keep the actions together or add a note that makes the timing clear, since the aim is a procedure that matches how the work is really done rather than one with the highest possible number of steps.

Interface does this breakdown automatically when a procedure comes in, and your team reviews the split steps before they go into the approved version. That review is a matter of checking each proposed split against the original wording, which is a much lighter task than rewriting every step from scratch.