Observations

The "Observation Response Workbench" is where you answer an inspector’s observation properly after the report lands. Oil majors expect a structured reply — a root cause, a corrective action, a preventive action and a lesson for the rest of the fleet. A reply that just says "corrected" is itself a warning sign to the reader.

Each observation gets its own card: a five-why chain to find the real cause, the nine human-factor headings (PIFs), the four response boxes, a countdown to the reply deadline and a date for checking later that the fix held.

Everyone, on every plan. Observations are part of the ship’s file, so every enrolled phone on a ship licence sees the same cards. "Draft with AI" needs a plan with AI and internet.

1. Tap "New observation" and paste the "Observation text (as written by the inspector)" exactly as it appears in the report.
2. Pick the SIRE "Chapter" and, if you have one, the "SOC/NOC code (optional)". Tap "Create & start analysis".
3. Fill the five "WHY" lines in order: why it happened, why that cause existed, why the condition developed, why the barrier failed, why the system allows it.
4. Under "Map the human factors (PIFs)" tap every factor that played a part, for example "Stress, workload & fatigue".
5. Write the "Root Cause", "Corrective Action", "Preventive Action" and "Fleet-wide Lesson" — or tap "Draft with AI" for a first draft from your whys and PIFs, then edit it. The draft is a starting point, never the final reply.
6. Set the "Report date" (the date on the inspection report — the 14 days to respond count from it) and the "Effectiveness check" date, the day you will confirm the fix held.
7. Tap "Copy response" to paste the text into your e-mail or company system, or "Print / PDF". Tap "Close" when the reply has gone; "Reopen" brings it back.

• "Crew error" is never a root cause on its own. The root cause is what allowed the error — the missing check, the unclear procedure, the workload.
• The "N d to respond" pill turns red with 3 days or fewer left; "response N d overdue" means the 14 days have passed.
• An open card with an empty root cause or preventive action shows "Incomplete" — finish it before you close.

• The reader is usually the vetting superintendent at the oil major. They look for a systemic cause, evidence the item was fixed, a change that stops it coming back, and proof the fleet was told.
• At the next inspection the inspector may ask what changed since the earlier observation. Keep the closed card — it is your evidence.

• The 14-day countdown runs from the "Report date" on the card — set it to the date on the inspection report. Until it is set, the countdown runs from the day you captured the observation in the app.
• "Draft with AI" needs internet and a plan with AI (not Free). Everything else on the card works offline.
• "Print / PDF" is a counted document on the Free plan (3 main PDFs a month, watermarked); paid plans print without limit.
• Deleting a card deletes its five-why analysis too; the app asks you to confirm.
• Observations sync through the SeaReady server as part of the ship’s file whenever the phone has internet; with no connection, changes are held on the phone until the connection returns.