An audit often becomes a rush to collect certificates, service reports and signed checklists. From the technical department's side, that is usually the wrong starting point. The difficult questions begin when an auditor selects one system and asks the crew to show how it is maintained, what happened after the last defect and whether the physical installation still matches the records.
A well-prepared yacht should be able to produce that evidence without building a special version of reality for audit day. The aim is not a perfect folder. It is a traceable account of how the yacht controls its equipment, work and known problems.
- How to distinguish an ISM audit, statutory or class survey, Port State Control inspection and internal management review.
- Which technical evidence should be current, retrievable and consistent with the yacht's physical condition.
- How to prove the history of one critical system from maintenance through defect close-out.
- Which recordkeeping weaknesses commonly lead to deeper questions.
- How Captains and management can support readiness without encouraging cosmetic close-outs.
The word audit is often used loosely onboard. Before assembling evidence, confirm who is attending, their authority, the scope and the standards or company procedures they will use.
Review type / What the technical team should expect
- Insurer or specialist review
- Evidence targeted at the agreed survey scope, such as machinery condition, fire risk, electrical safety, cyber controls or loss-prevention measures.
- Internal company or management audit
- Assurance that company procedures, owner requirements and assigned responsibilities are being followed between formal external visits.
- Port State Control inspection
- Initial checks of certificates, documents, ship condition and crew operation, with the possibility of a more detailed inspection where clear grounds exist.
- Flag or class survey
- Examination and testing against the applicable statutory, class or yacht-code requirements, with attention to equipment condition, approved arrangements, certificates and survey history.
- ISM or SMS audit
- Evidence that the yacht's safety-management procedures are implemented in practice, including maintenance, reporting, emergency preparedness, internal audits and corrective-action follow-up.
These activities overlap, but they are not interchangeable. IMO's ISM guidance describes audits as verification that the safety management system is implemented and functioning effectively, supported by objective evidence. HSSC surveys and Port State Control follow different mandates. The yacht should prepare to the issued scope rather than assuming that one general evidence pack answers every review. [1][2][3][4]
An auditor rarely needs every technical record at once. A more useful test is whether the crew can follow one requirement through the vessel's actual operation.
For a selected item, the evidence chain should answer:
- What is the equipment and where is it identified?
- What procedure, drawing or maintenance requirement applies?
- When was it last inspected, serviced or tested?
- What result was recorded rather than merely signed off?
- Were defects, alarms or temporary arrangements raised?
- Who assessed the operational risk and authorised any deferral?
- What proves that corrective action worked and the item was closed?
This approach quickly exposes records that look complete but do not describe the vessel. A service report with the wrong serial number, a planned-maintenance task with no measurement, or a closed defect with no operational test is weak evidence even when the document is signed.
The technical lead should know where each evidence group is held, who owns it and how it can be retrieved if the yacht's internet connection or cloud platform is unavailable.
Evidence area / Minimum readiness test
- Inspection history
- Previous audit, flag, class, Port State Control and internal findings can be traced to completed or managed corrective actions.
- Changes and configuration
- Modifications, software updates, bypasses and temporary arrangements are linked to approval, testing, current drawings and recovery information.
- Emergency readiness
- Drill and test records show what was exercised, what failed, who participated and what was changed afterwards.
- Controlled technical work
- Recent permits, risk assessments, isolation records and contractor work packs show how hazardous work was authorised and handed back.
- Defects and corrective actions
- Open defects have an owner, operational assessment, temporary controls and target date. Closed defects include proof of repair and verification.
- Maintenance and testing
- PMS tasks show dates, results, readings, responsible persons and attached service or calibration evidence where required. Overdue work and deferrals are visible.
- Vessel and equipment baseline
- Current equipment register, relevant approved drawings, manuals and certificate index agree with the installation and equipment identity.
For UK-flagged vessels within the relevant scope, MCA MGN 708(M) gives a useful current example. It says that a general inspection will normally accompany an SMC audit, that previous inspection and Port State Control findings should be available, and that an emergency drill is normally expected. Other flags and recognised organisations may use different arrangements, so this should not be applied universally. [6]
Before the audit, choose a small sample of systems and test the evidence chain yourself. An emergency generator, fire pump, steering-related supply, fixed fire-detection system or critical UPS can reveal more about readiness than reviewing hundreds of completed PMS jobs.
Take the emergency generator as an example. The technical team should be able to find its identity, drawing and maintenance schedule. The latest functional test should show what was actually observed: start method, voltage, frequency, alarms and any load or changeover result required by the vessel's procedure. If a jacket-water heater failed during the test, the defect record should show the interim control, repair and subsequent verification.
Then walk to the equipment. Labels, valves, local instructions and general condition should agree with the records. Finally, ask the duty engineer to explain the response to a failed automatic start. This connects documentation, physical condition and crew familiarity instead of treating them as separate audit folders.
Seven days before
Confirm the audit scope and responsible onboard contact. Review open findings, overdue critical maintenance, temporary bypasses and expiring certificates with the Captain and management company. Do not hide a legitimate open defect; make sure it has a current assessment, control and action date.
Five days before
Sample several evidence chains. Use equipment from different technical areas and include at least one recent defect. Check that electronic links work, attachments open and records can be retrieved offline where necessary.
Three days before
Carry out a physical walkdown. Look for mismatched labels, inaccessible emergency equipment, damaged guards, temporary cabling, disabled alarms and changes that have not reached the drawings or PMS.
Two days before
Brief the technical team on the scope and practical arrangements. Crew should answer from their own knowledge and use the controlled records; they should not be given scripted answers. Confirm who will retrieve evidence and who can authorise tests or demonstrations.
One day before
Freeze unnecessary changes. Check the audit workspace, safe access and any test equipment that may be needed. Record the current status of systems that are out of service or under maintenance.
After the audit
Log every observation, finding and requested follow-up. Assign owners and dates before people disperse. Keep the evidence supplied during the audit with the resulting close-out record so the next review does not restart from memory.
- A signed PMS task contains no result, reading or test condition.
- A certificate or service report cannot be matched to the installed serial number.
- A recurring alarm is accepted routinely but has no defect or investigation record.
- Temporary cables, bypasses or software changes are absent from the change log.
- A critical task is overdue without a documented assessment or authorised deferral.
- Contractor work has a report but no yacht-side acceptance or functional test.
- Drill records show attendance but no scenario, result, debrief or follow-up.
- The only person who can find the records is off the vessel.
- Emergency procedures or certificate verification links are unavailable during a network outage.
Use one technical coordinator so requests are logged and evidence is not supplied in conflicting versions. Answer the question asked, then provide the supporting record. If the crew does not know, it is better to retrieve the controlled information than guess.
Do not rush to edit a record while it is being examined. An identified error should be acknowledged and handled through the vessel's correction or non-conformity process. Quietly replacing evidence during the review damages confidence in the wider system.
The IMO Port State Control framework is a useful reminder of why consistency matters: where the condition of the ship or equipment does not correspond with the certificates, or the crew are not familiar with essential procedures, a more detailed inspection may follow. [4]
Use the related YachtByte register to prepare a controlled index of the audit scope, evidence owner, storage location, sample status and open gaps. Its system-traceability page is designed to test one selected item from requirement through maintenance, defect control and verified close-out.
The register is a preparation and handover tool. It should point to controlled vessel records rather than becoming another uncontrolled copy of them.
The required evidence depends on the yacht's flag, class, certification, size, use and the scope issued by the auditor or surveyor. Private, commercial and passenger yachts can have materially different requirements.
Use the vessel's SMS, survey status, applicable yacht code and instructions from flag, class or the recognised organisation as the controlling basis. This article is an evidence-readiness method, not a vessel-specific compliance checklist.