india-accident-notice

Generate de-identified statutory accident notifications for Indian establishments with state-specific forms.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Generic AI generates regulator-rejectable safety paperwork for Indian incidents, with incorrect state-specific forms, missing statutory deadlines, leaked personal data, and no compliance guardrails. This Skill produces consultant-grade, regulator-compliant India statutory accident and dangerous-occurrence notifications tailored to the detected state and establishment type, with mandatory de-identification, correct form resolution, and built-in quality checks to avoid non-compliance penalties.

Core Features & Use Cases

  • State-specific form resolution: Automatically detects the Indian state of the incident to pull the correct statutory form and deadline (e.g. Maharashtra Form 24 within 24 hours, Form 24A for dangerous occurrences), flags unverified forms like Tamil Nadu and Delhi accident notices as [GAP] instead of inventing numbers, and never uses a hard-coded national form.
  • Mine/DGMS routing: Separately handles mine incidents by resolving the DGMS region first and routing the notice through the Mines Act/DGMS layer (24-hour notice + Form J register) instead of state factory forms.
  • Mandatory de-identification: Scrubs all personal and health identifiers (names, Aadhaar, employee IDs, addresses, diagnoses) before drafting, aggregates small injury cells (fewer than 5) to prevent back-calculation, and keeps re-identification keys separate from circulated documents.
  • Compliance guardrails: Appends OSH-Code transition notes, defers root-cause analysis to the incident-investigation skill, and requires a domain expert SME review before any output is presented to ensure regulatory accuracy.
  • Use case: HSE managers, safety leaders, and external consultants in India can use this Skill after an incident to quickly assemble the correct, compliant notification for filing with the state inspectorate or DGMS, without risking penalties for incorrect forms or data leaks.

Quick Start

Provide the Indian state where the incident occurred, the establishment type (factory, construction site, or mine), incident severity, date and time of the event, number of affected persons, and statutory notifier role, and the Skill will generate a filled, de-identified statutory accident notice with the correct form, deadline, and follow-up actions assigned to named owners.

Frequently Asked Questions about india-accident-notice

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

FAQPage Schema
How do I draft a statutory accident notification for a factory incident in Maharashtra?

Statutory accident notifications for Indian factories require state-specific forms like Maharashtra Form 24, which must be filed within 24 hours of the incident. You need to provide the incident state, establishment type, severity, date, affected persons count, and statutory notifier role to generate the compliant notice.

What is the process for mine accident notification and DGMS routing in India?

Mine accident notification in India requires routing through the Mines Act and DGMS layer instead of state factory forms. The system resolves the specific DGMS region first, generates the mandatory 24-hour notice, and prepares the Form J register entry for compliance filing.

Does statutory accident notification software require de-identification of personal data?

Yes, mandatory de-identification is required before generating any statutory accident notification output. All personal and health identifiers including names, Aadhaar, employee IDs, addresses, and diagnoses are scrubbed, and injury cells with fewer than five individuals are aggregated to prevent back-calculation.

Can I use AI to generate OSH Code compliant dangerous occurrence notices for Indian states?

Yes, you can generate OSH Code compliant dangerous occurrence notices by providing the incident state and establishment type. The system resolves state-specific forms like Maharashtra Form 24A, appends OSH-Code transition notes, and flags unverified forms for states like Tamil Nadu and Delhi as gaps instead of inventing numbers.

What are the limitations of automated statutory accident notice generation under the Factories Act?

Automated statutory accident notice generation requires domain expert sign-off before any deliverable is presented for filing, defers root-cause analysis to a separate investigation skill, and cannot verify forms for certain states like Tamil Nadu and Delhi, flagging them as gaps instead of guessing.

Do I need a domain expert to review statutory accident notifications before filing with the state inspectorate?

Yes, a domain expert SME review is mandatory before any statutory accident notification output is presented for filing with the state inspectorate or DGMS. This ensures regulatory accuracy and prevents non-compliance penalties from incorrect forms or missing statutory deadlines.