Do task-based risk assessments (e.g., JSAs) embed human centred design? For example, prepopulating the known critical controls from higher layers, using plain terminology, and prompting for control effectiveness rather than generic hazard lists so workers aren’t starting from a blank page. 7. Frontline checks: risk assessment or verification? Is the frontline tool (e.g., quick check/last minute tool) explicitly defined as a risk assessment or as a verification activity? If it is a risk assessment, when is a JSA required and how do the two processes interact? If it is verification, does it confirm the presence and functioning of the few controls that prevent fatal and severe harm for the specific task (not just low consequence hazards)? 8. Learning loops & organisational memory When investigations or weak signals indicate control failures or design gaps, how are risk profiles, control standards, and verification routines updated, communicated, and anchored in the system? 9. Assurance that tests effectiveness, not activity Which KPIs and sampling approaches directly test control effectiveness (evidence that controls are present and working) rather than activity counts? Are results reviewed for quality and fed back to supervisors and crews in a way that improves day to day decisions? 10.Decision rights & capability at each level Who holds authority to make or change system design decisions (definitions, tool selection, data architecture), and what competencies are required for frontline workers, supervisors, managers, SSEs, and SMEs to sustain those decisions through role changes? 11.Version control & currency at the point of work How do workers and supervisors know they are viewing the latest control specification for this task and area (e.g., visible version labels, effective date banners, last verified indicators)? What prevents local downloads or shadow copies from becoming the de facto source? When a control standard changes, how is the update propagated into JSAs, permits, and frontline checks so the new requirements are immediately visible? 8. DOCUMENTING VARIATION AND ITS EFFECTS To ground discussion, Table 1 captures common system-design variants and the operational effects most often reported by participants. The intent is not to declare one pattern “right,” but to show how different choices predictably shape frontline experience. Table 1 - Examples of design variants and observed frontline effects 18
RkJQdWJsaXNoZXIy MTM0Mzk2