Safety module

Toolbox Talks with clear completion control

Deliver structured safety talks, capture signatures in real time, and complete only when attendance, content, and distribution checks are satisfied. Every step is traceable from draft to final PDF evidence.

What teams get with Toolbox Talks

Template-led talks

Create talks from predefined toolbox templates with consistent sections, categories, and response capture.

Live attendance and signatures

Set persons present, capture kiosk-friendly signatures, and track progress as signatures are added.

Validation-gated completion

Completion unlocks only when signatures match persons present and required content checks pass.

PDF and audit evidence

On completion, SiteGrip generates a PDF pack, preserves completion metadata, and logs each major action.

Step-by-step workflow

Step 1

Create draft

Start a new talk, select template, and auto-generate the TBT number (TBT-YYYY-NNN).

Step 2

Capture content

Complete the template responses and set persons present for the session.

Step 3

Collect signatures

Use the present/capture flow so every attendee signs with name and optional job title.

Step 4

Run completion checks

System validates draft state, content rules, matching signatures, and distribution setup.

Step 5

Complete and publish evidence

Generate PDF, lock the talk as completed, and keep the full audit trail accessible.

Notification system explained

Toolbox Talk completion uses SiteGrip's event-driven notification model. Distribution recipients are queued, then processed asynchronously for in-app and channel-based delivery.

How delivery works

  1. 1

    Completion triggers notification events

    When a Toolbox Talk is completed, recipients from the distribution list are queued for delivery.

  2. 2

    Server action queues the event

    SiteGrip follows a fire-and-forget pattern: server actions call queueNotification() rather than sending directly.

  3. 3

    Queue worker handles delivery

    Cloudflare Queue and workers process messages and send through configured channels.

  4. 4

    Channel and severity rules apply

    In-app is always used; email/SMS behavior follows notification severity, channel policy, and rate limits.

Governance and control

  • Role-based permissions for create, edit, capture, complete, and delete actions
  • Action-level audit logging for created, signature activity, status changes, and completion
  • Project-scoped visibility so teams see talks only in projects they can access

Practical channel model

In-app updates are always available, while email and SMS depend on event severity and configured notification rules, with anti-spam limits to prevent noisy delivery.

Deliver every Toolbox Talk with evidence confidence

Keep site communication structured, capture attendance reliably, and complete talks with a trusted record that supervisors and auditors can review.

Launch SiteGrip