The marine superintendent is the only role in shipping accountable for assets they almost never see. A technical superintendent typically manages a group of around four to five vessels depending on company structure, fleet size and vessel type, and acts as the link between ship and shore office. One major operator's job description puts the scale plainly: a ship superintendent is responsible for an estimated 120 million dollars in assets or equivalent programme management, with independent expense approval up to 10 million dollars a year at their own discretion for maintenance, engineering, spare parts and repairs. And the same role visits each vessel perhaps two to four times a year to conduct audits, oversee critical maintenance and support the ship's command. Work the arithmetic and the picture is stark. For roughly three hundred and fifty days a year per ship, everything a superintendent knows about a vessel is secondhand — assembled from emails, noon reports, a phone call at an awkward hour, a PMS they may or may not trust, and whatever the chief engineer decided was worth mentioning. The decisions are large. The direct observation is not. Start a free trial of Marine Inspection and close the gap between them.
Accountable for
Able to observe directly
Four to five vessels, operating across time zones
Two to four visits per vessel per year
An asset base reported at around 120 million dollars
A handful of vessel-days of physical presence annually
Discretionary spend authority reaching 10 million dollars a year
Whatever the last email, report or phone call contained
Technical condition, budget, and the appraisal of senior officers
Data that arrives when someone chooses to send it
The gap between those two columns is the entire job. Everything a superintendent does is an attempt to reason accurately about a machine they are not standing next to, using information they did not gather, on a schedule they do not control.
Three Hundred and Fifty Days of Inference
Put the visit schedule on a calendar and the proportion becomes uncomfortable, particularly since the visit days themselves are largely consumed by scheduled activity rather than by looking around. Book a Marine Inspection demo and see what a vessel looks like on the other three hundred and fifty.
Observed
Inferred
Days you are aboard: audits conducted, critical maintenance overseen, the ship's command supported
Days you are not: the vessel operates, wears, develops defects and closes them, and reports what it reports
The visits are not free-form observation either. Superintendent visits are scheduled to conduct audits, oversee critical maintenance tasks and support the ship's command — which means the rare days of direct presence are already spoken for. Wandering the engine room forming an impression is what is left over, if anything is.
It Is Not One Job. It Is Three.
The reason a superintendent's desk carries five browser tabs is not disorganisation. It is that the role genuinely spans three distinct disciplines, each with its own information source, and none of those sources were designed to speak to the others. Sign up for Marine Inspection and collapse the technical column into one place.
Technical
Reviewing all planned and repair work scopes reported. Advising the chief engineer on technical matters. Managing the supply of materials, consumables and spare parts. Appointing specialists. Overseeing dry-docking, major repairs and upgrades.
Lives in: the PMS, defect emails, class portals, maker correspondence
Commercial
Devising, agreeing and monitoring budgets. Continuous preparation of maintenance and repair periods and their budgets. Liaising directly with the vessel owner. Responding to charter, technical and operational questions.
Lives in: spreadsheets, the accounting system, the owner's inbox
People
Briefing, debriefing and appraising masters, chief engineers and other senior officers. Sometimes the management and hire of ship's staff. Working closely with operations superintendents and advising the HSE and operations departments.
Lives in: crewing systems, appraisal forms, memory
PMS
Class portal
Vetting database
Budget sheet
Defect tracker
Crewing
Email
Seven sources, none of which agrees with any other about what is outstanding on a given vessel. The reconciliation happens in one place only — a superintendent's head, usually on a Monday morning, usually just before somebody asks a question that requires the answer to be right.
How long would it take you, right now, to say how many open defects sit across your vessels?
Not approximately. Exactly, by vessel, with the oldest one named and the reason it is still open. If that question takes more than a minute, the problem is not effort or competence — it is that the answer is distributed across systems that were never built to be added together.
What Has to Be Visible Every Day
Below is the actual daily requirement, separated from the things that merely feel urgent. The test for each row is whether not knowing it could cost money or capability within a week. Schedule a walkthrough and check how many of these you could answer without opening a second window.
Table 1: The Superintendent's Daily View
| What you need to see | Why it cannot wait | Where it usually lives | The question it answers |
|---|---|---|---|
| Open defects by vessel | Age of the oldest open item predicts the next unpleasant surprise | Email threads and a defect spreadsheet per vessel | Which ship is quietly accumulating a problem? |
| Overdue planned jobs | Overdue counts are the first thing an auditor filters on | The PMS, if the crew have been keeping it current | Is the maintenance system being operated or populated? |
| Certificate and survey windows | An expiry discovered late becomes a deviation or a detention | A certificate spreadsheet separate from everything else | What falls due in the next ninety days across the fleet? |
| Open inspection findings | Reviewing observations and tracking them to close-out is explicitly the role | Inspection reports as PDFs, actions chased by email | What will the next inspector find that the last one already told us? |
| Critical spares position | A part not aboard converts a small defect into a long one | Stock records nobody has reconciled to a shelf recently | Can this ship fix its own problem, or is it waiting on us? |
| Budget consumed against plan | Discretionary authority is only useful if you know what is left | The accounting system, one month behind | Am I approving this repair against a real number? |
| Docking horizon | Specification quality depends on a year of accumulated findings | A folder, a calendar entry, and recollection | What am I about to have to write a specification from? |
| Running hours against intervals | Determines what genuinely falls due versus what looks due | Reported monthly, entered manually, trusted variably | Is the overhaul actually due or is the counter wrong? |
| Who did what | Attribution is what makes a record evidence rather than a claim | Frequently nowhere | Can I defend this if somebody asks in six months? |
One view. Every vessel. Updated by the people doing the work.
The Docking Specification Is Written From Three Places at Once
Planning for a special survey docking begins twelve to eighteen months in advance, and the repair specification is compiled from three distinct sources. Whether those three merge cleanly determines the quality of a document that a shipyard will price and a fleet will live with. Start a free trial and let two of the three assemble themselves.
Source one
PMS data
What the planned maintenance system says is outstanding, deferred or approaching. Only as good as the discipline with which crews have maintained it across the preceding cycle.
Source two
Superintendent inspections
What has been observed during those two to four visits a year, plus whatever was reported in between. Frequently the richest source and the one least likely to exist in a structured form.
Source three
Class survey requirements
What the society requires at this survey, including any conditions of class and any items whose scope has expanded because of previous findings.
Becomes: the repair specification
Sent to a shortlist of suitable shipyards for competitive tendering, with the final yard chosen on price, quality, available docking slots and previous experience with similar vessel types. In 2026 these projects are frequently compounded by major retrofits — ballast water treatment system installation, or energy-saving technology fitted to improve a vessel's carbon intensity rating — which raises the cost of a specification that turns out to be incomplete.
Anything missing from the specification arrives later as a change order at yard rates, or does not get done and carries into the next cycle. Two of the three input streams can be structured so they compile themselves. The third — what the society requires — was never going to be automatic, but at least it can be the only part you assemble by hand.
Close-Out Is a Tracking Problem Disguised as a Technical One
Reviewing inspection observations and deficiencies and working with the vessel and operations to track them through to close-out appears explicitly in superintendent job descriptions. It is also the part of the role most likely to be running on a spreadsheet, because it is administrative rather than engineering work. Book a walkthrough and see findings become tracked actions in one step.
Stage 1
A finding is raised
By a vetting inspector, a Port State Control officer, a class surveyor, an internal auditor or the superintendent's own visit. It arrives as a report, usually a PDF, usually by email, usually to more than one person.
Stage 2
It becomes an action, or it does not
This is where the process fails. A finding that becomes an assigned task with an owner, a deadline and a required evidence type survives. A finding that stays inside the report is remembered for a fortnight and then is not.
Stage 3
The work happens
Frequently it does happen. Crews fix things. The failure is rarely the repair — it is that the repair is not connected back to the finding that prompted it, so nothing demonstrates closure.
Stage 4
Evidence is attached
A photograph, a measured value, a signature, a date. Without it the close-out is an assertion, and the next inspector who checks whether previous findings were remediated finds an assertion rather than a record.
Stage 5
The next inspection reads it
Which is the entire point. An open finding from the last visit is visible at the next one and carries the added weight of having been known about. Closure with evidence is the difference between arriving clean and arriving with a history someone else wrote for you.
The Trust Problem With the Data You Already Have
Most superintendents already have a planned maintenance system. The reason it does not solve the visibility problem is worth stating directly, because it determines whether replacing it helps. Start a free trial and test whether the capture problem or the reporting problem is yours.
The symptom
A superintendent looks at the PMS and does not quite believe it. Completion rates look plausible, overdue counts look manageable, and yet the vessel produces surprises that a well-maintained system should have predicted.
The usual diagnosis
That the system is wrong, or that reporting is inadequate, which leads to a search for better dashboards. Reporting is rarely the actual constraint, and better presentation of unreliable data produces confident wrong answers rather than useful ones.
The actual cause
Capture. If a job is closed at a terminal in the ship's office at the end of a watch rather than at the machine when the work was done, then the completion time is approximate, the measured value is remembered, and the condition found is a summary. The system is not lying. It is faithfully recording a reconstruction.
What follows from that
A superintendent's confidence in fleet data is bounded by where the crew record it. Any evaluation that focuses on shore-side reporting features and does not test what closing a job looks like on a phone in a machinery space is examining the wrong end of the problem.
Evaluating a Platform From the Superintendent's Chair
Vendors demonstrate to fleet managers and IT departments. These are the questions the person who actually has to use it every morning should ask. Schedule a demo and insist on driving it yourself rather than watching.
Table 2: Buyer Questions for Marine Superintendents
| Area | The Question | A Real Answer | What Should Worry You |
|---|---|---|---|
| The one-minute test | Can I see open defects across all my vessels in under a minute? | Demonstrated on your own data, timed, from a cold start | A dashboard that requires configuration before it answers |
| Capture point | Where does the crew actually close a job? | At the machine, on a phone, offline, with a measured value | At a terminal in the ship's office, which is the current problem |
| Finding to action | Does an inspection finding become an assigned task in one step? | Conversion demonstrated live with owner, deadline and evidence type | Findings imported as documents with actions tracked separately |
| Visit preparation | Can I walk aboard already knowing what to look at? | A pre-visit view of open items, overdue jobs and recent findings by vessel | Preparation meaning reading through months of email |
| Docking assembly | Does the repair specification build from the year's records? | An exportable list with evidence attached, filtered to docking work | A specification written from memory twelve months out |
| Cross-vessel comparison | Can I see the same fault recurring across my ships? | Findings comparable across the vessels I manage, not only per hull | Records organised strictly per vessel with no fleet view |
| Attribution | Does every completion carry a name and a date? | Named individuals on every record, retrievable months later | Completion by rank or department rather than by person |
| Time zones | Does it work when a vessel wants me at three in the morning? | A mobile view that answers the question without opening a laptop | A desktop application with a mobile afterthought |
| Handover | If I move to another fleet, what does my successor inherit? | A structured record that holds independently of who built it | A configuration and a set of conventions only I understand |
2026 SUPERINTENDENT REALITY
The figures here come from job descriptions and industry commentary, not from a survey. Vessel allocations of around four to five per superintendent, visit frequencies of two to four times a year, and the asset and approval values cited are drawn from published role descriptions at individual operators. They vary considerably by company, vessel type and trade — treat them as illustrative of the shape of the role rather than as benchmarks. The role definition varies by title. Technical superintendent, marine superintendent, ship superintendent and fleet superintendent overlap heavily and are used differently between companies, with some splitting technical from operational responsibilities and others combining them. Dry-docking timelines have lengthened for retrofit reasons. Planning beginning twelve to eighteen months ahead is now frequently compounded by ballast water treatment installation and energy efficiency retrofits, which extends both specification complexity and yard slot competition. Nothing here removes the statutory obligations. ISM Code Element 10 and the applicable class and flag requirements sit underneath every system decision described above.
Frequently Asked Questions
How many vessels does a technical superintendent typically manage?
Commonly around four to five, though it varies with company structure, fleet size and vessel type, and some superintendents carry three while others carry more. The role acts as the link between ship and shore office, covering technical and operational oversight, budget preparation and monitoring, owner liaison, and the briefing, debriefing and appraisal of masters and chief engineers. One large operator's published description gives a sense of scale: responsibility for an estimated 120 million dollars in assets or equivalent programme management, with independent expense approval up to 10 million dollars a year for maintenance, engineering, spares and repairs.
How often do superintendents actually visit their ships?
Typically two to four times a year per vessel, with visits used to conduct audits, oversee critical maintenance tasks and support the ship's command. That is the structural difficulty at the centre of the role: for the overwhelming majority of the year, a superintendent's understanding of a vessel is assembled from reports, correspondence and system data rather than from observation. It also means the rare days aboard are largely committed to scheduled activity, so unstructured time to walk the ship and form an independent impression is whatever is left over after the planned work is done.
Why do superintendents end up working across so many systems?
Because the role genuinely spans three disciplines with separate information sources. The technical side lives in the planned maintenance system, defect correspondence, class portals and maker documentation. The commercial side lives in budget spreadsheets, the accounting system and the owner's inbox. The people side lives in crewing systems, appraisal forms and memory. None of those were designed to reconcile with the others, so the reconciliation happens in the superintendent's head. Consolidating the technical column into one place does not solve everything, but it is the largest single reduction available.
How far ahead should dry-docking planning start?
Twelve to eighteen months in advance for a special survey docking. The repair specification is compiled from three sources: planned maintenance system data, superintendent inspections, and upcoming class survey requirements. It then goes to a shortlist of suitable shipyards for competitive tendering, with the yard chosen on price, quality, available docking slots and previous experience with similar vessel types. In 2026 these projects are frequently compounded by major retrofits such as ballast water treatment system installation or energy-saving technology to improve carbon intensity ratings, which makes an incomplete specification considerably more expensive than it used to be.
We already have a PMS. Why is fleet visibility still poor?
Usually because the constraint is capture rather than reporting, and better dashboards over unreliable data produce confident wrong answers. If a job is closed at a terminal in the ship's office at the end of a watch rather than at the machine when the work was done, the completion time is approximate, the measured value is remembered and the condition found is a summary. The system is faithfully recording a reconstruction. Any evaluation that examines shore-side reporting features without testing what closing a job looks like on a phone in a machinery space is looking at the wrong end of the problem.
What is the single highest-value change a superintendent can make?
Converting inspection findings into assigned actions with owners, deadlines and required evidence at the moment the report arrives. Reviewing observations and tracking them through to close-out is explicitly part of the role, and it is also the part most often running on a spreadsheet because it is administrative rather than engineering work. The repair usually happens — crews fix things. What fails is the connection between the repair and the finding that prompted it, so nothing demonstrates closure. The next inspector then finds an assertion where a record should be, and an open item from the last visit carries added weight at the next.
You Cannot Be Aboard. You Can Be Informed.
Open defects and overdue jobs across every vessel you manage in one view. Certificate and survey windows escalating before they matter. Inspection findings converted into assigned actions with evidence at close-out. A docking specification assembling itself from a year of structured records rather than from memory. And a capture point on the device the crew already carry, so what you are looking at is what actually happened rather than what somebody remembered afterwards.
