Not a form the law names, and that is not a reason to skip it
No province names a field level hazard assessment, or a field level risk assessment, as a specific legal requirement. Not even Alberta, where the practice began. Its own Occupational Health and Safety Code sets out the general duty to assess hazards before work starts, and its own published handbook on hazard assessment describes that duty without ever using the words "field level" anywhere. What every Canadian jurisdiction asks for is the same general duty this site's full hazard assessment tool already states correctly: identify hazards before the work starts, control them, involve the people doing the work, and put a date on the record. This card satisfies that duty at task level rather than project level. It is not a certificate, and filling it in does not discharge anybody's legal duty by itself.
Where this came from
Field level risk assessment first appeared on Alberta industrial sites in the late 1990s, and the Construction Owners Association of Alberta wrote its best practice for it in 1998, at the request of its own Safety Committee, to encourage all workers to identify, assess and control risks that have the potential to cause loss to people, property or the environment. The technique spread from there across Western Canadian construction and energy work until it became the standard shift-start check it is today, filled in by a crew before the first task of the day or whenever the job changes underneath them. COAA's own best practice has since been archived, its job done: the point of a best practice document is to make itself unnecessary once the habit sticks on its own.
How this differs from the full hazard assessment
The hazard assessment builder on this site is a project record. It names a province, cites the instrument that applies there where one has been read directly, and covers the whole scope of work before it starts. This card is smaller on purpose. There is no province to pick, because no province cites this specific card by name, so there is nothing for a picker to switch between. There is no employer field and no separately named assessor, because a task level card belongs to the crew doing the task, right now, rather than to a company. Use both: the project record before the job starts, and this card at the start of each task or shift inside it.
Five things worth a quick look
The five quick-pick buttons on the form are not a checklist any regulator prescribes. They follow how a Canadian territorial safety regulator frames a field level check in its own published toolbox talk: the people doing the work, the equipment, the materials, the environment, and whether the procedure still matches what is in front of the crew today. Any one of those changing since the last card was filled in is the usual reason to fill in another one before carrying on.
A hazard with no control is not a finished card
The one thing this tool enforces is the trap a fast form makes easy to fall into. Writing down that grinding near a stair opening is dangerous, and stopping there, reads like a safety record. It is not one. The card refuses to call itself ready until every hazard named on it has something written against it about what is being done, however short that answer is.
It carries your branding, not ours
The card is built in your own browser and saved to your own machine, carrying whatever company details you have set up on this site rather than anybody else's branding. No account, no email address, and no copy of it sitting on a server you do not control.
Common questions
Is an FLHA card a legal requirement in Canada?
No. No province names this specific card, or one like it, as a requirement, not even Alberta where the practice began. What is required everywhere is the general duty behind it: hazards identified before work starts, controlled, with the people doing the work involved and the record dated. This card is one honest way of meeting that duty at task level.
What is the difference between an FLHA and an FLRA?
None that matters. Field level hazard assessment and field level risk assessment describe the same practice, and both terms are in genuine use across Canada. This tool treats them as interchangeable because the industry does.
How is this different from the hazard assessment builder on this site?
That one is a project record: it names a province, cites the instrument that applies there where one has been read directly, and covers a whole scope of work before it starts. This card covers one task or one shift, is filled in by the crew doing it, and has no province picker at all, because no province cites this specific card by name. Fill in the project record once, and this card at the start of each task inside it.
Who is supposed to fill this in?
The people doing the task, ideally with whoever is supervising it. Published Canadian practice describes it as something a supervisor and the crew do together in the minutes before work starts, not a form filled in afterwards by somebody who was not there.
What happens if I list a hazard but do not say what is being done about it?
The card will not call itself ready. A hazard with nothing written against it is not a finished thought, and this tool treats that as the one thing worth stopping on.
Where did the FLHA come from?
Alberta heavy industry, in the late 1990s. The Construction Owners Association of Alberta wrote its own best practice for it in 1998, and the approach spread from there across Western Canadian construction and energy work until it became the shift-start habit it is today.
Does this replace a job hazard analysis or job safety analysis?
Not necessarily. A job hazard analysis or job safety analysis is often written in advance for a type of task and reused each time it recurs. This card is filled in on the day, against whatever the site looks like at that moment, which is the same distinction Canadian practice draws between a formal hazard assessment and a field level one.
Is the completed card held anywhere?
No. The card is built in your browser and saved to your own machine, with your own details on it rather than ours. No account, no email address, and no copy kept on a server you do not control.