The TMSA Engine Room Audit: What Element 4 Stage 4 Actually Requires

A TMSA engine room audit is what separates a Stage 3 operator from a Stage 4 one on Element 4.

There is a version of Element 4 compliance that looks complete from the office. The planned maintenance system is computerised. Tasks are scheduled and recorded. Defects are logged and tracked. Superintendent visits happen twice a year. Critical equipment is listed, risk assessments are filed, and the Stage 3 KPIs are met across the board.

Then someone boards the vessel and watches the engineering team work.

That is what TMSA Element 4 Stage 4 KPI 4.4.5 is asking for. Not a review of records — an audit conducted by a suitably qualified company representative, on board, while the vessel is on passage, observing engineering practices as they actually occur.

Most operators who self-assess at Stage 3 have not yet put this in place. The Stage 4 KPIs in Element 4 are consistently the last to be met, and 4.4.5 is the one that requires something no system integration or monitoring programme can substitute for: a qualified person present on the vessel while it is working.

What Element 4 covers

Element 4 addresses planned maintenance, defect reporting, critical equipment management, and engineering reliability across the fleet. It runs alongside Element 4A, which deals specifically with critical equipment and systems — identification, maintenance procedures, testing, and performance monitoring.

The element builds across four stages. Stage 1 establishes the foundations: a planned maintenance system covering all equipment and machinery, a defect reporting system, and management review of maintenance status. Stage 2 adds superintendent verification during ship visits, dry-dock planning procedures, and structural inspection of cargo, ballast and void spaces. Stage 3 requires a fully integrated computer-based maintenance system, an optimum spare parts inventory policy, and performance indicators — blackout occurrences, loss of manoeuvrability, outstanding critical maintenance tasks — reviewed by senior management.

By Stage 3, a well-run operator has genuine system depth. The PMS is synchronised between ship and shore. Critical equipment is flagged in the system. Defect reports feed into procurement. Management receives regular status reports.

Stage 4 shifts the question entirely.

What a TMSA Engine Room Audit Requires at Stage 4

The first four Stage 4 KPIs in Element 4 (4.4.1 through 4.4.4) address integration and condition-based monitoring: procurement linked to the maintenance system, deferred repairs tracked automatically into drydock specifications, real-time maintenance status visibility for management, and the use of vibration monitoring, oil analysis, thermal mapping and remote diagnostics to move from time-based to condition-based maintenance.

These are system and data maturity requirements. They demand investment in platform integration and monitoring capability that most operators at Stage 3 have not yet made.

KPI 4.4.5 is different in kind. It does not require a software integration or a new monitoring programme. It requires a person — suitably qualified, experienced, from the company — to board the vessel and conduct a comprehensive engineering audit while the ship is on passage.

The TMSA definition of what that audit must cover is specific. The auditor is expected to review and confirm that engineering practices comply with industry standards and company procedures. To assess the skills and proficiency of the engineering team. To evaluate how the team functions during all sections of a voyage — manoeuvring, cargo operations, unmanned machinery space periods. To verify that junior officers are adequately supervised during critical operations, and that cadets are being trained. To confirm that logs are accurate and record-keeping is adequate. To identify any training needs, whether individual, vessel-specific, or fleet-wide.

The audit is followed by a debrief to the engineering team and a written report with corrective actions assigned, verified and closed within a specified period. All vessels are audited at intervals not exceeding one year.

Why the audit must be conducted at sea

TMSA 4.4.5 stipulates that the audit is conducted while on passage. That is not an administrative detail — it reflects what the audit is actually trying to establish.

A port visit can verify that records exist and equipment is present. It cannot observe an engineering team functioning as a team, because in port most systems are on standby or shut down. The main engine is not running. UMS operations are not active. The watch is reduced. The decisions that reveal how an engineering team actually operates — how they respond to alarms, how they manage critical systems under load, how they communicate during manoeuvring — are not available for observation.

The best practice guidance under 4.4.5 makes the scope explicit: the audit must evaluate the team across all sections of the voyage, including manoeuvring, operations when unmanned, and cargo operations. These are conditions that only exist when the vessel is working. An audit conducted only in port satisfies none of them.

The core purpose of 4.4.5 is to verify that what the SMS describes is what the engineering team actually does — under the conditions where it matters. That verification requires the auditor to be present when the team is operating, not standing by.

What a records review cannot tell you

A PMS entry that reads checked and found satisfactory is, in isolation, a statement about nothing.

