Make Safety Something the Business Records, Not Something It Hopes For
Most businesses have a safety rule for every hazard and a record for almost none of them. GullyHR sets up the employee-side processes — induction, training, protective equipment, incident reporting and the review that follows — so that what happened can be shown, and what was learnt actually changes something.
What is workplace health, safety and wellbeing?
Workplace health, safety and wellbeing covers the employee-side processes a business runs around physical risk and employee health: safety induction before work starts, role-specific training, protective equipment issue, incident and near-miss reporting, investigation, corrective action, and the wellbeing provisions that sit alongside them. It is the record as much as the rule.
When businesses ask us for this
- An incident happened, was dealt with sensibly on the day, and there is nothing written down about it six months later.
- New workers start on the floor before anyone has taken them through the hazards, because the induction depends on who is free.
- Protective equipment is issued when someone asks, and nobody can say who currently holds what.
- A near-miss is mentioned in conversation and never recorded, so the same near-miss happens twice more.
- A customer, insurer or auditor asks for your incident records and the answer has to be assembled from memory.
- Safety training happened, but there is no evidence of who attended, what was covered or whether they understood it.
- Corrective actions are agreed after an incident and nobody tracks whether they were actually done.
What the work covers
We start with how your last few incidents were actually handled, end to end, rather than with a policy document. From there we write the procedures that were missing, build the forms and registers, set a training matrix by role, and put a named owner and a date against every step. The output is a system your supervisors can run without you, and a monthly pack that shows whether it is being run.
Safety induction before work starts
A defined induction that happens before a new worker, transferee or contractor's employee begins, covering the hazards of the area they will work in. Recorded, with a signature and a date, because an induction nobody can evidence is an induction that did not happen.
Training matrix by role
Which training each role requires, who has completed it, when it was completed and when it falls due again. This is the single document that turns safety training from an event into a system.
Protective equipment
What each role is issued, against a signature, with replacement rules and a record of who currently holds what. Issue without a record is the commonest gap we find.
Incident and near-miss reporting
One route, one form, one place the record lives. Near-miss reporting matters more than incident reporting: it is the only warning you get for free, and it is the first thing to stop happening when reporting feels punitive.
Investigation and corrective action
A proportionate investigation format, with the corrective actions written down, owned by a named person, and tracked to closure. Untracked corrective actions are why the same incident recurs.
Emergency preparedness
Evacuation routes, assembly points, first aid arrangements, emergency contacts, and a drill schedule with records of who participated.
Employee wellbeing
The provisions that sit alongside physical safety — health checks where they apply, fatigue and shift-load practice, support arrangements for employees under strain, and the route for raising a health concern.
Roles and ownership
Who is responsible for what: the supervisor, the safety officer where there is one, the department head and the management representative. Safety that belongs to everyone belongs to nobody.
Reporting and review
A short monthly pack — incidents, near misses, training completion, open corrective actions — and a review meeting that reads it. The review is what keeps the rest of it alive.
How it runs
Walk the last few incidents
We take the incidents and near misses of the recent past and follow each one: who reported it, to whom, what was recorded, what was decided, and whether the corrective action was done. This finds the gaps faster than reading a policy.
Map hazards to roles
Which roles are exposed to what, and therefore what induction, training and equipment each role requires. This becomes the training matrix.
Write the procedures
Induction, equipment issue, incident reporting, investigation, corrective action and emergency response — written so a supervisor can run them without interpretation.
Build the forms and registers
The induction record, the equipment issue register, the incident and near-miss form, the investigation format and the corrective action tracker.
Name the owners
Every step gets a role against it, with a deputy. Reporting routes are defined end to end, including what happens when the usual recipient is unavailable.
Brief supervisors
A working session on what has changed and what they must now do. Supervisors decide whether reporting happens, so the session concentrates on making reporting safe to do.
Run one month and review
The first month exposes what the design missed. We review it with you, correct it, and hand over the reporting pack.
What you receive
- Written procedures for induction, equipment, reporting, investigation, corrective action and emergency response.
- A training matrix by role with due and renewal dates.
- An induction record and an equipment issue register.
- An incident and near-miss reporting form, and an investigation format.
- A corrective action tracker with owners and dates.
- A responsibility matrix covering every step and its deputy.
- A supervisor briefing pack.
- A monthly safety reporting pack and the review agenda that goes with it.
Who it is for
- Manufacturing, warehousing and logistics businesses with a physical workplace.
- Construction, infrastructure and site-based businesses running multiple locations.
- Hospitals, laboratories and food businesses with hygiene and exposure risk.
- Businesses that have had an incident and found their records would not stand up.
- Companies being asked for safety documentation by a customer, insurer or large client.
- Businesses running contractor labour on site alongside their own employees.
Why GullyHR.
We work on the employee-side process — induction, records, reporting, follow-through — which is where most safety systems fail, and which is the same process discipline we bring to hiring, attendance and exits. We are not safety engineers and not a legal practice: technical risk assessment and statutory obligations belong with your own specialist advisers, and we say so on the page rather than in the small print.
Design the process
Map how the work runs today, then write the procedure, the forms and the approval route it should follow.
Strengthen management
Settle the structure, the roles and the decisions each level can take without the owner.
Develop people
Train the managers who have to run it — the review, the difficult conversation, the handover.
Automate HR
Configure the agreed process in software, so the document and what people actually do stay the same thing.
What changes
- Nobody starts work in an area before being inducted into its hazards.
- You can say who has had which training, and when it falls due again.
- Incidents and near misses are recorded on the day, in one place.
- Corrective actions have an owner and a date, and are tracked to closure.
- Safety documentation can be produced when a customer or insurer asks for it.
- The monthly review discusses a pattern rather than the most recent event.
Who does what
| Activity | GullyHR | Your team |
|---|---|---|
| Reviewing how incidents are handled today | Walks recent incidents end to end and reports where the record, the route or the follow-through broke. | Provides access to what records exist and to the supervisors involved. |
| Mapping hazards to roles | Structures the mapping and builds the training matrix from it. | Supplies the technical hazard information, from its own safety adviser where specialist input is needed. |
| Writing procedures and forms | Drafts them and tests them against how work is actually done. | Reviews and approves, and confirms anything with statutory implications with its own advisers. |
| Briefing supervisors | Runs the session and provides the material. | Requires attendance and makes clear that reporting is expected rather than penalised. |
| Running the system | Supports the first cycle and corrects what the cycle exposes. | Owns it thereafter, including the monthly review. |
Where the software fits
Where GullyHR software is in use, the records that matter most can sit in it rather than in a folder: training completion and renewal dates against the employee record, equipment issued and returned, incident and near-miss entries with an audit trail, and corrective actions as tracked tasks with owners and due dates. The reporting pack then comes out of the system instead of being rebuilt each month.
Ways to engage us
- Review of current practice
- A focused look at how incidents, training and equipment are handled today, closing with a prioritised list of gaps.
- Defined project
- The full sequence — procedures, forms, training matrix, responsibilities, supervisor briefing and the first month's review.
- Records and reporting only
- A narrower engagement for businesses whose procedures are sound but whose records and reporting are not.
- Ongoing advisory
- Periodic review of the reporting pack and support on live incidents, for businesses that want the discipline held to.
Questions we are asked
No. Technical risk assessment, machine and process safety, statutory certification and legal obligations sit with qualified specialists. Our work is the employee-side process around them — induction, training records, reporting, investigation and follow-through.
That depends on your state, sector, premises and headcount, and it changes. We build readiness and ownership so you can answer the question; what applies to you specifically should be confirmed with a qualified professional.
Usually yes, and low reported incidents are sometimes the reason — where reporting is informal, small events simply never get recorded. Near-miss reporting is the useful test of whether a system is working.
They are partly right, which is why the forms are short and each has an owner. The trade is that an incident handled on paper protects the supervisor as much as the business, and most supervisors recognise that once it is explained that way.
By making it clear that reporting is not the start of blame, and by showing that reports lead to something changing. Both are cultural, and both fail quickly if the first few reports are met with a reprimand.
It should, and the induction and equipment steps usually need a contractor variant. Whose obligation is whose in a contracting arrangement is a question for your legal adviser.
Incidents, near misses, training completion against the matrix, open corrective actions and anything overdue. It is deliberately short, because a pack nobody reads stops being produced.
Yes, and it is worth doing precisely because sites drift apart. The procedures and forms are common, with site-level reporting rolled up so you can compare.
We cover the provisions that sit alongside — health checks where they apply, fatigue and shift-load practice, and the route for raising a health concern. Clinical services are not something we provide.
The writing is a few weeks. The part that takes time is the first cycle, because the design is only tested when a real incident goes through it.
Prefer to talk first? +91 80958 58589 · hello@gullyhr.com