Compliance Training Matrix for Shipping Companies: Connect Vessel, Shore Organisation and Port

A training matrix connects vessel, shore organisation and port

A shipping company can keep vessel training lists, certificates in a personnel system, and familiarisation records in emails yet still have no shared answer at the crucial moment: who may perform which task today, who must be told before a change, and which evidence is reliable? A compliance training matrix makes those questions operational. It connects role, activity, competence, validity, source, and escalation. The ConformBase shipping companies package is a practical starting point for turning scattered learning evidence into a controllable process.

The matrix does not replace a Safety Management System process, security management, or professional review of individual certificates. It is the operating view that brings those systems together at handovers. During crew changes, charter or route changes, new contractors, and port calls, execution rarely fails because no one has read a rule. It fails because role, learning objective, timing, and approval do not appear in one shared view. That is why a sound matrix starts with decisions rather than a long collection of course names.

Map activities and decision points before courses

For each vessel and shore role, start with recurring activities: watch handover, cargo information, incident reporting, access control, communication with terminal or agent, approval of a deviation, and reporting to the designated person. For every activity, record which role acts, which competence or familiarisation is required, which event triggers it, and how completion is evidenced. This prevents general instruction from being mistaken for authorisation to perform a specialised task. The difference between awareness, competence, authorisation, and actual availability must remain visible.

A resilient data model need not be complicated. One row can hold vessel or fleet, role, activity group, learning requirement, authoritative source, due date, evidence location, reviewer, deputy, and escalation deadline. Add a status for open gaps, but avoid a blanket green state merely because one document exists. A valid certificate may be missing, familiarisation may need renewal, or the person may not be available for the current voyage. The guide to audit-ready training records shows how status, evidence, and accountability can be brought together.

Separate requirements by source so the matrix remains readable

The international frameworks serve different purposes. The ISM Code sits within the SOLAS framework and provides the basis for a safety management system. The ISPS Code concerns the security framework at the interface between ship and port facility. STCW connects minimum standards for training, certification, and watchkeeping with mandatory and recommended parts of the Code. For the matrix, that means not deriving one blanket course from a single rule, but recording the applicable source, competent professional owner, and required evidence for each activity.

National flag-state requirements, classification requirements, customer requirements, and the company’s own management system can also trigger concrete learning or familiarisation needs. Keep those categories separate. A list labelled only mandatory training makes it difficult later to explain whether a gap is legal, contractual, systemic, or operational. That separation also supports management: it sees not merely a percentage but the type of risk and available decision space. The overview of mandatory employee training helps structure learning requirements by role and evidence rather than keyword.

AI-generated

Record the shore organisation as the control point

A matrix limited to crew leaves a crucial gap: many triggers arise ashore. Technical management, crewing, operations, chartering, security, procurement, and IT make decisions that change information or competence needs on board. Therefore, define not merely a course for each shore role but its handover to the vessel. For example, a new digital interface changes access rights. Who checks entitlement, who explains the process, who confirms familiarisation, and who stops use when a gap remains? Without that chain, cyber or security knowledge becomes a slide deck rather than action.

Link roles to concrete control points: a new person on board, new route, changed cargo, new terminal, technical conversion, notable report, or upcoming external inspection. Behind each control point are an owner, a deputy, and a time window. General NIS2 training offers a useful pattern by assigning awareness, reporting route, and accountability, but it does not replace professional assessment of maritime systems. For shipping companies, the matrix must apply that principle to real ship and shore processes. See also: NIS2 training for management and employees.

Test readiness on board rather than file completeness

On board, the moment a person takes over a task matters. Plan three separate status values: evidence exists, familiarisation for this vessel or system is complete, and the person is available and authorised for today’s work. During a crew change, that is more than administration. The incoming officer or specialist needs a clear list of current tasks, open points, and escalation contacts. The outgoing person needs a fixed way to hand over deviations, temporary measures, and training gaps that have not yet been closed.

A short exercise makes the matrix credible. Choose a plausible situation, such as a changed port instruction, a fault in the access system, or an unclear handover of cargo information. Do not ask first whether the course is complete. Ask who detects the issue, who may verify which information, who is informed on board and ashore, and where the decision is documented. The principle mirrors online occupational-safety instruction: learning must be visible in a concrete action and traceable documentation. See also: online occupational-safety instruction and documentation.

AI-generated

Plan port, agents, and contractors as interfaces

The port is not an external appendix to the matrix. Terminal, port facility, agent, pilot organisation, inspector, or maintenance contractor receives information, raises questions, or triggers dates that affect roles on board and ashore. Therefore document not merely external contacts but the concrete handover: which information goes out, which response is expected, who assesses it, and when escalation is required. This makes recurring interfaces trainable without assigning internal responsibility to an outside party.

Preserve the difference between familiarisation and control. A shipping company may inform a contractor about a process and still need to check itself whether an approval, report, or evidence is complete. Define minimum evidence for each interface: instruction received, handover confirmed, open point, accountable owner, and follow-up date. The practical guide to avoiding spreadsheet chaos transfers well to this work because it calls for one clear owner, deadline, and escalation rather than an unreviewable email chain.

Keep evidence so a question can be answered quickly

The value of the matrix appears in a simple question: can this person perform this task on this vessel under today’s conditions? A useful answer needs more than a scan. It points to the role, current assignment, learning or familiarisation evidence, validity, most recent review, and a person who decides when there is doubt. Link documents but do not copy every document into the matrix. A stable link to the system of record, a version indicator, and a review date usually suffice when access rights are secured.

For leaders, use a separate view with a few measures: open gaps by risk category, upcoming dates, unresolved deputies, vessels with incomplete handover, and cases without a timely decision. Avoid rankings that merely put crews under pressure. Measures should trigger resources and decisions, not shame. An escalation is effective when it makes a real gap visible early and names a manageable next step, such as familiarisation before departure, an additional deputy, or restricting a task.

A four-week control rhythm keeps the matrix alive

A good matrix is not created once and then archived. Review changes in people, vessels, systems, routes, and contractors on a short cadence. Also capture learning from exercises, reports, audits, and questions. Every new requirement needs a professional owner, translation into a concrete activity, and a date when effectiveness will be reviewed. The matrix then grows with operations in a controlled way instead of becoming a frantic complete stocktake before every inspection.

Start small: one vessel group, three critical handovers, and the associated shore roles. After a real crew change, test whether answers were quick to find and decisions unambiguous. Only then extend to further activities. Compliance training becomes not a separate administrative project but a reliable working routine between vessel, shore organisation, and port.

Tie learning objectives to the decision

Do not formulate learning objectives as topic labels such as ISM, security, or communication. Instead describe the observable decision: a person recognises an incomplete handover, assigns it to the right process, informs the accountable role, and records the chosen action. Suitable practice formats follow from that. A short scenario, handover list, or role question can be more effective than an extensive presentation. The matrix shows which role the objective applies to and what evidence later confirms application.

Also avoid overloading the same audience with near-identical instruction. For each new need, first test whether an existing familiarisation should be extended, a local process change explained, or a new competence genuinely developed. That decision saves time on board and makes the evidence landscape clearer. What matters is one clear version, an accountable professional owner, and a date for the next review. It then remains traceable which information is actually valid for which activity.

Sources and context

The following primary sources explain the international frameworks referenced above. This article is an operational organisation guide and not legal advice for an individual case.

• IMO: International Safety Management Code
• IMO: International Ship and Port Facility Security Code
• IMO: STCW Convention and Code
• EUR-Lex: Directive 2009/16/EC on port State control

Structure training evidence for vessel and shore organisation