Near misses reported by phone, investigated on record
EHS (environment, health and safety) incidents, near misses and hazards are reported from a phone with type, place and photo; a report is taken to prevent a repeat rather than to blame anyone, and investigation, root cause and actions move on the same record. Accident-free days and rates show on the board, a permit cannot go to approval without its prerequisites, and health data sits in a separate vault open only to the authorised health role.
The EHS incidents module takes incident, near-miss and hazard reports from a phone with type, place and photo. Investigation, root cause and actions move on the same record; accident-free days and rates show on the board. A permit cannot go to approval until its prerequisites are ticked, and health data sits in a separate vault open only to the authorised health role.
Reports are made from a phone with type, place and photo; staff number and PIN are enough
Investigation, root cause and actions move on the same record
Accident-free days and rates show on the board
A permit cannot go to approval until its prerequisites are ticked
Health data is in a separate vault; only the authorised health role opens it
Built for three roles
Who sees what is the company's role setting; the record moves through three screens in the same order. At every step it shows who has it and when it was opened.
Shop-floor employee
Reports from a phone with type, place and photo; staff number and PIN are enough.
Safety specialist and company doctor
Investigates, writes the root cause, assigns actions; health documents are opened only by the authorised health role.
Plant management
Sees accident-free days, open actions and rates on the Gemba and EHS boards.
Setup in four steps
The company builds its own structure: record type, form fields, approval steps and who sees what are your settings.
01
Open the record types
Start from the ready-made types for incidents, near misses and hazard reports or build your own. The report form asks for type, place and photo; the investigator adds the detail.
02
Build the investigation flow
A report lands on the EHS officer; investigation, root cause (5 Whys, fishbone) and action steps are ordered. The evidence required to close an action is a company setting.
03
Separate permissions
Health data is in a separate vault; only the health role authorised by the company opens it, approvers see only "valid / invalid".
04
Connect the board and permits
Accident-free days and rates arrive on the board. A permit request cannot go to approval until the company's prerequisites are ticked.
Inside the module
Incident and near-miss reporting
Reporting from a phone, investigation, root cause and actions; accident-free days and rates on the board.
Work permits
Permit requests that cannot go to approval until the company's prerequisites are ticked, with their own flow.
Inspections, PPE and health
Periodic inspections, PPE issues, health surveillance; health data is protected by a separate permission.
EHS training
Needs analysis, approved plan, attendance and effectiveness forms; reminders for the refresher periods the company sets per hazard class.
Legal dates
KKDİK registration deadlines are reminded by tonnage band; devices within periodic inspection scope are marked in the work-equipment list.
Floor plan
EHS incident, work permit and risk pins on the site floor plan; heat map. Switched on by the company.
Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.