leading-lagging-kpi-framework

Enforce balanced leading/lagging HSE KPI frameworks aligned to ISO 45001:2018 clause 9.1.

1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill leading-lagging-kpi-framework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: leading-lagging-kpi-framework
Source: https://github.com/ashley-eyekyam/hse-leadership-skills/tree/main/skills/leading-lagging-kpi-framework
Command: npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill leading-lagging-kpi-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Generic AI-generated HSE KPI frameworks are often rejected by regulators: they are limited to lagging outcome metrics, include gameable targets that incentivize under-reporting, lack full definitions for each indicator, and risk leaking personal health or employee data. This Skill eliminates those failures by enforcing balanced leading/lagging indicator sets, full per-indicator definitions, anti-gaming guardrails, and strict de-identification rules, all aligned to ISO 45001:2018 clause 9.1.

Core Features & Use Cases

  • Balanced KPI Design: Enforces a mix of leading (predictive) and lagging (outcome) indicators per ISO 45001:2018 clause 9.1, rejecting lagging-only scorecards that provide a reactive-only view of safety performance.
  • Full Indicator Definition: Requires every metric to include a formula, data source, review frequency, named owner, and stretch-but-credible target, eliminating vague, copy-paste KPIs that lack accountability.
  • Anti-Gaming & Privacy Guardrails: Flags raw incident count targets that incentivize under-reporting, and automatically scrubs personal identifiers and suppresses small-cell metrics (fewer than 5 individuals) to protect privacy and meet de-identification standards.
  • Use Case: A safety manager at a manufacturing site with a TRIR-only scorecard can use this Skill to add leading indicators, define every metric fully, and build a regulator-ready KPI framework in minutes.

Quick Start

Use the leading-lagging-kpi-framework skill to design a balanced set of leading and lagging HSE KPIs for your manufacturing division, aligned to ISO 45001 clause 9.1, with every indicator fully defined and anti-gaming safeguards applied.

Frequently Asked Questions about leading-lagging-kpi-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design HSE KPI frameworks that meet ISO 45001 clause 9.1 requirements?

Designing ISO 45001 HSE KPI frameworks requires balancing leading and lagging safety performance indicators to satisfy clause 9.1. This Skill enforces that balance while mandating full per-indicator definitions including formulas, data sources, review frequencies, owners, and targets to ensure regulatory compliance.

Why do lagging-only safety scorecards fail regulatory review?

Lagging-only safety scorecards fail regulatory review because they provide a purely reactive view of safety performance without predictive leading indicators. This Skill eliminates that failure by enforcing a balanced leading and lagging indicator mix aligned to ISO 45001:2018 clause 9.1, ensuring comprehensive HSE measurement.

How do I prevent under-reporting when setting incident count targets for safety KPIs?

Preventing under-reporting in safety KPIs requires anti-gaming safeguards that flag raw incident count targets incentivizing under-reporting. This Skill automatically applies those guardrails to countable targets, ensuring your HSE metrics drive genuine safety improvement rather than statistical manipulation.

Can I include road safety KPIs for fleet operations in my ISO 45001 framework?

Yes, you can include road safety KPIs for fleet operations using an optional ISO 39001:2012 road-safety indicator branch. This Skill supports building site, function, organization, or fleet-level KPI sets, extending your HSE framework to cover transport-specific safety performance indicators.

How do I de-identify HSE metrics to protect employee privacy in safety reporting?

De-identifying HSE metrics requires scrubbing personal identifiers and suppressing small-cell data representing fewer than five individuals. This Skill automatically applies aggregate de-identification with <5 small-cell suppression to protect personal health and employee data while maintaining meaningful safety performance reporting.

What's the best way to define lagging rate calculations for incident rate KPIs?

Defining lagging rate calculations for incident rate KPIs requires routing computations to a standardized incident_rates engine to prevent fabricated figures. This Skill mandates that approach, ensuring your TRIR and other lagging safety metrics are calculated consistently and accurately for regulatory submissions.