PleoStack

Getting Started with Safety

A complete walkthrough — deliver a toolbox talk, run a safety walk, raise a permit, and report an incident, then track it all from the Hub.

This guide walks you through the Safety module end to end — a toolbox talk, a safety walk, a permit to work, and an incident — so you can see how each workflow behaves and how the Hub ties them together. The Safety module is in beta.

Quick Summary
  1. Open the Safety Hub to see what needs attention
  2. Log a toolbox talk and route it for sign-off
  3. Start a safety walk and log observations as you go
  4. Request a permit for hazardous work and take it through approval
  5. Report an incident, then investigate and close it
  6. Come back to the Hub to track open items

Before You Begin

Prerequisites

Reporting incidents and logging walk observations needs safety create access — held by default by the project owner, PM, safety officer, superintendent, QC inspector, and foreman. Delivering talks, approving permits, and investigating incidents are typically done by a safety officer or above.

Six permit templates (hot work, work at height, excavation, confined space, lifting, electrical isolation) are seeded for your organisation, along with default safety policies. If the request panel tells you there are no active templates in this project, create one under Permits → Templates first.

1

Open the Safety Hub

Click Safety in the sidebar. The Hub is your safety console:

  • The KPI strip shows open incidents, active permits, talks this week, and open walk findings
  • The needs-attention feed lists what to act on — open incidents, expiring permits, and talks awaiting sign-off
  • The incident trend chart shows the last 8 weeks

Everything on the feed is a deep link — tap a row to jump straight to the record.

The Safety Hub — start here to see what needs your attention
2

Log a Toolbox Talk

Toolbox talks record a pre-work safety briefing and who attended:

  1. Go to Safety → Toolbox Talks and click Log talk (or use the + button on a phone)
  2. Pick a topic (e.g. Fall Protection) and add a location
  3. Record attendance — a headcount or named attendees
  4. Add any notes and photos, then submit

The talk enters a cascade sign-off — an ordered chain of steps named after roles (by default: deliverer → PMC → safety head). Each step is acknowledged or approved by someone with safety approval rights until the talk is closed.

Logging a toolbox talk — topic, location, attendance, and evidence
3

Run a Safety Walk

Safety walks are quick, ad-hoc site inspections built around observations:

  1. Go to Safety → Safety Walks and click Start walk
  2. Give it a name (e.g. "Morning walk — Tower A") and start
  3. As you walk, tap Log observation for each thing you see:
    • Choose a severity — good, low, medium, high, or critical
    • Describe what you saw and attach a photo
    • Optionally capture your location
  4. Turn any observation into a safety issue or escalate it to an incident
  5. When you're done, tap Complete walk
A completed walk — observations rated by severity, ready to promote or escalate
4

Request a Permit to Work

Permits authorise hazardous work for a fixed time window:

  1. Go to Safety → Permits and click Request permit
  2. Choose a template (hot work, work at height, excavation, confined space, lifting, electrical isolation) and give the permit a title
  3. Set the validity window (valid from → valid to)
  4. Assign the approvers — you are the Requester at step one, and every later party has to be assigned to a real person
  5. Create the permit, then on its detail page work through the mandatory checklist items and attach any required documents before Submit for approval

The permit stays pending while it moves through the party chain. Once every party has approved and the validity window has opened, it becomes active. It flags as expiring within 24 hours of its end time and expired once the window passes.

An approver's reject is a send-back, not an ending: the chain resets to the requester for rework (optionally raising a safety issue) and the permit stays pending. Extending a permit is off unless an admin turns Allow extension on in Safety Policies, and where a template requires close-out, only the final approver can confirm it.

An active permit — validity window, requirements checklist, and approval timeline
5

Report and Investigate an Incident

Incidents capture near misses, injuries, and damage:

  1. Go to Safety → Incidents and click Report incident
  2. Pick a type (near miss, first aid, lost time, property damage, environmental, and more)
  3. Record when and where it happened and a clear description
  4. Add evidence, flag a stand-down if work must stop, and mark if it's regulatory reportable
  5. Submit — the incident is reported

To close it out, open the incident and work the investigation panel:

  • Record the root cause
  • Add corrective actions and mark each one done as it's completed
  • Lift the stand-down when it's safe

Depending on your policies, an incident can't be closed until the root cause is filled and every corrective action is done.

Investigating an incident — root cause and corrective actions gate the close-out
6

Track It All from the Hub

Everything you just created rolls up to the Safety Hub:

  • Open incidents and expiring permits appear in the needs-attention feed
  • Talks awaiting sign-off are listed with a deep link
  • The incident trend updates automatically

Come back to the Hub each day to see what still needs action.

Next Steps

Now that you've seen the full cycle, dig into each area:

  • Safety Hub — reading the console and acting on the feed
  • Toolbox Talks — the cascade sign-off in detail
  • Safety Walks — observations, issues, and escalation
  • Permits to Work — the permit lifecycle and approvals
  • Incidents — investigation and close-out
  • Policies — tuning the workflows for your project (Admin → Safety → Policies)