SMS Reporting Schedule
The company response is critical and depends on shared awareness, not just onboard actions. When information is communicated clearly and promptly, the company can coordinate resources, provide guidance, and support the vessel more effectively. It also allows the company to identify patterns or recurring issues across the fleet, enabling proactive measures and continuous improvement of safety standards.
- It turns incidents, near-misses, and defects into organizational learning, so the same failure is less likely to happen again.
- It enables fast shore-side support (technical, medical, legal, crewing), which can reduce harm and escalation.
- It creates traceability and accountability: what happened, what was done, and what still needs closure.
- It helps identify trends across vessels and time, so preventive actions can be taken before a serious event occurs.
- It supports compliance with ISM and flag/state obligations, protecting crew, vessel, and company.
This is exactly what a strong safety culture looks like: people report early, without blame, so risks are visible and can be controlled collectively.
1. Critical reportings
1.1. Non-conformity and accident reports
Purpose
- Record all non‑conformities, accidents, near‑misses, occupational diseases, and defects
- Bring such situations to the attention of the Master and Yachting Concept Monaco
- Plan and track root‑cause investigations and identify long‑term preventive action
When
- Immediate phone call to the office or to the Designated Person Ashore (DPA), followed by a detailed report in Deepblue© as soon as possible
Closure by the DPA
- All immediate, corrective, and preventive actions implemented
- Evidence saved/referenced in the Deepblue© entry (e.g., emails, photos, third‑party confirmations, witness statements)
- Closure agreed by the Master
1.2. Defects or other less important reportable
For defects, near‑misses, occupational diseases, observations, or reportable items, report as follow:
Purpose
- Record all non‑conformities, accidents, near‑misses, occupational diseases, and defects
- Bring such situations to the attention of the Master and Yachting Concept Monaco
- Plan and track root‑cause investigations and identify long‑term preventive action
When
- Same day
Closure by the DPA
- All immediate, corrective, and preventive actions implemented
- Evidence saved/referenced in the Deepblue© entry (e.g., emails, photos, third‑party confirmations, witness statements)
- Closure agreed by the Master
1.3. Crew complaints
Purpose: Record formal crew complaints not resolved by onboard procedures; all complaints are treated confidentially
When: Same‑day email to the DPA and Director, followed by a detailed written report as soon as possible (no specific form required)
Closure by the company: Close when agreed with the crew member or, where applicable, the Flag State (if no valid complaint)
2. Routine reportings
2.1. Master’s report
- Purpose: Acknowledge to the Company the yacht’s compliance status
- Frequency: Monthly
- Method: DPA acknowledges receipt in Deepblue© and reviews
2.2. Chief Engineer’s report
- Purpose: Confirm status of compliance with the Planned Maintenance System (PMS)
- Frequency: Monthly
- Method: DPA acknowledges receipt in Deepblue© and reviews
2.3. Onboard safety and security meeting
- Purpose: Record crew review and discussion of safety, security, and crew welfare
- Frequency: Monthly
- Method: DPA acknowledges receipt in Deepblue© and reviews
2.4. Yacht drill schedule
- Purpose: Demonstrate compliance with required drills on board
- Frequency: Monthly
- Note: Missed scheduled drills must be made up at the earliest opportunity
- Method: Text message to the specific yacht group
2.5. Permit to work
- Purpose: Prevent execution of hazardous work without supervision and controls
- Timing: Before specified task
- Responsibility: Safety Officer/Officer‑in‑Charge
2.6. Departure and arrival
- Purpose: Notify shore‑side support of planned yacht movements and safe arrival
- Timing: Immediately after departure and arrival for each voyage
- Method: Text message to the specific yacht group
2.7. Passage plans
- Purpose: Ensure safe and compliant voyages
- Timing: For each voyage, from berth to berth
- Method: Upload passage plans to Deepblue© and retain onboard
3. Revision history
The Master is responsible for ensuring that the latest version of the manual is available on board.
| Version | Date | Editor | Revision history |
|---|---|---|---|
| 1.0 | 26 Nov 2023 | Christophe Guegan | Initial commit |
| 1.1 | 28 Sep 2025 | Christophe Guegan | Rewrite & Simplification |
| 1.2 | 14 Mar 2026 | Christophe Guegan | Add Introduction |

