On board, a work order looks nothing like a factory job card. The specialist workshop is three thousand miles away, the only spare available is the one already in the store, and the job is often carried out while the vessel is under way. Yet almost everything written about work order management assumes a fixed industrial site: one technician, one maintenance manager, one travel time to shave down. Transferred unchanged to a ship, it misses the point entirely.
The work order is nevertheless the single most important object in marine maintenance. It carries the record of what was done to a component, by whom, on what date and with which parts. It is the first thing an auditor opens, and it is what the port State control inspector asks for when deciding whether the vessel's planned maintenance system is alive or purely decorative. Digitalising it is therefore not a question of modernity: it is a question of the quality of the evidence.
This guide follows the full life cycle of a work order on board — request, planning, execution, watch handover, closing, analysis — and sets out what a marine CMMS has to be able to do at each stage.
Why a work order changes nature on board
Three constraints separate a marine work order from its shore-based equivalent, and they apply together, all the time.
Isolation first. A vessel under way has no central store an hour away and no contractor to call in for the day: the crew is the only labour force and the onboard inventory is the only stock.
Time second. The vessel does not stop because a work order is open. Watches follow one another and crews rotate, so a job opened on a Tuesday morning may well be finished by people who were not on board that day.
Evidence third. A poorly documented shore job costs time; a poorly documented marine job costs an audit observation, and sometimes a non-conformity.
The life cycle of a work order on board
The cycle is the same one used everywhere else — request, planning, execution, closing, analysis — but every stage behaves differently once it takes place on a ship.
The request: from an observation in the engine room to a work order
It all starts with an observation: a leak at the gland of a circulating pump, unusual vibration on a bilge fan, an alarm that keeps repeating with no obvious cause. On board, the person who notices is rarely the person who will carry out the work.
A request raised on the spot, from a phone, with a photograph and the exact identification of the component, is worth far more than a line in a notebook. Attaching it to the right equipment matters as much as the description: on a ship, “the cooling pump” means nothing until you have said which one, on which engine, on which circuit.
As soon as the work order is created, the component's history should appear: previous jobs, parts already replaced, observations left by the previous crew. That memory is what stops a diagnosis being repeated six months after it was first made.
Planning: the port call window drives the calendar
This is where the difference with shore-based industry is clearest: you do not plan to stop a main component while under way. A work order that requires an auxiliary engine to be immobilised, a circuit to be opened or a switchboard to be isolated is scheduled against a window: the port call, the anchorage, the dry docking.
Planning on board therefore answers three questions, in order. When will the vessel be in a condition compatible with the job? Is the part on board, or will it be delivered in time at the intended port? Does the crew available in that window hold the required certifications?
The second question wrecks more schedules than any other. Scheduling a job without first confirming that the part is available means opening a work order that will sit blocked and distort every indicator. A useful CMMS links the work order to the onboard inventory and blocks scheduling until the part is confirmed on board or on order with a date. The same logic applies to the preventive maintenance plan, whose due points must be expressed in running hours as much as in calendar dates.
Execution: offline is not an option, it is the whole subject
A job carried out at sea has to be recorded at the moment it is carried out. This is not a matter of convenience, it is the heart of the problem.
A CMMS that needs a satellite link before it will save a line mechanically produces deferred records. The officer scribbles on a scrap of paper, or writes nothing at all, and then reconstructs from memory at the next port call what happened four days earlier. Hours become approximate, part numbers become close rather than correct, observations vanish. The register is still full, but it no longer describes reality.
An experienced auditor spots that kind of register immediately. Twenty work orders closed within the same hour, the day before the visit, with interchangeable comments, tell a very clear story: the entries were made in one block, after the fact. That is precisely the signal that turns a routine check into a detailed examination.
Offline operation must therefore be complete rather than partial: opening a work order, consulting the component's history and documentation, ticking off a task list, consuming a part from the ship's store, adding photographs and closing the job, all of it with no connection whatsoever. Synchronisation happens afterwards, without altering the original time stamps. This deserves to be checked during a demonstration: the time stamp kept must be the one from the job, not the one from the synchronisation.
Execution is also the point at which safety conditions attach themselves to the work order. Electrical isolation, circuit isolation, enclosed space entry permits, hot work: these are not annexes, they are fields of the work order. The link with lockout procedures and crew certifications must be visible on the screen of the person doing the work, not in a binder in the chief's office.
The watch handover: passing on an open work order
This is the case industrial literature never covers, because it does not exist anywhere people go home in the evening leaving the machine shut down.
On board, a work order regularly crosses a change of watch. Stripping down starts during the 8-12, recommissioning will happen during the 12-16, with different people. What has to be handed over is not only progress: it is the physical state left on the installation. Which valves are shut. Which breaker is locked out, and by whom. Which circuit has been drained and not yet refilled. Where the removed part is.
A well-designed digital work order carries this in dedicated fields, updated at every interruption, rather than in a free-text comment at the end of the day. The incoming watch can see within seconds what is still isolated and what remains to be done. This is a safety matter before it is a traceability matter: a valve reopened by someone who did not know a circuit was open is a classic incident.
This handover works alongside the engine room logbook: the logbook records operation, the work order records intervention, and a coherent system avoids capturing the same information twice.
Closing: what separates evidence from a problem
Closing a work order is not ticking “done”: it is producing a record that will be read two years from now by somebody who was not there.
A proper closure holds the real start and finish time stamps, the identity of the person who did the work, what was found and what was done, the parts consumed with their references, the useful photographs, the readings taken and the observations for what comes next. The difference between a good and a bad closure comes down to what is asked for at the moment of entry: a form that requires a counter reading and a part number gets them, a free-text box gets “no defects found”.
Closing also updates everything else: the ship's stock goes down, the component history grows, the next preventive due point is recalculated from actual running hours, and replenishment is triggered if the threshold is crossed.
Analysis: from the vessel to the fleet
Once consolidated ashore, work orders become fleet information. The superintendent can see that the same auxiliary keeps failing across four sister vessels, or that a preventive task is systematically postponed on one ship — a sign that its interval is unrealistic, not that the crew is negligent.
That reading is only possible if vessels record data in the same way. A shared equipment hierarchy and common failure codes are worth more than any dashboard: without them, consolidation simply adds up figures that are not describing the same thing.
Shore and ship: who does what
The “maintenance manager” of shore-based literature does not exist in a shipping company: the function is split across three distinct roles, and a well-designed work order reflects that split.
The technical superintendent, ashore, looks after several vessels. They plan dry dockings, order the parts that cannot be bought locally, consolidate fleet data and prepare audits. They need a comparative view, and the assurance that what they are reading is faithful.
The chief engineer decides on board: what gets done during this port call and what waits for the next one, based on the actual condition of the machinery, the crew available and the parts in the store. They need a workload view by window of opportunity, not a list sorted by date.
The crew executes and documents: it is the watch officers, the petty officers and the engineers who produce the data. Any reporting requirement that costs them more than it gives them back will eventually be worked around, and that is exactly how reconstructed registers come into being. An interface usable on a phone, with gloves on and with no network, is not an ergonomic detail: it is what determines the reliability of the whole system.
The work order as the unit of evidence under ISM Code chapter 10
Chapter 10 of the ISM Code requires the company to establish procedures ensuring that the ship is maintained in conformity with the applicable rules, that inspections are held at appropriate intervals, that non-conformities are reported with their possible cause, that corrective action is taken and that records of all this are kept. Chapter 7 requires documented procedures for key shipboard operations.
In practice, the unit of evidence for those requirements is the work order: it is what shows that a scheduled inspection took place on the scheduled date, that a reported defect led to action, and that the action was carried through by an identified person. A properly closed work order is evidence; empty, backdated or closed without detail, it is a non-conformity waiting to be raised.
That is what the ISM auditor and the port State control inspector look at: not the number of work orders, but their consistency. Do the dates match the logbook? Have the parts declared as consumed actually left stock? Are postponed due dates justified? A CMMS that produces these records with no extra effort does the compliance work at the same time as the maintenance work, as our article on the ISM Code and maintenance explains in detail.
Anatomy of a properly completed work order
The table below sets out, field by field, what each element is there to demonstrate on the day the work order is read back.
| Field | Expected content | What it proves |
|---|---|---|
| Equipment identification | Unique tag of the component, circuit and vessel | That the job concerns the right component and feeds the right history |
| Origin of the work order | Preventive due point, reported defect, corrective action | That detected defects lead to action, as chapter 10 requires |
| Real time stamps | Start and finish date and time, entered as the job happens | That the work took place when it is claimed, rather than being reconstructed in port |
| Operator | Name and rank of the person doing the work, certifications used | That the job was done by a qualified, identifiable person |
| Safety conditions | Isolations applied, valves shut, associated permits | That safety procedures were applied, not merely displayed |
| Task list and check points | Steps ticked off one by one, values measured | That the job was complete rather than partial |
| Parts consumed | Exact reference, quantity, issued from the ship's store | That declared stock matches real stock and that costs are real |
| Photographs | Initial condition, points of interest, final condition | That the finding can be verified rather than taken on trust |
| Observations and follow-up | Defects not yet addressed, parts to order | That outstanding work is recorded and does not depend on one person's memory |
| Counter reading | Running hours of the component at closure | That the next preventive due points are calculated on a real basis |
Paper and digital: what changes in shipboard situations
The table below compares paper and the offline digital work order across the situations that come up most often in the engine room.
| Shipboard situation | Paper work order | Offline digital work order |
|---|---|---|
| Job carried out under way, with no satellite link | Handwritten notes, entry deferred to the port call, details lost | Recorded immediately on mobile, synchronised later without altering time stamps |
| Change of watch during the job | Verbal handover, isolation status rarely written down | Isolations and outstanding work in dedicated fields, readable by the incoming watch |
| Consuming a part from the ship's store | Issue noted in a book, theoretical stock drifting away from reality | Issue recorded at source, ship's stock current, replenishment triggered |
| Looking up a component's history | Binders on board, archives incomplete after a crew change | History available at the machine, including offline |
| Preparing for an ISM audit | Rebuilding files, bulk entries easy to spot | Records time-stamped as work happens, consistent with the logbook |
| Visit by a port State control inspector | Delay in retrieving the evidence for one specific job | Work order retrieved and presented with its photographs and parts consumed |
| Crew change | Knowledge of the installations leaves with the people | Technical memory retained and available to the new crew |
Making the move to digital work on board
A successful transition does not start with deploying an application, it starts with the structure of the data: a clean equipment hierarchy, each component identified once, with a stable tag common to the whole fleet. Without that, no usable history ever builds up.
Next comes deciding what the crew is asked to record. The temptation is to ask for everything, and that is the most common mistake: an over-long form gets half filled in, and half-reliable data is worse than missing data, because people trust it. The value then appears gradually, once the history spans several crew changes.
Conclusion
Digitalising the work order on board is not about replacing a paper form with a form on a screen. It is about producing the record where the job happens — at the machine, at sea, with no network — so that it describes reality rather than the memory people keep of it.
The benefits follow. The crew spends less time copying out and more time working, the chief engineer decides on a reliable picture, the superintendent anticipates orders. And on audit day, compliance is not a reconstruction exercise: it is the consequence of how the year was worked.
To see how these principles translate to your fleet, request a demonstration.
.png){kind=small}
