Safety Reports

A safety report is the questionnaire behind an inspection: the questions are answered per topic, what needs attention becomes an observation, and the observations become the tasks that are followed up afterwards. The report belongs to an audit and is closed from there.

Three ways to work on a report

The same report can be worked on in three places. They are meant for different situations, and nothing has to be decided in advance - a report can be started on the PC and continued on a phone.

Where When to use it
ZeeBORN on the PC In the office: creating the inspection, the full report with all tabs, the final review. This is what the pages below describe.
Web portal - browser on phone or tablet On board or on the move, with a connection. Answering topics, adding remarks, photographing findings with the camera, and giving approvals. No installation, can be placed on the home screen like an app.
Offline file Without any connection. The whole report leaves the system as a single file, is worked on in a browser anywhere, and is imported again afterwards.

The pages here

Topic What it covers
Questionnaire Structure What counts towards the score, chapters that repeat per tank or crane, and questions with sub-questions.
Working with a Report Referring to the previous inspection, flagging what matters, observations with due date and responsible role.
Port State Control and Conditions of Class The two extra tabs, where their entries come from, and how the audit type switches them on.
Editing a Closed Report The two editing modes, what each records, working on board with office rights, and distributed audits.
Offline Editing Taking a report off the system as a single file, working on it in a browser without a connection, and bringing it back.
On a phone or tablet Working on a report through the web portal - and how that differs from the offline file.

For the way an inspection runs as a whole — from planning to final verification — see the Inspection Workflow.