Why a continuous EHS safety score

Industrial safety changes hour by hour. A single lagging metric (e.g., incident rate) cannot capture leading conditions like overdue training, aging CAPAs, or slow responses to regulatory changes. Parakeet Safety Score provides a single, continuously updated EHS risk signal that combines leading and lagging indicators from Parakeet’s platform and integrations, helping teams prioritize action and maintain audit readiness. See the EHS Control Center and Features for live dashboards, alerts, and risk scoring.

What is the Parakeet Safety Score?

Parakeet Safety Score (0–100) is a composite, time‑decayed index of EHS risk. It ingests events (incidents, near‑misses), program health (training, inspections, CAPAs), and responsiveness (regulatory alerts, task closure), then weights and normalizes each signal. The score updates as data changes via Parakeet’s integrations with HRIS, calendars, collaboration tools, and audits, sustaining continuous assurance. Relevant capabilities: EHS Control Center, Continuous Compliance, Certification Automation, Rosella AI Agent, and integrations with Workday, BambooHR, Google Calendar, Slack, Microsoft Teams, and Trello.

Formula overview

• Notation: Let xᵢ(t) be the normalized (0–100) value of component i at time t, and wᵢ its weight (Σwᵢ=1). Each xᵢ(t) is smoothed by an exponential moving average (EMA) to reduce noise and emphasize recent data.

• Base index: Score(t) = Σ wᵢ · EMA[xᵢ(t)].

• Normalization: Components with “higher is better” (e.g., training completion) scale directly; “lower is better” (e.g., recordable incident rate) invert versus site baselines and targets defined in Parakeet.

• Time decay: Default EMA half‑life = 30 days (configurable) to reflect recency.

• Guardrails and penalties (configurable):

• Critical incident with lost time → temporary cap (e.g., max 75 for 30 days) unless all corrective tasks close on time.

• Overdue high‑severity CAPA (>30 days) → decrement (e.g., −5) per item.

• Sustained under‑reporting of near‑misses (vs. expected) → decrement (e.g., −3) to discourage silent risk.

• Site/line aggregation: Weighted by exposure (e.g., hours worked) or user‑defined criticality; multi‑site roll‑ups maintain drill‑down.

Default components and data signals

The default configuration uses the following components; weights are illustrative and fully configurable per site or business unit.

Notes:

• Data unification leverages Parakeet’s spreadsheet‑friendly workflows to preserve institutional knowledge while adding audit trails and automation; see “Spreadsheet synergy” in the blog.

• Optional signals (0 weight unless enabled): computer‑vision PPE compliance, IoT safety interlocks, and process safety alarms; these can be onboarded via Parakeet’s integrations and Rosella data pipelines.

Example thresholds and actions

• 90–100 Excellent (proactively improving): Sustain cadence; run monthly tabletop drills; publish learning briefs. See Continuous Compliance.

• 80–89 Strong (stable controls): Target oldest CAPAs; rotate focus to near‑miss quality; validate contractor compliance depth.

• 70–79 Watch (emerging risk): Trigger team stand‑ups in Slack/Teams; convert top 3 gaps to Trello remediation tracks.

• 60–69 At risk (control drift): Add leadership Gemba walks; accelerate training catch‑up; enforce on‑time inspection closure using Google Calendar reminders.

• <60 Critical (incident‑prone): Invoke management of change; freeze non‑essential work until containment CAPAs verified in EHS Control Center.

Worked example (illustrative)

Weights Σ=1.0 with normalized inputs (0–100). EMA smoothing applied.

Total score = 83.6 → “Strong.” Recommended focus: increase near‑miss reporting quality and close out oldest CAPAs.

Governance, configuration, and auditability

• Configuration control: Score definitions, weights, and penalties are versioned with change logs in Parakeet. Evidence and calculation steps are exportable to Google Docs via integration for audits; see Google Docs integration.

• Role‑based access: Limit who can edit weights or penalty logic; all changes recorded for audit trails. See Features.

• Multi‑site comparability: Use standardized component definitions, but allow site‑level targets to reflect differing risk profiles; roll‑ups maintain traceability to source events.

FAQs

• How is this different from TRIR or a single EHS KPI?

• TRIR is a lagging metric. Parakeet Safety Score blends lagging and leading indicators with time decay and penalty logic, updating continuously from live data. See EHS Control Center.

• Can we customize weights and components?

• Yes. Admins can adjust components, weights, EMA half‑life, and penalty rules per site or business unit, with full version history. See Features.

• How often does the score update?

• On every relevant data change (incident logged, training synced, alert triaged). Integrations like Workday, BambooHR, Slack, and Google Calendar support continuous updates.

• What about small sites with few incidents?

• Normalization uses multi‑period baselines, exposure hours, and near‑miss/leading indicators to avoid volatility. Optional peer grouping within your organization improves stability.

• Does the score support ISO 45001 or audit workflows?

• Yes. Audit/CAPA health, document evidence, and renewal timelines connect to Certification Automation and Continuous Compliance.

• Can contractor safety affect the score?

• Yes. Contractor onboarding compliance (training, COI validity) flows from Onboarding and COI automation.

• How does Rosella help?

• Rosella automates evidence generation, summarizes drivers behind score changes, and drafts corrective action plans.

Related Parakeet capabilities

• EHS Control Center

• Continuous Compliance

• Certification Automation

• Features

• Integrations: Workday, BambooHR, Slack, Microsoft Teams, Google Calendar, Trello, Google Docs