Inspections and audits

Every inspection planned. Every finding closed.

Findings from inspections and audits, root cause analysis, and follow-up until each one is closed.

Book a demo
Inspection register with flag state, PSC and superintendent inspections, intervals, status and next due dates
Why it matters

A finding is only useful if someone closes it.

Flag state, Port State Control, class and the company's own superintendents all inspect the ship. Each visit leaves a report, and each report leaves findings.

When the reports sit in email and the findings in a spreadsheet, the same deficiency comes back at the next inspection, and nobody can show what was done about it.

An inspection register keeps every inspection, its findings, the root cause and the corrective action together, until each one is closed.

In SEA360

From the inspection plan to the closed finding.

Every type of inspection

Flag state, Port State Control, class and superintendent inspections, internal ISM audits and external DOC, SMC and ISPS audits. Add your own types with their intervals.

More about Port State Control

Next due date

The next inspection is due by its interval. The date can be set by hand when needed.

Status at a glance

Overdue, open and due inspections are marked for every vessel, with the date and port of the last visit.

Recorded on board

The crew record inspections and findings on board, also without a connection.

Findings with root cause

Each finding gets a root cause analysis and a corrective action.

Responsible and target date

Every corrective action has a responsible person and a target date. Overdue actions are highlighted.

From inspections and safety reports

Root cause analysis can start from an inspection finding or from a safety report, such as an incident or near miss, and links back to its source.

Evidence and reports

Attach photos and documents as evidence of the fix, and export inspection reports to PDF.

Root cause analysis

Every finding, until it is closed.

Each line shows the finding, where it came from, who is responsible, the target date and the status.

Root cause analysis register with findings, source, responsible person, target date and status
Getting started

From scattered reports to one register.

  1. 01

    Set up inspection types

    Choose the inspections and audits you track and their intervals.

  2. 02

    Record on board and ashore

    The crew and the office record inspections and findings. On board this also works without a connection.

  3. 03

    Follow up to closure

    Assign corrective actions, attach the evidence and close each finding.

FAQ

Questions about inspections and audits in SEA360.

What is ship inspection management software?

A system that keeps every inspection of a ship, from flag state and Port State Control to the company's own superintendent visits, with the findings and the corrective actions until each one is closed.

Which inspections and audits can we track?

Flag state, Port State Control, class and superintendent inspections, internal ISM audits and external DOC, SMC and ISPS audits. You can add your own types with their intervals.

What is a root cause analysis?

Finding why a deficiency happened, not only what was wrong, so that the corrective action prevents it from happening again. The ISM Code expects non-conformities to be investigated and corrected.

Can the crew record findings on board?

Yes. The crew record inspections and findings on board, also without a connection. They sync when the ship is back online.

Can we attach photos and documents?

Yes. Photos and documents can be attached to each finding as evidence of the fix.

Can we export inspection reports?

Yes, inspection reports can be exported to PDF.

See how it works on a demo fleet. Book a demo