TRA (Task Risk Assessment)

TRA is a site-specific pre-work risk check that validates controls against real conditions on the day of execution.

How TRA works in practice

A practical sequence teams can run quickly before starting work.

Confirm scope for today

Define the exact task scope, interfaces, and constraints for this shift.

Review baseline controls

Reference RAMS/JSA and identify which controls must be present before work starts.

Assess live conditions

Check weather, access, utilities, concurrent works, and any environmental changes.

Re-rate risk and adjust

Update risk for current conditions and strengthen controls where assumptions no longer hold.

Brief team and assign roles

Walk through hazards, controls, responsibilities, and stop-work triggers.

Authorize go or no-go

Proceed only when controls are verified; otherwise pause, escalate, and re-plan.

Where TRA has the most impact

These are the areas where mature teams typically see measurable gains.

For HSSE Teams

TRA closes the gap between planning documents and field reality, reducing incidents caused by changed site conditions.

For IT & CIOs

Digital TRA records improve auditability, link actions to ownership, and surface recurring hazards across projects.

Deep Dive

TRA explained for operations, HSSE, and leadership teams

A practical reference for day-of-work risk control and execution discipline.

What TRA covers

A Task Risk Assessment (TRA) confirms whether planned controls are still valid under actual conditions immediately before work begins.

It is the operational bridge between static planning (RAMS/JSA) and safe execution on site.

Where teams get value

Detects changed conditions before they become incidents.
Forces explicit go/no-go decisions with accountable sign-off.
Improves quality of toolbox talks and role clarity at task start.

Common failure modes

Treating TRA as a paperwork exercise rather than a field decision tool.
Reusing yesterday's assumptions without re-checking current hazards.
Starting work with unresolved control gaps or unclear ownership.

Operating principle

If conditions differ from plan, controls must be adapted before work proceeds. If they cannot be adapted safely, work does not start.

Template

Example TRA record

Structured TRA entries improve consistency, communication, and audit readiness.

Roof-level railing task example

Item	Detail
Task	Erection of external roof-level safety railings at 8 m height.
Hazards	Falls from height, dropped objects, wind exposure, manual handling.
Controls	Certified fall-arrest harnesses, secured platform, wind-speed trigger, spotter, two-person minimum, toolbelts.
Sequence	Inspect harness/platform, secure anchor point, load tools, execute work, clear area, inspect/store equipment.
Personnel	Supervisor and operatives assigned with verified competency; spotter designated.
Emergency	Stop work, raise alarm, notify office, follow emergency route and first-aid protocol.
Supervisor approval	Named supervisor sign-off with date/time before commencement.

Frequently asked questions

A typical TRA takes 15-30 minutes depending on task complexity. Simple tasks (routine, low-hazard) may be assessed in 15 minutes. Complex tasks (multiple hazards, high-risk, multiple personnel) may take 30-45 minutes. TRA should not be so time-consuming that supervisors skip it on busy days; if TRA is taking too long, consider whether a formal JSA exists that can be referenced (reducing TRA to confirming the JSA against current conditions).

Continue your glossary path

Explore connected concepts often applied alongside this term.

Read term

Toolbox Talk

Explore this related glossary concept.

Explore ->

Read term

RAMS (Risk Assessment and Method Statement)

Explore this related glossary concept.

Explore ->

Read term

CDM Regulations (Construction Design and Management Regulations 2015)

Explore this related glossary concept.

Explore ->

Operationalize TRA at workforce scale

Dockt helps teams move from manual credential tracking to proactive, audit-ready competence management.