10.07.2015 Views

field level risk assessment - Construction Owners Association of ...

field level risk assessment - Construction Owners Association of ...

field level risk assessment - Construction Owners Association of ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Supervisor’s Guide to Field Level Risk Assessment Part 2: Training OthersTime Objective Content Method Helps15 minutes List the twocomponents <strong>of</strong> FieldLevel RiskAssessment (teamand individual)• State that :• It does not replace other safe work planning.• It adds information about new hazards or “day<strong>of</strong> the job hazards”.• It is done each time something changes.• It involves identifying each step associated withthe job,• It involves identifying the hazards associatedwith each step.• For each hazard, the crew determines howserious the <strong>risk</strong> is.• Then they decide how it will be controlled.Comment: Emphasize this information.• Hand out the “Memory Jogger” cards.State that the process requires periodicallystopping and thinking about what’s going on orwhat’s about to happen. Refer to the five steps <strong>of</strong>the model on the front <strong>of</strong> the card.• State that the team part is done by the wholecrew – together – on the day <strong>of</strong> the job – beforethe job starts.• State that the foreman writes the informationgenerated by the crew on the form and the form isposted where everyone can refer to it.Discuss Elements <strong>of</strong> the Model Overhead#6 Field LevelRiskAssessmentUse the Memory Jogger card to reviewthe Field Level Risk Assessment ProcessMemoryJogger CardPresent the Team Part <strong>of</strong> Model Overhead#7 The TeamPart. Overhead #8Field LevelRiskAssessmentForm<strong>Construction</strong> <strong>Owners</strong> <strong>Association</strong> <strong>of</strong> Alberta 11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!