Safety and Training Notes
Competency, Training & Document Control
A. We need a formal competency assessment system
We must prove that staff are competent to perform procedures, tests, and field tasks.
This requires:
Documented training
Competency assessments
Sign-off records
Evidence of capability tied to each procedure
B. Paperwork must show ability to perform specific tests
For every major task (e.g., cable testing, PD, transformers, commissioning), staff need:
A completed training record
A competency sign-off
Evidence stored centrally
This is essential for compliance, insurance, contracts, and internal safety assurance.
C. Intranet as the central entry point
The intranet should become the single source of truth for:
Procedures
Training materials
Document control
Competency frameworks
Procedures and training content must be linked directly.
D. Bridge between files + training platform
Training modules must link back to:
Procedure documents
Field documents
Templates (project briefs, checklists, safety forms)
A tight integration ensures consistency and reduces confusion.
E. Formalise onboarding
New staff must complete:
Safety onboarding
Procedure training
“Project Brief” training
Competency steps
This needs to be embedded into the training platform, not handled ad hoc.
F. Prove retention of knowledge
It’s not enough to train once.
We must evidence:
Ongoing retention
Refresher training
Practical checks
The training platform must track this automatically.
G. Next steps
Matt will work with managers during the quiet period to build out the platform and structure the training program properly.
2. Safety – Current Status & Risks
A. Safety performance is strong
Objectively, we’re doing well on safety.
The increase in reported incidents shows improved awareness and culture — not increased risk.
B. Remote safety observations
If only one team member is onsite, supervisors can perform safety observations via Microsoft Teams (remote visual checks).
Minimum requirement:
Two safety observations per month per team.
C. Zero tolerance for high-risk incidents
“One bad incident will be the end of us.”
We must continue active, disciplined safety management.
Major risk areas must be addressed before they escalate.
D. Incident reporting delays
Incidents are being logged too slowly.
The current 24-hour timeframe is too long.
Training needed on:
What is an incident
What is a near miss
How quickly it must be reported
Exact reporting procedure
This is urgent from a compliance and insurance standpoint.
E. Concerns raised about NZ field behaviour
Jon raised concern about Nixon (NZ) using a Megger in breach of procedure.
This highlights the need for:
Supervision
Competency sign-off
Better oversight of new staff
Clear enforcement of procedures
F. Supervision of new starters
We need a clear structure for:
Checking that new staff follow procedures
Supervising their early work
Signing off their competency
Ensuring safety compliance from day one
This reduces risk and improves field consistency.
3. Overall Themes
machinemonitor® needs to create an integrated system where:
Procedure → Training → Competency → Safety → Document Control
all live in one ecosystem.Training is structured, mandatory, and linked to the tasks we perform.
Competency is documented and auditable.
Safety behaviours are reinforced continuously.
New staff are supervised and formally signed off.
Incident reporting is immediate, accurate, and consistent.
Remote safety observations are embedded into our workflow.
Managers and Matt collaborate to build the complete platform during downtime.
