A defect only matters to a ship until it becomes a work order. After that, it matters to the Chief Engineer, the superintendent and eventually the inspector, and each of them wants to know the same three things: who owns it, what was done, and how anyone knows it worked. This guide covers how to raise, assign, track and close PMS work orders and how to link corrective actions to the inspection findings that triggered them. For the wider process of logging defects across a fleet, see our marine defect tracking software guide.

From Defect to Closed Work Order: Corrective Action That Holds Up
Raising, assigning, tracking and closing PMS jobs with evidence, and linking each corrective action to the inspection finding behind it.
Free trial available. Or book a walkthrough built around your own defect and work order process.

ISM 10.2
Report every non-conformity
With its possible cause, if known, per the IACS guide to ISM maintenance (Rec. 74).
Verify it
Corrective action is not enough
IACS: "it is not enough simply to take corrective action. The effectiveness of such action must be verified."
15 days
RightShip close-out window
For operators responding to inspection findings, with extensions only in limited cases.
Most cited
Maintenance in PSC detentions
IACS says more detentions linked to safety management failures refer to maintenance than to any other ISM clause.

The Defect Lifecycle: What the ISM Code and the IACS Guide Expect

Where defects come from and why each source needs a linked work order

The IACS guide to managing maintenance under the ISM Code says problems may be discovered during routine technical inspections or maintenance, or after a breakdown or accident. External records, such as class, statutory, port State control and vetting records, add findings from outside. Whatever the source, each defect needs a work order that can be tracked to closure. The grouping below is our reading of that guide.

Two Ways a Defect Reaches the Work Order List (Our Reading of the IACS Guide)
FOUND EARLY
Routine inspections and maintenance
The IACS guide notes problems may be discovered during routine technical inspections or maintenance. These are the cheapest defects to fix.
FOUND LATE
Breakdowns and accidents
Problems also surface after a breakdown or accident. These need a cause analysis and a check for the same fault elsewhere in the fleet.
FROM OUTSIDE
Audits, class, PSC and vetting
The IACS record list includes class, statutory, port State control and vetting records. Each finding needs a linked job.
Grouping is ours, built on the IACS guide's list of how problems are found and which external records exist.

The six-step corrective action loop and why verification is the step people skip

IACS describes the corrective action process as identify the problem, establish the cause, propose solutions, evaluate them, implement the chosen one, and evaluate effectiveness. If the action is not effective, it returns to the loop. The guide states plainly that taking corrective action is not enough, and that effectiveness must be verified. Many ships stop at step five, which is why verification gets its own gate in the templates below. For how this fits a wider planned maintenance system, see our {L2}.

The Corrective Action Loop in the IACS Guide: From Problem to Verified Closure
1
Identify the problem
2
Establish the cause
3
Propose solutions
4
Evaluate them
5
Implement the choice
6
Evaluate effectiveness
Not effective: back into the loop
Effective: close the job
Sequence from IACS Recommendation 74, Rev.2 (2018). IACS also says responses should address underlying management-system failures, not only the immediate defect, and that lessons should be checked for relevance across the fleet.
Turn Every Defect Into a Task With an Owner, a Deadline and Proof
Raise work orders from inspections, attach dated photos, assign owners and keep a verified closure on record for every vessel.
Free trial available. Or book a walkthrough built around your own defect and work order process.

Raising and Assigning a Work Order: The Fields That Make It Closable

What a complete work order should capture at the moment the defect is found

A work order raised in a hurry usually fails at closure, because nobody wrote down what was wrong or why. ISM clause 10.2 asks for the possible cause to be reported where known, and the critical equipment list under 10.3 tells you which orders need faster escalation. The template below adds the fields that make the order closable: owner, deadline, proof and a verifier.

