Toolbox talks built from today's work.

Rosie builds the toolbox talk from today's site context.

Topic libraries hand every site the same talk. Rosie writes this morning's talk from what your site actually recorded: yesterday's findings, open corrective actions, the weather moving in, the high-risk tasks on the schedule. The crew listens to this one, because it's about the work they're about to do.

Name the topic. Rosie has already read everything.

Need a talk on working at heights? Building one used to mean digging through binders, PDFs, and a safety program nobody can search. Now the foreman asks in plain language, Rosie reads the company's entire document base — six thousand documents, if that's what it takes — and a structured, signable talk comes back in about two minutes, built from your own standards, not a generic internet handout.

Six thousand documents read. Zero documents browsed.

You do the talk. Rosie makes it signable.

Some talks happen at the rack, not at a desk — a live walkthrough of harness inspection before the crew goes up. Hit record. Rosie turns the recording into a toolbox talk form: a notes summary of what was covered and a crew sign-off list, ready for signatures. The talk that actually happened becomes a record that actually holds.

The foreman never types. The record never slips.

Attendance should be verified, not scribbled.

The clipboard is where attendance goes to die: passed hand to hand, signed illegibly, easy to sign for an absent buddy. In SALUS the foreman shows the QR code, the crew scans, and every worker gets an individual timestamped receipt — which topic, what time, whose verified name — checked against the site list at the scan.

Scan. Signed. Working.

Topic. Time. Name. Verified.

A concern raised in the meeting leaves with an owner.

A worker flags a missing safety guard on press #3 — the kind of comment that usually evaporates when the room empties. Not here: the concern becomes corrective action CA-882 before the meeting breaks — named owner, high priority, due date. The crew watches the status move from raised to closed, and nothing builds reporting culture like watching your concern get fixed. The wider story lives on Crew Communication.

Every crew gets its own talk — in the language it works in.

Relevance used to trade off against scale — one safety manager can't write thirty crew-specific talks a night, let alone in two languages. Rosie can: heights for the crew on the scaffold, PPE for the gate, each generated in about two minutes, in the language the crew actually works in. AI Spanish translation is how one customer's most resistant foreman became the app's biggest advocate.

The office stops choosing between relevant and feasible.