What a Useful Field Level Hazard Assessment Actually Does

A field level hazard assessment should make the worker stop for a minute and look at the job in front of them. What is different today? What can hurt someone? What control is actually needed before the work starts?

The same task can change depending on traffic, weather, equipment condition, access, nearby work, customer activity, staffing or a change in scope. The FLHA is where the normal procedure gets tested against the conditions that actually exist that day.

The form matters because it records the assessment. The real value is the decision that came before the form was submitted.

Alberta OHS legislation requires employers to assess worksite hazards, involve affected workers, apply controls, and repeat the assessment when work processes or operations change and at reasonably practicable intervals. The legislation does not prescribe one universal form called an FLHA. An FLHA is one practical method an employer, client, industry, or Certifying Partner may use as part of meeting broader hazard-assessment expectations.

I like completion data. If an FLHA is required each shift or before certain work, the organization should know whether people are doing it. A low completion rate tells you the process is not being followed.

But 100 percent completion can still hide weak assessments. If every form says slips, trips, weather, PPE and driving, you may have excellent compliance with a poor process.

The better question is whether the assessment reflects the actual task and whether the controls make sense.

Writing traffic tells me very little. Writing that the unit has to reverse into a tight customer site beside moving public traffic gives me something useful.

Writing weather is broad. Writing freezing rain at the rear work area with poor footing is specific enough to drive a control.

That level of detail does not require a long essay. It just needs to show that the worker looked at the real job rather than selecting the same list they use every day.

An FLHA has very little value if the worker can identify a problem but cannot do anything about it.

If the assessment shows that the job needs traffic control, another worker, different equipment, a shutdown or a supervisor decision, there needs to be a clear way to stop and get that support.

Supervisors matter here. If a worker raises a legitimate concern and gets treated like they are slowing the job down, the organization has just taught them that completing the form matters more than using it.

If the only question a supervisor asks is whether the FLHA was submitted, workers will focus on submitting it. That is predictable.

Quality improves when supervisors occasionally read the content, challenge weak controls, ask why something was identified and recognize a good assessment when they see one.

You do not need a supervisor reading every line of every form. A reasonable sample and some field conversation will tell you a lot.

A large volume of FLHAs can show patterns before those patterns turn into incidents. Repeated access problems, traffic exposure, equipment defects or customer site issues are useful information.

If the organization stores every FLHA for audit evidence and never looks at the trends, it is leaving value on the table.

Digital tools can make this easier because completion, quality and recurring hazards can be reviewed faster. The software is only useful if somebody is actually looking at the information and acting on it.

Ask whether anything on the assessment could reasonably change the job. Could it change where the truck is parked, how traffic is controlled, what equipment is used, whether another worker is needed or whether the job should stop until something is fixed?

If yes, the process has value.

If nothing written on the form could ever change how the work is done, then the FLHA has probably become an administrative exercise. That is the point where the organization should look at the process again.