The mechanical integrity element of OSHA's Process Safety Management standard reads like an engineering requirement. In enforcement practice it behaves like a documentation requirement. When a compliance officer works through 29 CFR 1910.119(j), the questions are rarely about whether a vessel was inspected. They are about whether the site can produce the procedure, the schedule, the result, and the deficiency resolution, on paper, in order.
What the element actually asks for
Mechanical integrity under PSM covers a defined equipment population: pressure vessels and storage tanks, piping systems, relief and vent systems, emergency shutdown systems, controls, and pumps. For that population the standard expects a working system, not a binder that exists for audit day:
- Written procedures. How each inspection and test is performed, maintained as controlled documents, not tribal knowledge.
- Trained personnel. Evidence that the people doing the work were trained on the procedures and on the process hazards, with records of that training.
- Inspections and tests on a schedule. Frequency consistent with manufacturer recommendations, good engineering practice, and prior operating experience. Recognized and generally accepted good engineering practice, RAGAGEP, is the phrase auditors reach for, and API and NFPA documents are usually the reference point.
- Documentation of each inspection and test. Date, inspector, equipment identity, description of what was done, and the result.
- Deficiency correction. Equipment operating outside acceptable limits gets corrected before further use, or in a safe and timely manner with interim measures. The correction itself must be traceable.
Where the paper trail breaks
Most sites do the work. The trail breaks in predictable places.
The first break is between the schedule and the record. A CMMS says the inspection was completed; the actual result lives in a contractor PDF that never made it back to the equipment file. The work order closes, the evidence does not attach.
The second break is the deficiency loop. An inspection report notes thinning near a nozzle, a recommendation is written, and then the recommendation ages in an email thread. Under PSM, an identified deficiency without a documented resolution is often a worse audit position than never having found it, because it proves the system saw the problem and lost it.
The third break is inspector identity. The record shows a result but not who produced it, or the person's training record cannot be matched to the date of the work. The finding writes itself.
Building a trail that survives
A defensible mechanical integrity file answers four questions per equipment item without a search party:
- What procedure governed the last inspection, and which revision.
- Who performed it, and what their training record showed on that date.
- What was found, with the raw evidence, readings, photos, and sign-off attached.
- What happened to every deficiency, closed with a date, or open with an interim safeguard documented.
The common thread is that the record has to assemble when the work happens, not weeks later from memory and inbox archaeology. Reconstruction is where trails fail.
intelliSPEC was built around that idea: the procedure, the result, the evidence, and the deficiency all land on the same equipment record at capture time. If you are preparing for a PSM audit, bring one equipment file to a demo and see how the trail holds together.
