12 deadlines within 30 days: 5 fire safety courses, 2 health check-ups, 1 extinguisher maintenance area B, 1 risk assessment update.
Workplace safety obligations stay tracked and on time.
OSHA Workflow Compliance tracks workplace health and safety obligations under EU health and safety legislation (EU Framework Directive 89/391/EEC and national transpositions). Mandatory training calendar, occupational health surveillance, collective PPE maintenance, risk assessment updates. Reminders to the safety officer with configurable lead time. Integration with the HRIS and the safety management system is delivered during the project.
OSHA Workflow Compliance at work.
Scheduling the fire safety courses for next week. Notifying the occupational health physician for the check-ups. Maintenance order opened today.
Actions recorded in audit. 7-day reminder set for any obligation not yet closed.
Why it exists.
EU health and safety law imposes detailed obligations: periodic training, occupational health surveillance, collective PPE maintenance, periodic risk assessment updates, periodic safety committee meetings above the threshold headcount. The operational problem is fragmentation: the obligation map per employee, per role, per area is scattered across HRIS, the safety officer's folders, manual sheets. Missed deadlines generate regulatory sanctions and inspection findings.
How it tracks the calendar.
The agent centralises the calendar of all obligations. Per employee: mandatory training with deadlines by course type, occupational health surveillance with periodic check-ups. For the company: collective PPE maintenance deadlines, risk assessment update, periodic safety committee meeting. Reminders to the safety officer with configurable lead time (typically 30 and 7 days). Periodic summary to the employer and the occupational health physician.
Planning stays with the safety officer.
The agent does not replace the safety officer in planning. It sets up the calendar, flags upcoming deadlines, records confirmed completions. Scheduling decisions, documented exceptions, make-up sessions for absent employees stay with the safety officer following the company's procedures.
Who it serves and where it applies.
Safety officer (RSPP or equivalent)
Recovers the time spent manually planning obligations. Receives reminders far enough in advance to organise training sessions, schedule medical check-ups, plan collective PPE maintenance. Focuses on exceptions and non-standard situations — not on calendar work.
Employer
Has aggregated visibility over the company's obligation status. Compliance data is measurable against the regulatory baseline and documentable for inspection. Critical deadlines surface in time for action, not after a sanction.
Occupational health physician and HR officer
The occupational health physician receives a summary of upcoming surveillance deadlines with enough lead time to plan the check-up schedule. The HR officer has the mandatory training calendar per employee integrated with the onboarding and staff development cycle.
A concrete example.
The agent produces the deadline map.
For a mid-size manufacturing company, on the first Monday of each month the agent produces a map of obligations falling due in the following thirty days. The safety officer receives on the configured work channel a structured list: five fire safety training courses due in the month, two occupational health check-ups to schedule, one fire extinguisher maintenance deadline for a production area.
The safety officer plans and confirms in the channel.
For each obligation, the link to the applicable regulatory article and the history of the last completed instances. The safety officer plans the training sessions, notifies the occupational health physician for the check-ups, opens the maintenance order for the fire extinguishers. They confirm the planned actions in the work channel. The agent records the confirmations in the audit registry.
An employee on sick leave: make-up session.
An exception arises in the third month: one of the employees on the fire safety training list is on sick leave. The agent recognises the case from the configured rules (employee absent on the training date), automatically generates a make-up session reminder, and notifies the safety officer. The full event — reminders, confirmations, exceptions — remains in the audit registry for regulatory inspection.
Configuration and technical resources.
The rules are declarative. The safety officer defines, in a readable format, the obligation map by role and company area, deadlines by type, follow-up procedures. The rules live in the customer's repository, versioned, validated at agent startup. When an employee changes role or is added, the HR officer updates the profile in the management system; the agent detects the change and updates the obligation calendar to reflect the new profile.
- Language
- TypeScript (Node.js)
- LLM model
- customer's choice: Anthropic, OpenAI, Mistral, open source models hosted internally, AWS Bedrock for a private model
- Built-in controls used
- pii-detector, topic-guardrail
- Native delivery channels
- Slack, Telegram, HTTP OpenAI-compatible
- HRIS and safety management system integration
- dedicated adapter built during delivery
- Memory
- persistent per instance
- Registry
- append-only, regulatory inspection queryable with a standard SQL client
Frequently asked questions about the agent.
Compliance Reminder HR covers compliance training in the broad sense — privacy, AML, general safety awareness. OSHA Workflow Compliance is the specialisation for the workplace health and safety domain, with the depth of the operational calendar — occupational surveillance per employee, collective PPE by area, risk assessment, periodic safety committee meetings — that the general module does not cover.
The employee-to-obligation mapping rules are declarative. When an employee changes role or is added, the HR officer updates their profile in the management system. The agent detects the change and automatically updates the obligation calendar to reflect the new profile.
The typical pattern is 10-14 weeks. Discovery 2 weeks, obligation map configuration with the safety officer 3-4 weeks, HRIS and safety management system integration 3-5 weeks, hand-off. The effective duration is defined in discovery on the real case.
From a 30-minute conversation to the squad in production.
A 30-45 minute conversation to understand how OSHA Workflow Compliance would configure to the company's case. Which HRIS, how many employees are in scope, which production areas, which obligations are already tracked in a structured way.