Safety Records — duties, not paperwork
Alberta’s Occupational Health and Safety Act puts real duties on every work site party: employers must ensure the health and safety of their workers, supervisors must protect the workers under their supervision, and workers must take reasonable care and cooperate — and every worker holds the right to refuse work they believe endangers them. The Safety module is where a Constructum operation keeps the record those duties produce: incident or finding, the job and site, who reported it, the action due date, and its state — Open → Investigating → Actions assigned → Closed, with Stop-work issued and Regulator notified as exception states that mean exactly what they say.
Stop-work is a right, and the record backs it
Anyone on site can stop work on a hazard and be backed, not penalised. When that happens it is recorded as Stop-work issued — a state with a date and a reporter, visible in the work summary until it is investigated and closed. An operation that punishes stop-work calls gets silence instead, and silence is how people get hurt. The same applies to reporting generally: a near miss reported is a lesson bought cheaply, and the person who reported it should be thanked in front of the crew.
Investigation and closure discipline
An incident record closes when the investigation is done and the assigned actions are complete — not when the form is filed. Actions carry due dates, and overdue safety actions sit in the same overdue view as overdue tasks and deliveries, because they are at least as urgent. Serious incidents carry notification duties to Alberta OHS; the Regulator notified state exists so that step is explicit in the file rather than assumed. Records are kept honestly: findings are never edited after the fact to read better, because a safety record that cannot be trusted is worse than none — it will be read, one day, by someone whose job is to decide what really happened.
How safety connects to the rest of the job
Safety records name their job and site, so a job file shows its whole safety history beside its schedule, inspections and claims. Patterns become visible: the same hazard on three jobs is a company problem, not three coincidences. That visibility is the point of keeping safety inside the ERP rather than in a binder in the site trailer.
Worked example: on the CHAIN Northgate Yard Expansion, a near miss — a load swing over a pedestrian walkway — was reported by the site superintendent, investigated, carried assigned actions, and closed, with the full sequence on the job’s record.