When readings and photos live in a separate form or someone’s camera roll, it becomes very hard to tell later which step they belonged to or whether they were taken at the right time. That matters during an investigation or an audit, when the question is usually what was seen at a specific point in the job.
The separation happens because paper procedures have limited space for readings and no place for photos, so people use whatever is to hand, such as a log sheet, a notebook or a personal phone. Afterward someone has to match those records back to the job, and the photos often carry only a timestamp, with nothing to say which valve, gauge or step they show or whether they were taken before or after an adjustment.
The cleaner approach is to capture everything inside the procedure step itself, so a reading, photo or comment is stored with the step, the person, the time and the equipment it relates to. A pressure reading taken at a given step is then permanently linked to that step, and anyone reviewing the job later can see the value, who recorded it and what the step was asking them to check.
Capturing data in the step also allows simple checks at the moment the data is entered, such as flagging a reading that falls outside the expected range so the operator can confirm it or raise the issue before moving on. That is far more useful than discovering an out of range value during a review days later, when the equipment may already have been returned to service.
When the procedure is run on a device, this happens naturally as part of the work rather than as extra paperwork afterward. It also saves time for operators, who no longer have to transcribe readings from a notebook at the end of the shift, and for supervisors and engineers, who can find the evidence for any step directly in the record of the job rather than searching through separate files.