It does not describe what was checked. It does not record the condition found. It gives no indication of whether the person who made the entry understood what they were looking at, or whether the task was completed to the manufacturer’s standard, or whether the equipment is performing within acceptable parameters.

This is not a criticism of the officer who wrote it. It reflects what happens when a maintenance system is used primarily as a compliance log rather than a technical record. The entry exists. The box is ticked. The audit trail is formally intact.

What it does not provide is the operational assurance that 4.4.5 is designed to generate — confirmation, by a qualified person observing directly, that engineering practices on board are sound.

A records review conducted from the office can verify that entries have been made. It cannot verify what the entries mean. It cannot assess whether the engineering team understands the equipment they are maintaining, whether watch practices are disciplined, whether the culture in the engine room reflects the standards the company believes it has embedded.

That requires presence.

When paperwork and practice separate

In a well-functioning engineering operation, the maintenance record and the maintenance work are part of the same process. The record captures what was done, what was found, what decisions were made. It is a technical document that feeds the next maintenance cycle and gives the shore team genuine visibility of equipment condition.

In practice, the relationship between the two can drift. The work gets done — competently, sometimes excellently — and then the record gets completed afterwards, as a separate task, to satisfy a requirement. The entry exists because it has to exist. It is not written as a tool for the next person who opens the system; it is written to close the loop on a compliance obligation.

This is not a failure of individuals. It is what happens when a maintenance system is experienced primarily as an administrative burden rather than an operational resource. The engineering team is focused on the machinery. The paperwork is something that happens around the machinery.

An engineering audit conducted under 4.4.5 can identify where this separation has occurred — not to assign fault, but because a qualified auditor observing work in progress will see the relationship between what is being done and how it is being recorded. That gap, where it exists, is information the shore team cannot extract from the system itself.

Why physical attendance is the point

The navigational audit asks what the bridge team actually does under real operating conditions. The engineering audit asks the same question of the engine room.

The difference is that engineering practice is harder to observe remotely than navigational practice. A VDR captures audio, radar, ECDIS inputs and helm movements. The engine room generates data — alarm histories, running parameters, PMS records — but that data reflects what was logged, not what was done or how decisions were made. The only way to assess whether the engineering team is operating in accordance with company procedures is to be there when they are operating.

For operators pursuing Stage 4 on Element 4, the gap is rarely the paperwork. The systems are in place. The procedures exist. What is missing is the assurance cycle that closes the loop between what the SMS says and what the engine room does — and that cycle requires a qualified person on board, at sea, watching the team work.

What the audit produces

A properly conducted 4.4.5 engineering audit delivers three things that a desktop review cannot.

First, it establishes the actual competency baseline of the engineering team — not the qualification records, but the operational reality. Where the team is strong, that is documented and can be used for benchmarking across the fleet. Where gaps exist, training needs are identified at the individual, vessel, and fleet level before they become deficiencies or inspection findings.

Second, it provides genuine evidence for the TMSA self-assessment. A Stage 4 KPI supported only by a self-assessment entry is a vulnerability in any external review. An audit report with a debrief record, corrective actions, and close-out evidence is a different proposition entirely.

Third — and most practically — it gives shore management a verified picture of engineering standards that no PMS dashboard can replicate. The maintenance system shows what was recorded. The engineering audit shows what is actually happening.

A note on Element 4A

Element 4A sits alongside Element 4 and deals specifically with critical equipment and systems. Its Stage 1 and Stage 2 KPIs require that critical equipment is identified through risk assessment, listed in the PMS, maintained under approved procedures with shore management notification when taken out of service, and tested and recorded to defined standards.

Stage 3 adds the requirement for designated personnel with the skills and competencies to perform maintenance and repair on critical equipment, and for performance data to be compared against manufacturer’s baseline criteria.

Stage 4 of 4A (KPI 4A.4.1) requires that reliability and performance of critical equipment and associated alarms is monitored and analysed continuously — using condition-based monitoring, trend data, fleet experience, and predictive maintenance tools.

The engineering audit required under 4.4.5 is the mechanism through which shore management can verify that 4A requirements are being met in practice — that the procedures exist, that designated personnel understand them, and that critical equipment is being maintained to the standard the SMS describes.

If your fleet is working towards Stage 4 on Element 4, or if a TMSA review has identified 4.4.5 as an open KPI, we conduct engineering audits on board, at sea, with a written report and corrective action tracking.

Get in touch →