Anatomy of a Work Order a Chief Engineer Can Close With Confidence (Our Template)
WhatEquipment, location and a one-line defect description
Why it mattersCritical equipment flag and risk level
SourceRoutine inspection, breakdown, audit or external finding
Who and whenNamed owner, deadline and spares needed
CausePossible cause at raising, confirmed cause at closure
ProofPhotos, readings or report attached on completion
Verified byA second person confirms the fix worked
LinkRelated inspection finding or non-conformity number
Our layout. The IACS guide asks for the possible cause to be reported where known (10.2) and for effectiveness to be verified. The other fields are our suggestions.
Work order fields and why each one earns its place (suggested template unless marked)
FieldWhat goes in itWhy it mattersSource status
Equipment and defectEquipment tag, location and a clear descriptionLets the right person find and fix itOur suggestion
Possible causeCause at raising, if knownISM 10.2 asks for the possible cause, if knownIACS Rec. 74
Critical flagMarks equipment on the ISM 10.3 listRoutes the job to faster escalationIACS Rec. 74
Owner and deadlineA named person and a dateWithout both, a job driftsOur suggestion
Completion proofPhoto, reading or reportShows the work was doneOur suggestion
Effectiveness checkWho verified, when and howCorrective action must be verifiedIACS Rec. 74
Linked findingAudit, class, PSC or vetting referenceCloses the loop with the sourceOur suggestion
IACS Rec. 74 for the rows marked as sourced. Everything else is our suggested template.

Tracking Orders Through to Closure With a Verification Gate

A status path that stops jobs being closed before anyone checks them

Most PMS tools have statuses like open, in progress and closed. The path below adds one: awaiting verification. A second person checks the work before closure, which matches the IACS point that effectiveness must be verified. If the check fails, the order returns with the reason recorded. The status names are ours and should be adapted to your system.

A Work Order Status Path With a Verification Gate (Our Suggestion)
Raised
▶
Assigned
▶
In progress
▶
Awaiting verification
▶
Closed
If verification fails, the order returns to In progress with the reason recorded.
Our status names. The gate reflects the IACS point that effectiveness must be verified. Adapt the names to your PMS.

How to judge the strength of the evidence on a closed job

Closing a job with no note proves nothing, and a text note is only a claim. A dated photo is better, a photo with a reading or test result better still, and for critical equipment a second person's check is the strongest. The bars below are our own illustration of that ladder.

How Strong Is the Evidence on a Closed Job? (Our Illustration of Relative Strength, Not Measured Data)
Closed with no note

None
Closed with a text note only

Weak
Closed with a dated photo

Fair
Photo plus reading or test result

Good
Photo, test result and a second person's check

Strong
Our qualitative illustration. The widths show relative strength and are not data. For critical equipment, aim for the strongest rung your procedures allow.

Why a repeat defect should trigger a fleet check and a change to the plan

The IACS guide says lessons should be checked for relevance across the fleet, and that analysing maintenance records can justify changing inspection or maintenance intervals and reveal recurring problems. For a Chief Engineer, that means tagging orders by equipment type and cause so that the same fault on two ships is visible to the superintendent. When a defect repeats, ask whether the interval, the spare or the procedure needs to change, and record the decision in the order.

Why every external finding needs a work order with its own reference

The SEE-Berufsgenossenschaft ISM circular on reports and analyses of non-conformities says the aim is that internal investigations and analyses lead to appropriate corrective and preventive actions, and that a missing report to the administration can cause port State control difficulties even when corrective action was taken. A finding that lives only in an inspection report is easy to lose. Give each one a work order that carries the finding's reference and a closure that points back to it.

Linking inspection findings to work orders: what each source needs (our suggested mapping)
Finding sourceWork order actionEvidence at closureCheckpoint type
Internal inspection or auditOne order per finding, with the audit item referencedPhoto and the verifier's noteVisual
Class survey or condition of classOrder referencing the class item and due dateSurveyor-accepted report or certificateRecord
Port State control deficiencyOrder marked urgent, with the authority's referenceRectification record and photosRecord
Vetting inspection observationOrder with cause, correction and preventionRoot cause analysis and photosRecord
Breakdown or incidentOrder plus cause analysis and a fleet checkTest run results after repairTest
Overdue planned jobOrder with reason and new date, approvedCompletion proof or approved deferralRecord

What a vetting close-out submission looks like in one example

RightShip's help page for its close-out process gives operators 15 days from receipt of the findings, with extensions only in limited cases. It asks for a detailed root cause analysis, an explanation of cause, correction and prevention, and supporting evidence such as photographs. Independent superintendents review each submission. Other vetting schemes and class have their own rules, so use this as an example of the pattern, not a universal standard.

