Frequently Asked Questions

Question 1

What types of vessels does Vaayuvent Maritime Assurance work with?

Accepted Answer

We work across vessel types including tankers (crude, product, chemical, and LPG), bulk carriers, container vessels, and general cargo ships. Our auditors hold relevant endorsements and operational experience for the vessel types they audit. If you have a specific vessel type or trade, contact us to confirm auditor availability and relevant experience.

Question 2

Are your auditors flag state approved?

Accepted Answer

Our auditors hold ISM and ISPS auditor qualifications and carry the relevant STCW certificates and endorsements for the vessel types they audit. Flag state approval requirements vary by flag administration. We are happy to provide auditor credentials and qualifications for review prior to engagement — contact us with your flag state and we will confirm suitability.

Question 3

Do you work with ship management companies as well as shipowners?

Accepted Answer

Yes. We work with both shipowners and ship management companies. For ship management companies operating fleets under management, we can scope fleet-wide audit programmes and provide consolidated reporting across multiple vessels. Our engagement terms are structured to suit both single-vessel and multi-vessel arrangements.

Question 4

What flag states do you have experience with?

Accepted Answer

We have conducted audits on vessels registered under more than 25 flag states, including Panama, Marshall Islands, Liberia, Bahamas, Malta, Cyprus, and Indian flag. Our auditors are familiar with the specific SMS documentation and certification requirements of the major open registries as well as Indian flag requirements under the Directorate General of Shipping.

Question 5

How do I schedule an audit or engagement?

Accepted Answer

Contact us through the enquiry form on our Contact page or directly by phone or email. Provide the vessel name, vessel type, flag state, the service you require, and your preferred date range or port of call. We will confirm auditor availability and revert with a formal scope and fee proposal within 48 hours of receiving your enquiry.

Question 6

How much advance notice do you need to mobilise an auditor?

Accepted Answer

For port-based audits and inspections, we typically require a minimum of five working days' notice to confirm auditor availability, arrange travel, and issue the engagement documentation. For urgent mobilisations, contact us directly — we will advise on availability and any additional mobilisation requirements. Remote Navigation Audits can generally be initiated within 48 hours of receiving the required vessel data.

Question 7

Can audits be conducted at any port, or only in India?

Accepted Answer

Our auditors can mobilise to ports across India and internationally. Mobilisation costs for international ports are quoted separately based on the port of call and auditor availability. For vessels trading in Indian ports — including major ports such as Mumbai, Chennai, Visakhapatnam, Paradip, and Haldia — we can typically mobilise at short notice.

Question 8

What happens if the vessel's schedule changes after an audit is confirmed?

Accepted Answer

We understand that vessel schedules are subject to change. If a confirmed audit needs to be rescheduled, notify us as early as possible. We will work with you to identify an alternative date. Our engagement terms set out the conditions for rescheduling and any applicable charges for late cancellations — these are provided with the formal scope and fee proposal.

Question 9

How long does a typical ISM/ISPS/MLC audit take?

Accepted Answer

A combined ISM, ISPS, and MLC audit on a single vessel typically takes one full working day on board — approximately eight to ten hours. The duration depends on the vessel's size, the number of crew, and the scope of the audit. Vessels with a large number of outstanding non-conformities or complex SMS documentation may require additional time. We confirm the expected duration in the engagement scope.

Question 10

When will I receive the audit report after the vessel visit?

Accepted Answer

We issue the draft audit report within five working days of completing the vessel visit. The report includes all non-conformities, observations, and corrective action recommendations referenced to the applicable convention and code requirements. Following your review of the draft, we issue the final report within two working days of receiving your comments.

Question 11

How long does a SIRE 2.0 pre-inspection assessment take?

Accepted Answer

A SIRE 2.0 pre-inspection assessment typically takes one to one and a half days on board, depending on vessel type and the scope of the assessment. The assessment covers the full SIRE 2.0 question framework relevant to the vessel type, including crew competency evaluation, documentation review, and practical observations. The pre-assessment report is issued within five working days of the vessel visit.

Question 12

How long does a Remote Navigation Audit take to complete?

Accepted Answer

Once we receive the required vessel data — VDR records, ECDIS track exports, passage plans, bridge logs, and rest hour records — a Remote Navigation Audit is typically completed within five to seven working days. The timeline depends on the number of passages under review and the volume of VDR data. We confirm the expected completion date when we acknowledge receipt of the data package.

Question 13

What is a Remote Navigation Audit and how does it differ from a Dynamic Navigation Audit?

Accepted Answer

A Remote Navigation Audit is a shore-based review of navigational performance using vessel data — VDR records, ECDIS track exports, passage plans, bridge logs, and rest hour records — without an auditor boarding the vessel. A Dynamic Navigation Audit is conducted on board while the vessel is underway, allowing the auditor to observe bridge team behaviour in real time. The remote format is suited to fleet-wide monitoring, post-incident review, and situations where vessel schedule or trading area makes a physical audit impractical. The dynamic format provides a more direct assessment of bridge team behaviour under operational conditions.

