A field-level hazard assessment is a dated, task-specific record of the hazards at one work front today, the controls chosen for them, and the workers who took part. Alberta’s OHS Code is the clearest statement of what it must contain: assess before work begins, prepare a report of the results and the methods used to control the hazards, record the date, and repeat it when the work changes.
Key takeaways
The field-level hazard assessment goes by several names — FLHA, FLRA, tailboard, task hazard analysis — and it fails the same way everywhere. Somebody photocopies yesterday’s, everyone signs it, and it becomes evidence that the crew did not look. A well-run one takes eight minutes and is the most useful safety document on the project.
Alberta states the duty most explicitly. Section 7 of the OHS Code requires an employer to assess a work site and identify existing and potential hazards before work begins at the work site or prior to the construction of a new work site, to prepare a report of the results of the hazard assessment and the methods used to control or eliminate the hazards identified, to ensure the date on which the assessment is prepared or revised is recorded on it, and to repeat the assessment at reasonably practicable intervals to prevent unsafe and unhealthy working conditions, when a new work process is introduced, when a work process or operation changes, and before the construction of significant additions or alterations to a work site.
Section 8 adds the part that turns a form into an assessment: the employer must involve affected workers in the hazard assessment and in the control or elimination of the hazards identified. Section 9 then sets the order of controls — eliminate the hazard if reasonably practicable; otherwise control it through engineering controls; if that is not possible, use administrative controls that reduce it to a level as low as reasonably achievable; if that is not possible, ensure appropriate personal protective equipment is used; and a combination may be used where the combination gives a greater level of worker safety. Section 10 relaxes the reporting requirement only for the period during which emergency action is required.
Other provinces get to the same place by a different route. British Columbia’s OHS Regulation requires regular inspections at intervals that will prevent the development of unsafe working conditions, and a special inspection when required by malfunction or accident. Ontario’s general employer duties include informing a worker about any hazard in the work and taking every precaution reasonable in the circumstances for the protection of a worker. Whichever province you are in, name it in your own procedure — the wording of the duty differs, and so does what an officer will ask to see.
The Canadian Centre for Occupational Health and Safety describes the underlying technique as a job safety analysis: each basic step of the job is broken down to identify potential hazards and recommend the safest way to do the job. CCOHS also warns about scope — an analysis is not suitable for a job defined too broadly, such as “overhauling an engine”, or too narrowly, such as “positioning car jack”.
That warning is the single most useful thing to bring to a field-level assessment. “Install ductwork” produces nothing. “Hang 900 mm rectangular duct from a scissor lift in an occupied corridor while the floor above is being cored” produces a real list, because the hazards come from the combination.
The eight-minute structure
1. The work front and the task, described narrowly. Not the trade, the task.
2. What has changed since yesterday. New crews above you, weather, a delivery in the lay-down area, a permit that expired.
3. Hazards, walked not recalled. One line each.
4. The control for each hazard, in hierarchy order. If every line says “PPE”, the assessment has not been done.
5. Who took part. Names, because participation is a legal requirement, not a formality.
6. The date, on the document. Alberta requires it expressly.
The bottleneck is not knowledge, it is friction at 6:45 in the morning with gloves on. Four things move the needle.
Dictation to structure. A foreman talks through the work front for two minutes; the output is a drafted assessment in your own template, hazard by hazard, with a control field waiting under each. Transcription of spoken input into text is a mature capability — Microsoft documents real-time and batch speech-to-text with support for multiple languages. The value is not the typing saved; it is that a spoken assessment describes what the person actually saw, whereas a written one describes what fits in the boxes.
Recall of the last one. Pulling forward the assessment for the same task at the same location gives the crew something to argue with. Arguing with a draft produces better hazards than staring at a blank form — provided the draft is presented as last week’s and not as today’s.
Completeness checks. A control line missing against an identified hazard; a hazard controlled by PPE alone where an engineering control was used last month; an assessment with no date; an assessment for a task nobody was signed on to. These are structural checks, and they are exactly what a reviewer notices in an audit.
Cross-referencing. Chemical hazards on the assessment should reconcile against the products actually on site and their safety data sheets; hazards that keep recurring should feed the near-miss and inspection record rather than sitting in a drawer.
A model has never been to your site. It can propose the hazards that usually accompany a task, which is genuinely useful as a prompt and genuinely dangerous as an output, because a generated list reads exactly as confident when it is wrong. It cannot see the loose guardrail, the second crew that arrived overnight, or the fact that the lift is on a floor that has not been backfilled.
The regulation also puts people in the loop for a reason. Alberta requires affected workers to be involved in the assessment and in the control decision. An assessment produced by software and signed by a supervisor does not meet that, however good the text is. The sequence that works is: crew walks and talks, tool drafts, crew corrects, competent person signs.
The following is illustrative — a composite of how the workflow is usually assembled, not a measured result.
A civil crew is saw-cutting and removing a slab section inside a live plant. The foreman dictates: work front, three tasks, silica dust, noise, buried services, an overhead conveyor, and a forklift route that crosses the exclusion zone. The draft comes back with those six hazards and empty control fields.
The crew fills them in order: the forklift route is re-routed for the shift, which is elimination; wet cutting and local exhaust handle the dust as engineering controls; the conveyor is isolated; hearing protection and respirators are the last line, not the first. The system flags that the previous assessment for this task controlled dust with respirators alone, and asks whether that was intentional. Somebody has to answer — and the answer, recorded, is worth more than the form.
No. A safe work procedure is written in advance for a repeated task and lives in your programme. A field-level assessment applies it to today’s conditions and records what is different. If your assessments read identically to your procedures, the assessment step is not happening.
Alberta requires it at reasonably practicable intervals to prevent unsafe conditions, when a new work process is introduced, when a work process or operation changes, and before significant additions or alterations. On a construction site that generally means daily per work front, and again whenever the surrounding work changes — which is the trigger crews most often ignore.
Nothing in the requirement compels paper, and an electronic record is easier to date, retain and produce. What matters is that the signature reflects participation rather than attendance. A screen passed round the truck at the end has the same evidentiary weight as a photocopy: it proves the form existed, and nothing else. These records are also the backbone of a COR audit.
A 30-minute call is enough to tell you whether AI pays for itself here.
