Near misses that reach shore — with evidence attached
Near-miss capture, evidence trails, and fleet-relevance flags feed safer meeting topics.
Why fleets still struggle
The cost of how it’s done today
Incomplete or delayed incident reports leave shore guessing, weaken investigation quality, and create insurance and regulatory exposure when evidence is missing.
The traditional approach
Paper forms stay onboard; photos sit in personal phones; corrective actions live in a separate spreadsheet the next auditor cannot trust.
Monday with WaterTight
What changes when this is under control
Crew submit structured incidents or near misses from the dashboard or crew app. Shore reviewers pick them up in the fleet Safety Inbox, request corrections, assign actions, and close only when evidence supports closure.
Time back
Structured submit plus a shore inbox queue beats email chains and lost photo attachments.
Less waste
Less superintendent time chasing incomplete reports vessel by vessel.
Lower risk
Near-miss capture, evidence trails, and fleet-relevance flags feed safer meeting topics.
In the module
How Incident Reporting delivers it
Evidence attachments and factual narrative
Submit to awaiting office review (no legacy “approval” step)
Shore review, reject with comments, and close
Fleet Safety Inbox queue with vessel filters
Optional fleet-wide relevance for safety meeting topics
Capabilities
- Positive observations (separate safety write path)
- Corrective and preventive action tracking
- Push and inbox notification for reviewers
- Partial offline support on mobile with sync
- PDF export with workflow history
- Does not replace emergency or statutory reporting
Ship to shore
How the work moves
- Make the situation safe and follow emergency SMS first
- Crew create the incident or near miss with facts and evidence
- Shore opens the Safety Inbox, reviews, and assigns actions
- Close when corrective actions are evidenced; export for audit
Regulatory alignment
Customers remain responsible for regulatory compliance. WaterTight is the operational system of record.
Questions before you commit
Can crew report from the mobile app?
Yes. Incidents can be raised from the crew app or company dashboard when the user’s rank has incidents write permission.
Is there an “approved” status?
No. The current flow is submit → office review → close. Shore uses incidents_review permission; do not rely on legacy approve permissions.
Does this replace GMDSS or distress reporting?
No. Follow emergency and statutory procedures first. Record the incident in WaterTight when it is safe to do so.
Are exports audit-ready?
Incidents support PDF export with workflow history for audits and management review. Customers remain responsible for what they present to authorities.
Related solutions
Bring this pain to a demo
We’ll walk incident reporting for DPA and Safety Officer on a sample vessel — so you can judge the fit, not sit through a feature tour.