Safety
EHS software for factories: what it should do, and what to skip
Good EHS software for a factory does four things well. It lets anyone report a hazard or near miss in under a minute, it drives every corrective action to a verified close, it controls high-risk work through permits and lockout, and it calculates LTIFR and TRIR from the hours people actually worked. Skip features that add forms without closing actions, and test any tool on your own shop floor before you buy it.
What EHS software should do in a factory
EHS stands for environment, health and safety. In most Indian plants, EHS lives in a mix of paper permit books, an Excel incident register, a WhatsApp group for near misses and a folder of licences that someone checks before the audit. None of this is wrong on its own. The problem is that nothing connects. A near miss is reported, discussed and forgotten. A permit is signed, but nobody can find it three weeks later.
Software should fix the connections, not add more forms. Judge any tool against five jobs:
- Capture. A worker on the floor can report a hazard, near miss or unsafe act quickly, with a photo and the location, without filling in twenty fields.
- Act. Every report and every incident produces actions with an owner and a due date. Someone other than the owner checks that the action worked.
- Control high-risk work. Hot work, work at height, confined space and electrical work start with a permit and end with a proper handback. Isolations are locked, and the lock is tracked.
- Keep people, materials and licences in date. Training, PPE issue, chemical approvals, fire equipment checks and statutory licences all have expiry dates. The software should warn you before they lapse.
- Report honestly. LTIFR, TRIR and open action counts come straight from the records, not from a separate monthly spreadsheet.
If a tool does these five well, it is useful. If it does twenty other things but makes reporting slow, your people will go back to WhatsApp.
A buyer's checklist you can copy
Take this into every demo. Ask the vendor to show each item on screen, using a scenario from your plant, not their sample data.
| Need | Ask them to show you | Red flag |
|---|---|---|
| Fast reporting | A near miss reported from a phone, with a photo, in under a minute | Long forms, or only supervisors can report |
| Investigation | An incident with witnesses, a cause analysis and linked actions | Root cause is a free text box with no structure |
| Action closure | A corrective action closed by one person and verified by another | The owner can close and verify their own action |
| Permits to work | A hot work permit with gas test, named crew and a handback step | A permit is just a PDF upload |
| Lockout tagout | An isolation that cannot be released while a personal lock is on | Locks are a checkbox |
| Risk assessment | A HIRA where the score and band are calculated, with controls listed | Scores are typed in by hand |
| Man-hours and rates | LTIFR and TRIR worked out from logged hours, including contractors | Rates are typed in each month |
| Expiry tracking | Training, licences and fire equipment due in the next 30 days | No reminders, only a report you must run |
| Audit trail | Who changed a record, when, and what it said before | Records can be edited with no history |
| Link to maintenance | An incident on a machine, next to that machine's work orders | Safety and maintenance in separate systems |
Score each line 0, 1 or 2. Anything scoring 0 on reporting, action closure or permits should end the evaluation, whatever the rest looks like.
What to skip, or leave for later
Most plants buy more EHS software than they use. These are the features that look good in a demo and rarely change what happens on the floor in the first year.
- Large dashboard libraries. You need five numbers: open actions, overdue actions, near misses reported, LTIFR and TRIR. Forty charts nobody reads do not make the plant safer.
- Behaviour scoring of individual workers. It tends to stop people reporting. Count observations by area and type instead.
- Custom form builders you will not maintain. Every new form is another thing to train and audit. Start with standard registers and add forms only when a real gap shows up.
- Predictions you cannot check. If a vendor cannot show you which records a forecast came from, treat it as decoration.
- Modules for a certification you are not pursuing yet. If you are not working towards ISO 45001 or ISO 14001 this year, do not pay for the full management system pack. Make sure the core records will support it later.
Leaving something out is not the same as never having it. Ask the vendor whether you can switch a module on later without migrating data.
Worked example: a forging plant in Rajkot
Worked example (illustrative)
Take a closed die forging plant near Rajkot with 300 permanent employees and about 120 contract workers across two shifts. The EHS officer keeps an Excel injury register and works out rates each month. All numbers below are illustrative.
Last year the plant recorded 2 lost time injuries and 5 recordable injuries in total. Two of the recordables were contract workers. The spreadsheet counted hours only for permanent staff, because those came from payroll: 300 people, 8 hours a day, 300 working days, which is 7,20,000 hours. Contract workers' hours sat with the labour contractor and never reached the register.
| Basis | Hours worked | LTIFR (per 1,000,000 hours) | TRIR (per 200,000 hours) |
|---|---|---|---|
| Permanent staff hours only | 7,20,000 | 2.78 | 1.39 |
| All workers, including contract | 10,08,000 | 1.98 | 0.99 |
What the example shows (illustrative). Injuries to contract workers were counted, but their hours were not, so both rates were overstated by about 40%. The fix is not a better formula. It is logging man-hours for everyone on site, every month, in the same system as the injuries. Then LTIFR is 2 × 1,000,000 ÷ 10,08,000 and TRIR is 5 × 200,000 ÷ 10,08,000, worked out from records anyone can check. Try your own numbers in the LTIFR and TRIR calculator.
Run a two-week trial before you sign
Pick one line or one bay, not the whole plant. Load its machines, its people and its open actions. Then ask operators to report real hazards for two weeks. Count how many reports come in compared with the paper or WhatsApp channel before.
Raise at least one real hot work permit and one lockout through the software, with the actual crew. Close two corrective actions and have a second person verify them. At the end, ask the EHS officer to produce last month's LTIFR from the system and compare it with the spreadsheet.
If operators stop reporting after day three, the tool is too slow. That single signal matters more than any feature list. For permits and isolations, the permit to work guide and the lockout tagout procedure show what a good flow looks like.
Common mistakes
- Buying for the auditor, not the operator. If reporting is hard, the registers stay empty, and an empty register proves nothing.
- Letting owners verify their own actions. A second person checking effectiveness is what turns an action into a real fix.
- Leaving contractors out. Contract workers often do the highest risk jobs. Their hours, permits and training belong in the same records.
- Keeping safety and maintenance apart. Many incidents happen during maintenance or because of a machine fault. When the incident and the work order sit in different systems, the link is lost. See incident investigation for how the two connect.
- Treating the HIRA as a one-time document. Review it after every incident and every change to a process or machine. The HIRA guide walks through it.
- Migrating ten years of old records first. Start clean with open actions, live permits and current licences. Archive the rest and bring it in later if you need it.
Sources
- Guidelines on occupational safety and health management systems (ILO-OSH 2001) (opens in a new tab), International Labour Organization
- ISO 45001 (opens in a new tab), Wikipedia
- Hierarchy of controls (opens in a new tab), NIOSH, CDC
- Injuries, Illnesses, and Fatalities (opens in a new tab), U.S. Bureau of Labor Statistics
- Directorate General, Occupational Safety and Health (opens in a new tab), Ministry of Labour and Employment, Government of India
Frequently asked questions
What is EHS software?
EHS software is a system for managing environment, health and safety work in a plant: hazard and near miss reports, incidents, corrective actions, permits to work, risk assessments, training, chemicals and safety reporting such as LTIFR and TRIR.
What features should EHS software have for a factory?
Fast hazard and near miss reporting, incident investigation, corrective actions with a separate verifier, permits to work, lockout tagout, risk assessment, expiry tracking for training and licences, an audit trail and rates calculated from logged man-hours.
Does EHS software make us ISO 45001 certified?
No. Software keeps the records and evidence an auditor asks for. Certification comes from an accredited certification body after it audits your management system.
Why are our LTIFR and TRIR numbers wrong?
The most common reason is incomplete man-hours. If injuries to contract workers are counted but their hours are not, both rates are overstated. Log hours for everyone on site.
Should EHS and maintenance software be the same system?
It helps. Many incidents involve a machine or happen during maintenance work. Keeping both on the same asset record makes investigation faster and stops lessons from getting lost between departments.