Inform.
Be informed.
If you receive news and it affects more than one person, the whole team needs sight of it.
Clear. Concise. Controlled. Three C's to keep the team informed.
The rule (tap a tile)
Press Tap to reveal communication tips across the specified areas they may require information being passed through the team.
*You can even copy these tips and paste them in your phone notes for ease of reference.
Safety
Anything that changes how safely we can work.
Safety
- What we need to cover: Anything that has an impact on safe working conditions for our team.
- Why: Safety information cannot rely on memory, verbal handovers, or "I thought you knew". When safety conditions change and the update is not passed on, risk multiplies fast and silently.
- Quick reference triggers:
New or unexpected hazards
Changes to method or equipment
Site conditions shifting (weather, ground, access routes)
Anything that makes you pause and rethink how you work - What to consider when sharing an update: Safety update (what changed). Impact (what it affects). Next (plan of action, response).
- Copy:
Safety update: [what changed]
Impact: [what it affects]
Next: [what happens now]
Customer
Timing, access, expectations.
Customer
- What we need to cover: Anything that affects customer expectations, access, timing, or experience.
- Why: Customers lose trust when information changes but messaging does not. One person being out of the loop creates frustration for everyone else.
- Quick reference triggers:
Delays or reschedules
Access or availability issues
Changes to agreed timelines
Complaints or concerns raised - What to consider when sharing an update: Customer update (what changed). Impact (who it affects). Next (what has been agreed).
- Copy:
Customer update: [what changed]
Impact: [who it affects]
Next: [what happens now]
Access
Keys, entry, readiness.
Access
- What we need to cover: Anything that blocks entry, permissions, or site readiness.
- Why: Access issues waste time, fuel, and goodwill when not shared early.
- Quick reference triggers:
Locked gates or doors
Missing keys, permits, or permissions
Site or property not ready
Customer not present - What to consider when sharing an update: Access issue (what’s blocking entry). Impact (which job or crew). Next (resolution or new plan).
- Copy:
Access issue: [what]
Impact: [who or what]
Next: [action or ETA]
Schedule
Changes, priorities, knock-ons.
Schedule
- What we need to cover: Anything that changes job order, priorities, or timing.
- Why: Schedule changes ripple. One missed update can derail an entire day.
- Quick reference triggers:
Jobs moved, added, or cancelled
Priority changes
Crew or dependency changes - What to consider when sharing an update: Schedule change (what moved). Impact (who it affects). Next (revised plan).
- Copy:
Schedule update: [what changed]
Impact: [who it affects]
Next: [new plan]
Stock
Materials, tools, shortages.
Stock
- What we need to cover: Anything affecting materials, tools, or availability.
- Why: No stock update means someone else finds out the hard way on site.
- Quick reference triggers:
Shortages or damaged items
Incorrect or missing kit
Substitutes required - What to consider when sharing an update: Stock issue (what’s missing or changed). Impact (which job or crew). Next (fix or workaround).
- Copy:
Stock update: [what]
Impact: [job or crew]
Next: [fix or timing]
Quality
Standards, rework, sign-off.
Quality
- What we need to cover: Anything affecting standards, workmanship, testing, or sign-off.
- Why: Quality problems repeat when information stays isolated instead of shared.
- Quick reference triggers:
Failed tests or inspections
Repeat defects
Standard or process changes - What to consider when sharing an update: Quality issue (what was identified). Impact (standard or outcome affected). Next (correction or prevention).
- Copy:
Quality update: [what]
Impact: [what it affects]
Next: [fix or prevention]
Money
Approvals, variations, costs.
Money
- What we need to cover: Anything involving costs, variations, or approvals.
- Why: Cost information must be clear, confirmed, and traceable. Assumptions here cause real damage later.
- Quick reference triggers:
Variations required
Extra time or materials
Approvals pending - What to consider when sharing an update: Cost update (what changed). Impact (amount or approval needed). Next (who decides and when).
- Copy:
Cost update: [what]
Impact: [amount or approval]
Next: [decision or timing]
If it affects more than one person, it goes where the team can see it and act.
Quick check
This checklist exists to stop half-stories, assumptions, and second-hand updates.
Before passing information on, pause and check it. If you can confidently tick the points below, you are sharing something useful, accurate, and actionable.
It helps the next person understand what actually changed, know whether it affects them, and decide what to do next without chasing clarity.
If you cannot tick it, do not share it yet. Get the facts first.
You're making work easier.
That is what good comms looks like. Quiet. Clean. Done.
Myth-bust (tap a tile)
Short myths. Shorter fixes. Less chaos.
I told someone.
That is not telling the team.
Reality
- What it is: Info living in a person, not in the process.
- Fix: Post a one-line update where it belongs.
- Best line: Update: [what]. Owner: [who]. Next: [what/when].
I didn't want to bother anyone.
Silence is the bigger bother.
Reality
- What it is: Delaying an update until it becomes a fire.
- Fix: Share early with facts, impact, next step.
- Best line: Heads-up: [what]. Impact: [who/what]. Next: [action].
Everyone saw the message.
Assume nothing.
Reality
- What it is: Relying on feed visibility instead of ownership.
- Fix: Put it where it is searchable and owned.
- Best line: For [owner]: [one line update]. Please confirm received.
One clean update beats five side chats.