Most inspection and NDT companies have some version of an emergency contact list. It's usually a laminated sheet in the site office, a tab in a shared spreadsheet, or a PDF saved to a network drive that may or may not be the current version. In normal operations, this is invisible. In an emergency, it becomes a serious liability.
When something goes wrong on a live job — a radiation incident during RT work, a confined space emergency, a chemical exposure in a testing lab — the window for effective response is short. The people on site shouldn't be hunting for a phone number through a file server or calling someone who left the company six months ago.
The Problem with External Contact Lists
Emergency contact management fails in predictable ways. None of them require a major incident to observe:
- Version drift. A printed list is accurate on the day it was printed. After that, it degrades silently — personnel change roles, external agencies change numbers, and new branches get added. Nobody updates the laminated sheet until someone notices it's wrong, often at the worst possible time.
- No branch specificity. A single contact list for a multi-site organisation is only useful if every site has the same emergency contacts. They don't. The ambulance service for a remote pipeline inspection site and a CBD testing laboratory are not the same. Generic lists create dangerous assumptions.
- No access control. If emergency contacts live in a shared drive, anyone can edit them — including accidentally. There's no record of who changed what, or when.
- No integration with operations. Emergency contacts stored outside your operations platform mean a gap between where your jobs are managed and where your safety information lives. During an incident, that gap costs time.
What emergency contact management actually requires
Effective emergency contact management for inspection and testing companies isn't complicated — but it does require a few things that spreadsheets and printed lists can't provide.
A single source of truth, accessible from any device
Field technicians on a remote shutdown, lab managers in a fixed facility, and operations staff working from home should all see the same contacts. The directory needs to be in the platform they're already using for jobs and records — not a separate system that requires a separate login.
Branch-level organisation
Each contact should be associated with the branches where it's relevant. A site-specific safety representative, a local emergency service, a regional medical centre — these should be visible to the people working at that branch and filtered out for everyone else.
Always-current personnel records
When a contact person is one of your own staff — a safety representative, a site manager, a first aid officer — their contact details should pull directly from the active user record. If that person leaves the organisation or is suspended, the system should flag the record as requiring an update rather than silently leaving a name that can't be reached.
Click-to-call
During an emergency, nobody should be transcribing a number from a screen to dial it manually. Contact numbers need to be callable with a single tap.
Instructions, not just names
Knowing who to call is one part of emergency response. Knowing what to do before the call connects — evacuation procedure, isolation steps, first aid actions — is the other. That information needs to be one tap away, not buried in a procedure document.
The Compliance Angle
For organisations operating under ISO 45001 (occupational health and safety management), maintaining documented emergency preparedness and response procedures is a clause requirement. Clause 8.2 requires that organisations establish, implement, and maintain processes to prepare for and respond to potential emergency situations — including communicating relevant information to workers and other interested parties as appropriate.
An emergency contact directory isn't just an operational convenience — it's part of demonstrating that you have a functioning emergency response system. A printed sheet that may or may not be current doesn't satisfy this. A structured, access-controlled, auditable directory within your operations platform does.
Similarly, for laboratories operating under ISO/IEC 17025 and inspection bodies under ISO/IEC 17020, personnel records and competency management are audited. A safety representative assigned to a job whose contact record is out of date creates a gap in your traceability — one that an assessor can reasonably question.
What This Looks Like in OMS
The OMS Emergency Contacts module stores all emergency-related contact information directly within the platform — the same system where jobs are created, test records are managed, and personnel qualifications are tracked.
Each contact record captures the role (drawn from the same role library used elsewhere in the system), service provider agency, contact person, branch phone, official mobile, personal mobile, speed dial extension, and free-text emergency instructions. Contact persons are selected from active system users — and if a selected user later becomes inactive, the system flags the record for update in edit mode.
The listing page shows all contacts for the selected branch, filterable by role and status. Phone numbers are click-to-call. Emergency instructions open in a pop-up dialog. Supporting documents — evacuation plans, emergency response procedures, site maps — can be attached per contact and downloaded directly from the listing. An emergency video URL field allows linking to recorded training or response procedures.
Access is role-controlled: System Users, User Managers, and Productivity Users can create and edit contacts. All other users can view and call, but not modify — with a tooltip explaining how to request access if needed.
Separating Emergency Contacts from SWMS
It's worth being explicit about the distinction between emergency contact management and Safe Work Method Statements. SWMS define the hazards, controls, and procedures for a specific piece of work before it starts. Emergency contacts define who to reach and what to do when something goes wrong despite those controls.
Both are part of a complete safety management system. But they serve different purposes at different points in time, and they need to be managed separately. A SWMS that includes emergency contacts as a section creates a version control problem — the SWMS changes every time a contact changes. A standalone emergency contact directory, managed independently and always reflecting current information, avoids that problem entirely.