What a Close-Out Submission Contains: The RightShip Model (Vetting Example)
Cause
Detailed root cause analysis.
Correction
What was done to fix the finding.
Prevention
Action to prevent recurrence of similar findings.
Evidence
Photographs and the root cause analysis.
Source: RightShip close-out process help page. Operators have 15 days from receipt of findings, and independent reviewers assess each close-out. The page does not state acceptance criteria, which sit in a matrix we could not see. Other vetting schemes have their own rules.

The Work Order Closure Checklist for the Chief Engineer

A checklist with a checkpoint type on each item before an order is marked closed

Before closing any order, especially one on critical equipment, run through the table. It covers the description, cause, ownership, the repair, a test, evidence and verification. Adapt it to your PMS and company procedures.

Work order closure checklist for the Chief Engineer, with a checkpoint type on every item (our suggested template)
ItemWhat to checkCheckpoint type
Defect descriptionClear enough that someone else could find and fix itRecord
Cause recordedPossible cause at raising and the confirmed cause at closureRecord
Critical equipmentFlag checked and standby arrangements consideredRecord
Owner and dateNamed owner and a deadline, with any extension approved and explainedRecord
Repair doneWork done as described and equipment in a fit stateVisual
Function testedEquipment run or tested after repair, result recordedTest
Evidence attachedDated photos, readings or reports attachedRecord
VerificationA second person confirmed the fix worked, and the order links to its source findingRecord
Our suggested template. Checkpoint types: Visual, Test and Record.

Mistakes That Leave Defects Closed on Paper but Open on the Ship

Six habits that undermine corrective action

1
Closing the order when the part is fitted
Fitting is not the same as fixed. IACS says effectiveness must be verified, so test and check before closing.
2
Fixing the symptom only
IACS says responses should address underlying management-system failures, not just the immediate defect.
3
No possible cause at raising
ISM 10.2 asks for the possible cause, if known. A blank field also makes later analysis harder.
4
Orders with no named owner
Shared ownership usually means no ownership. Put one name and one date on every order.
5
Findings with no linked order
An audit or PSC finding that lives only in a report can be forgotten. Link every finding to an order.
6
Not looking across the fleet
IACS says lessons should be checked for relevance across the fleet. One ship's defect may be waiting on another.

Systems That Keep Work Orders, Evidence and Findings Together

How a dated photo repository, task ownership and deadlines support closure and audit

Work orders get weak when the proof lives in a camera roll and the finding lives in a PDF. Marine Inspection supports a dated photo repository, observations turned into tasks with owners, deadlines and evidence, and certificate and equipment tracking. A dated photo of a repaired pump attached to the task, the task linked to the inspection observation, and an owner and deadline on each give the Chief Engineer and the superintendent one record to open. It does not replace your own procedures or the verification steps in them.

Frequently Asked Questions About PMS Work Orders and Corrective Action

What does the ISM Code say about reporting defects?

Clause 10.2 says the company should ensure that any non-conformity is reported, with its possible cause if known. The IACS guide describes a non-conformity as a technical deficiency, meaning a defect in or failure of part of the ship's structure, machinery, equipment or fittings.

Is raising a corrective action enough?

No. The IACS guide says it is not enough simply to take corrective action, and that the effectiveness of the action must be verified. If it is not effective, the problem goes back into the loop.

What steps should a corrective action follow?

IACS sets out: identify the problem, establish the cause, propose solutions, evaluate them, implement the chosen one, then evaluate effectiveness.

How long do we have to close out inspection findings?

It depends on the scheme. RightShip gives operators 15 days from receipt of findings, with extensions considered only where there is genuine difficulty. Class, flag and other vetting schemes set their own limits.

What evidence does a vetting close-out need?

On the RightShip page, each submission should have a detailed root cause analysis, an explanation of cause, correction and prevention, and supporting evidence such as photographs.

Does a company have to inform the flag State of defects?

An ISM circular from SEE-Berufsgenossenschaft says a missing report to the administration can cause port State control difficulties even when corrective action was taken, and that companies should advise the administration considering the urgency of the case. Check your own flag's rules.

Where does the guide say deferrals should be handled?

The IACS guide does not address deferring maintenance. Follow your company procedures, class requirements and flag rules, and record the reason and approver.
Close Every Defect With Proof, Not Just a Tick
Work orders, owners, deadlines, dated evidence and linked inspection findings for every vessel, in one system your engineers and superintendents can use.
Free trial available. Or book a walkthrough built around your own defect and work order process.