PTQ Q3 2026 Issue

incomplete coverage (42.7%) as a root cause category indi- cates that the most frequent procedural failure mode stems from gaps in written guidance for conditions operators routinely encounter, rather than from non-compliance with existing guidance. Without feedback channels between field execution and procedure authoring, this gap com - pounds over time and remains invisible to management until a failure event reveals it. Digital procedure management: Industrial deployments Platform architecture and functional scope Digital procedure management platforms address the structural limitations of document-based approaches through an integrated set of capabilities: centralised authoring with version control ensuring a single approved revision is always in circulation; access to a library of stand- ardised procedural instructions; digital field execution via mobile devices with step-level tracking and timestamped completion logging; deviation and exception recording; and closed-loop feedback channels that route operator obser- vations directly into authoring and review workflows. Integration with enterprise systems, including enterprise resource planning (ERP) platforms, business intelligence tools, digital twin environments, control of work systems, and shift-handover applications, extends the operational value of execution data beyond procedure management into broader continuous improvement programmes. This integration positions the procedure management system as a data-generating infrastructure asset rather than a docu- ment repository. Large-scale deployment: Major global energy operator A major global energy operator deployed a digital procedure management platform across downstream, gas, liquefied natural gas (LNG), offshore, and new-build operations over a five-year period. The deployment was initiated in direct response to industry safety incidents in which procedural deficiencies had been identified as contributing factors. The organisation sought a unified system for procedure author - ing, publishing, execution, and continuous improvement, with full lifecycle auditability. Initial implementation covered downstream facilities, with procedure volumes in the low thousands. Subsequent expansion incorporated gas, LNG, offshore, shipping, and new-build operations. Total procedure volumes grew to tens of thousands; annual digital completions grew pro- portionally, reflecting substantive integration into daily operations. Early implementation fragmentation, characterised by site-specific workflows, naming conventions, permission structures, and document hierarchies, was addressed through a global standardisation programme that replaced hundreds of locally defined roles with a common role set and consolidated many workflow variants into a small num - ber of shared, governed processes. This standardisation reduced new site onboarding complexity and established consistent governance conditions across the enterprise. The digital execution environment also introduced a qual- itative change to operational governance. Critical steps can

be flagged, preventing progression without confirmed com - pletion. Deviations are recorded automatically, generating an audit trail that paper-based systems cannot produce. Supervisors gained real-time visibility into execution pro- gress across concurrent field operations. For the first time, the organisation could produce systematic documentary evidence of procedural adherence. This capability is directly aligned with API RP 754 and API 770 requirements.⁸ Crossbridge Energy’s implementation at the Fredericia Refinery provides a documented case at mid-scale. Since the start of the project in November 2022, full integration into daily workflows was achieved within approximately one year. Under the paper-based model, operators communi- cated each completed action to the control room by radio, generating a continuous traffic of routine confirmations. Following digital implementation, step completion was logged automatically and visible to supervisors in real time. As Richard Aasholm, Production Specialist for Ensure Safe Production at Crossbridge, described: “They had to call in every time to check: ‘I’m closing valve number six now.’ ‘OK, have you closed it?’ ‘Yes, I did.’ Now, ‘Closed valve num- ber six’ is indicated in the system, and they can move on. It makes the control room much more silent.” The API audit outcome is significant in the context of reg - ulatory compliance. Crossbridge’s first American Petroleum Institute (API) audit under its new ownership identified procedural gaps; the digital platform was used to address and close these gaps, and the implementation was subse- quently designated by auditors as an exemplary practice. This designation reflects both the quality of the docu - mented procedures and the integrity of the management system governing them. Alignment with process safety standards This outcome illustrates, in practical terms, the expecta- tions embedded in process safety guidance. API RP 754 establishes process safety performance indicators for the refining and petrochemical industries, treating procedure quality and adherence as leading indi- cators of safety outcomes, because they can be measured in day-to-day operations and reveal whether work is being carried out as intended before deviations escalate into near-misses or incidents. API 770 addresses the reduc- tion of human error in process plant operations, identifying robust procedure management as a foundational control. Both standards require that organisations demonstrate through documented evidence that procedures are current, complete and consistently followed. This emphasis is consistent with UK HSE guidance. HSG48 highlights that failures to follow or implement pro- cedures are frequently linked to human factors, such as gaps in training, communication, and understanding, while also stressing that procedures must be clear, concise, and usable if they are to be followed reliably. HSG250 similarly notes that deviations often originate in the practical appli- cation of procedures, rather than their formal existence. Digital execution environments generate the eviden- tiary infrastructure these standards require. Timestamped

PTQ Q3 2026