External partners and authorities in the same platform
Most incident management systems stop at the organisational boundary. In the maritime world, that boundary is exactly where the crisis begins — because a port incident is never only a port's problem.
The problem with the boundary
A fire in a terminal involves the fire service, the harbour master and probably the police. An oil spill involves the environmental authority and the coast guard. A cyber incident in a booking or customs system involves authorities that have their own reporting clocks. A security incident at an ISPS site involves the port facility security officer, the ship's security officer and, at the right level, the state.
The conventional way of handling this is a conference call and a set of documents sent after the meeting. That produces three predictable problems:
- Latency. By the time the external party has the picture, the picture has changed.
- Distortion. Verbal summaries lose detail and pick up emphasis that was never intended.
- Load on key personnel. The people who should be making decisions are instead acting as a switchboard.
See the incident, not a summary of it
One platform, many participants
The dashboard that your crisis team uses can be extended to external collaborators — police, fire departments, environmental agencies, port authorities, agents and other officials. They see the incident, not a summary of it.
Full overview or tailored view
Each external participant can be given the complete picture, or a view scoped precisely to what they require. The environmental authority does not need your commercial action log; the police may need the security timeline and not the operational checklists. Access is granular, inside the hierarchy, and controlled by you.
Real-time, without the phone calls
Status updates and progress reports are pushed through the mobile app by the people on the ground, so the shared picture updates itself. Fewer calls, fewer duplicated briefings, less room for a misheard instruction.
Authority participation in exercises
Because access is configuration, you can run an exercise with the fire service and the municipality in the room — or on the platform — and keep the structure in place afterwards. The division of responsibility is rehearsed, not improvised.
Every participant's contribution is logged
Status changes, actions and inputs are recorded with time and attribution. For the post-event evaluation, the authority question "what did you know, and when?" is answered from the record.
Every party in the incident
Ports and terminal operators
Harbour master, terminal operations, security organisation, and the authorities that respond to a port incident.
Shipping companies and ship managers
Shore-side crisis teams connected to the vessel's reports, with the flag state, class, P&I, agents and port state in the same incident picture where relevant.
Maritime service providers and agents
The parties who are always in the middle of the incident and never in the tool.
Authorities and agencies
Police, fire, environment, coast guard, municipality, customs — as participants with scoped access, and as beneficiaries of a sector that can present them with an accurate operational picture on arrival.
How it is set up — the short version
- Map the participants. Who would need to see what, in each of your realistic scenarios.
- Define the views. Full overview or tailored scope, per role and per agency.
- Grant access through the hierarchy. Granular control inside your document and incident structure — no separate system, no shared spreadsheet, no unmanaged file share.
- Rehearse. Run a table-top or live exercise with the external participants on the platform.
- Keep it warm. Maintain the access and repeat the exercise; a partnership that is only activated at 03:00 is not a partnership.
Show us your worst-case scenario and we will show you the participant view.
In a 30-minute session we will build a demonstration incident and walk through how each external party would see it.
Book a demo