Question 14

What data does the vessel need to provide for a Remote Navigation Audit?

Accepted Answer

The standard data package for a Remote Navigation Audit includes: VDR or S-VDR data for the passages under review (exported in the manufacturer's standard format), ECDIS track exports for the same passages, the passage plans used for those voyages, bridge log entries covering the passage periods, and rest hour records for watchkeeping officers for the relevant period. We provide a data request checklist when the engagement is confirmed, and can advise on VDR export procedures for the specific VDR model fitted to the vessel.

Question 15

How many passages are reviewed in a standard Remote Navigation Audit?

Accepted Answer

A standard Remote Navigation Audit covers three to five passages, selected to provide a representative sample of the vessel's navigational operations — typically including at least one coastal passage, one ocean passage, and one port approach or departure. If you have a specific passage or incident you want reviewed, we can scope the audit around that passage. The number of passages and the selection criteria are agreed at the time of engagement.

Question 16

Is a Remote Navigation Audit accepted by vetting inspectors and flag states?

Accepted Answer

A Remote Navigation Audit is an internal assurance tool — it is not a substitute for a flag state audit or a SIRE vetting inspection. Its primary purpose is to identify navigational performance gaps and rest hour compliance issues before they are identified by an external inspector. The findings and corrective actions from a Remote Navigation Audit can be documented in the vessel's non-conformity management system as evidence of proactive safety management, which is viewed positively in ISM audits and SIRE 2.0 vettings.

Question 17

What should the vessel prepare before an ISM/ISPS/MLC audit?

Accepted Answer

No special preparation is required — the audit is designed to assess the vessel as it operates, not as it presents for inspection. Ensure that the SMS documentation is accessible and current, that the non-conformity register is available for review, and that the Master and senior officers are available for the opening meeting. We will provide a pre-audit information request covering the documents we will review, which allows the vessel to have the relevant records ready without disrupting normal operations.

Question 18

What is the difference between a non-conformity and an observation in your audit reports?

Accepted Answer

A non-conformity is a finding where objective evidence confirms that a specific requirement of the ISM Code, ISPS Code, MLC 2006, or the company's own SMS is not being met. An observation is a finding that does not constitute a non-conformity but indicates a potential weakness or area for improvement. Both are included in the audit report with corrective action recommendations. Non-conformities are classified as major or minor based on the severity and potential safety impact of the finding.

Question 19

Can you assist with closing non-conformities identified in a previous audit?

Accepted Answer

Yes. We can review the corrective actions taken in response to previous non-conformities and assess whether the root cause has been addressed effectively. This is particularly useful before a flag state renewal audit or a SIRE vetting, where the inspector will review the non-conformity history and the effectiveness of corrective actions. Contact us with the previous audit report and we will advise on the most efficient approach.

Question 20

How is SIRE 2.0 different from the previous SIRE framework?

Accepted Answer

SIRE 2.0 is a fundamentally different inspection framework. The previous SIRE framework was primarily documentation-based — inspectors verified that records existed and procedures were documented. SIRE 2.0 is competency-based and evidence-driven: inspectors assess whether crew can actually perform the functions their certificates certify, using structured questioning aligned to OCIMF's competency framework. The inspection is also conducted using a tablet-based system that generates questions dynamically based on vessel type and previous inspection history, making it less predictable than the previous framework.

Question 21

How far in advance of a SIRE vetting should we conduct a pre-assessment?

Accepted Answer

We recommend conducting the pre-SIRE assessment at least four to six weeks before the anticipated vetting date. This allows sufficient time to address the findings identified in the pre-assessment — particularly crew competency gaps, which require structured training and practice rather than a quick documentation fix. If the vetting date is less than four weeks away, contact us and we will advise on the most effective use of the available time.

Question 22

Does the pre-SIRE assessment cover all vessel types?

Accepted Answer

Our SIRE 2.0 pre-assessment capability covers crude tankers, product tankers, chemical tankers, and LPG carriers — the vessel types for which OCIMF has published the SIRE 2.0 question framework. Our assessors hold relevant tanker endorsements and operational experience for the vessel types they assess. Contact us with your vessel type and flag state to confirm assessor availability and relevant experience.

Question 23

What does the SIRE 2.0 pre-assessment report include?

Accepted Answer

The pre-assessment report includes a gap analysis referenced to the SIRE 2.0 question framework, crew competency findings for the officers assessed, documentation and record gaps identified during the review, and a prioritised corrective action plan. Findings are classified by priority — critical, high, and standard — based on the likelihood and severity of a SIRE finding if the gap is not addressed before the vetting inspection.

General

Scheduling

Timelines & Deliverables

Remote Navigation Audit

ISM / ISPS / MLC Audits

SIRE 2.0 Preparation

Have a question not covered here?