UProcess

ModulesSafety TalksReport & Learn

Lessons the crew actually hears.Every talk with the lesson it came from.

For supervisors who give the talk and EHS teams who write it: start it from an investigation, an external lesson or the library, edit it, and publish it for your sites.

Published. The talk itself, with the lesson it came from.

TK-0057 · Hand-tight is not tight
Based on INV-2026-014 · Hose coupling came apart during tanker unloading
Published
Status
Published
Key message
Pin every cam-lock coupling, and have it checked before the pump starts.
Context
On 21 Oct at Harbour site, a hose coupling came apart during tanker unloading. About 40 L of sodium hypochlorite sprayed onto the bay, and an operator had a splash on his forearm.
Discussion question
Which connections on your unit are only hand-tight when the pump starts?
Call to action
Before every transfer: pins in, checked by a second person.
Keywords
cam-lock, hose, chemical transfer, hold point

One talk, as its page. An example talk; the fields are the product’s, the values illustrative.

TK-0057 · Hand-tight is not tight
Key message
Pin every cam-lock coupling, and have it checked before the pump starts.
Question
Which connections on your unit are only hand-tight when the pump starts?
Edit talk

Where it connects

Incident InvestigationSafety Talks

On the same loop: External Lessons and 41 more modules in one workspace.

Method note

Read the script, or start a conversation? The research supports both.

Supervisors deliver better talks from a short script. Crews learn more when the talk carries a story and a question.

Leandro · Founder, UProcess

A field study found short scripted toolbox guides easier for supervisors than long incident reports. A randomised study found that adding a story and discussion questions raised what workers learned. The script carries the story; the question starts the conversation.

So every talk has a key message, a context and a question.

  • PageThe talk’s own page, for reading before or after the session.

Where Safety Talks usually breaks

Four places a safety talk goes wrong, and what the record does about each.

01

The talk is read at people, not with them.

A randomised study of construction toolbox talks found that adding a narrative and discussion questions significantly increased knowledge gain.

Source: Cunningham et al., American Journal of Industrial Medicine (2018)

In UProcess Each talk has a title, a key message, the context, a discussion question and a call to action, so the question is part of the talk, not an afterthought.

TK-0057 · Hand-tight is not tight

Key message
Pin every cam-lock coupling, and have it checked before the pump starts.
Discussion question
Which connections on your unit are only hand-tight when the pump starts?
Call to action
Before every transfer: pins in, checked by a second person.

The question is a field of the talk.

02

Nothing is ready, so nothing is said.

A field study of construction crews found a quarter of surveyed workers had never run a safety meeting, and supervisors preferred short scripted guides that cut preparation time.

Source: Toolbox talks study, Safety Science 86 (2016)

In UProcess Start a talk from an investigation’s lessons, from an external lesson or from the library. The draft arrives filled in, for you to edit.

Create a safety talk

From an investigationINV-2026-014 · lessons learned
From an external lessonCSB · call to action on combustible dust
From the libraryA UProcess talk, copied into your company

The draft arrives filled in.

03

A signature is not understanding.

OSHA tells its inspectors to look beyond paper training records, which can exist when workers did not understand the material, and requires instruction in words workers understand.

Source: OSHA training policy memorandum, 2007

In UProcess A talk is kept apart from training records, so it is never counted as a course.

TK-0057 · Hand-tight is not tight

Status
Published
Training record
None. A talk is not a course.

Training records stay in Training.

04

The lesson reaches one site.

HSE’s investigation guide asks whether the same risks exist at other locations, and says lessons should be shared across the organisation.

Source: HSE, HSG245

In UProcess Sessions, and the sites a talk reached, are not recorded in UProcess today. Each talk carries the investigation or external lesson it came from.

TK-0057 · source

Based on
INV-2026-014 · Hose coupling came apart during tanker unloading
Sessions
Not recorded in UProcess today

The talk carries the lesson it came from.

TalkSourceStatusPublished
TK-0057 · Hand-tight is not tightINV-2026-014Published12 Nov 2026
TK-0058 · Dust on the beamsExternal lesson · CSB, combustible dustDraft—
TK-0049 · Line of fire at the pumpLibrary · v2Published3 Oct 2026

The record an auditor asks for.

Each talk keeps the lesson it came from.

  • Each talk with its key message, question and call to action.
  • The investigation or external lesson each talk came from.
  • Library talks copied into your company, and the version they came from.
  • When each talk was published.

What’s in a talk

Content
Title, key message, context, discussion question, call to action and keywords, with attachments.
Forms
The talk page, read before or after the crew meets.
Sources
An investigation’s lessons, an external lesson, or a library talk copied into your company.
Library
A library talk copied into your company never changes under you.
Status
Draft, published or archived.

Questions

Is a safety talk a training record?

No. A talk is kept apart from training records. Training records stay in Training.

If a library talk changes, does our copy change?

No. Your copy is yours and never changes under you.

Can a talk start from an investigation?

Yes. Start it from an investigation’s lessons, an external lesson or the library, and the draft arrives filled in.

Does a talk show where it came from?

Yes. It carries its source, such as “Based on INV-2026-014”.

Your next talk, heard and on record.

Start free →No account needed to start. Keep your work when you’re ready.