Liquid RockSOP System General SOP
SOP Hub › General › Communication Protocol

Communication Protocol

How the crew syncs, reports problems, and hands off — built for night shifts where the owner is off-site. Silence is not status.

SOP-GEN-005v1.0Applies to: ALL SITES
SOP IDSOP-GEN-005
Version1.0  ·  Effective TODO(confirm) date
OwnerSite Manager
Applies toAll crew, all sites
ReviewAnnual

1 Channels: Sync vs Async

WhatChannelWhen
Immediate safety / scope blockerPhone callNow
Status, completed tasks, photosLive Task Board + daily log / channel (async)As you go
End-of-shift report to ownerStructured message / voice note (async)Before owner sleeps
Same-day field-to-ownerNever email

One messaging channel per active job site. Every meeting/decision produces a written artifact within 24 hours — no artifact, it didn't happen in the record.

2 Pre-Task Brief (PTP) Agenda

Before every distinct activity (10–15 min, site manager leads, all crew present):

  1. What we're doing — specific task, location, sequence.
  2. Hazard scan — risks specific to this task & site right now (not generic).
  3. Controls & precautions — concrete mitigation for each hazard.
  4. PPE — what's mandatory before this task starts.
  5. Roles — who does what; who's spotter; who runs equipment.
  6. Coordination — other trades, deliveries, access constraints, facility staff tonight.
  7. Scope boundary — where the task stops; what condition forces a pause & re-brief.
  8. Questions — "What concerns do you have? What did we miss?"
  9. Sign-off — each crew member confirms understanding; site manager logs names + time.
🔁 Re-brief on change
If conditions change materially mid-task (site condition, scope request, equipment): STOP and re-brief before continuing.

3 Escalation Path

TierWho → whoWhenHow / response
1Worker → Site Manager (on-site)Safety hazard, unclear instruction, material/tool shortage, deviationDirect verbal; if SM unavailable, stop that task. Response within the hour.
2Site Manager → OwnerScope change above field authority, injury/near-miss, regulatory contact, client conflictCall if urgent; structured message if not. Owner acks within ~2 hrs (night: async log for non-emergencies).
3Owner → ExternalWorkSafeBC reportable incident, contractual dispute, client authorization for overrunWorkSafeBC portal / written notice. Serious incidents are time-bound (immediate notice; see Quality & Safety).
🛑 Immediate stop-and-call
Any imminent risk of serious injury → worker stops, calls site manager; site manager calls owner; owner decides on re-entry. No production pressure overrides this.

4 End-of-Shift Debrief

Written by the outgoing lead, read by owner (async) and incoming lead before next shift. Five fields, under 10 minutes if logged throughout:

  1. Work completed — tasks finished, to what standard, which zones.
  2. In progress / state of play — started-not-finished; exact condition left.
  3. Blockers & issues — what slowed/stopped work; field decisions made & why; owner follow-ups.
  4. Safety events — incident, near-miss, hazard observed; toolbox talk conducted.
  5. Ready-for-next-shift — what incoming crew needs to know; site warnings; material/equipment status.
🌙 Owner night report
When the owner is off-site, they get a structured end-of-shift report before sleeping — not a check-in. Goal: the owner can reconstruct the whole shift and make next-day decisions from the written record alone.

Related SOPs

SOP-GEN-005 · Communication Protocol · v1.0 — Liquid Rock SOP System.