SIRE 2.0 PIQ and HVPQ Data Verification Checklist
Verify PIQ and HVPQ vessel data before submission so inspection requests are complete, consistent, and traceable. This checklist helps catch mismatched particulars, expired certificates, and missing evidence before filing.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Maritime Shipping · Oil And Gas Tanker Operations · Ship Management · Marine Compliance
Overview
This checklist is a pre-submission control for SIRE 2.0 PIQ and HVPQ data. It is used to verify that the vessel’s identity, particulars, certificates, survey status, equipment data, and supporting evidence are complete and consistent before an inspection request is filed.
The template is organized the way a reviewer would actually validate the file: first confirming the submission cycle and source documents, then checking vessel identity and statutory particulars, then reviewing certificates and survey status, followed by equipment and safety data, and finally confirming that both questionnaires match and the package is approved for submission. That makes it useful for operators, technical teams, and vetting coordinators who need a repeatable review step rather than a one-off spreadsheet check.
Use it when preparing a new submission, after a certificate renewal, following drydock or modification work, or whenever vessel particulars change. Do not use it as the only record of compliance, and do not rely on it if source documents are missing, unresolved discrepancies remain, or the vessel’s status is still changing. It is a verification checklist, not a replacement for class records, statutory certificates, or the underlying management system. If the vessel has temporary certificates, exemptions, or recent survey findings, those items should be explicitly explained before submission.
Standards & compliance context
- The checklist supports documentation control and traceability expectations commonly associated with maritime vetting, class, and flag-state oversight.
- It helps teams maintain alignment with statutory certificate management and survey status practices used across international shipping compliance programs.
- Where applicable, it can be adapted to reflect safety management and security documentation expectations tied to ISM, ISPS, and MLC frameworks.
- It is a verification aid, not a legal determination, and should be used alongside the vessel’s controlled records and applicable authority requirements.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Readiness and Source Control
This section confirms the submission is based on the correct version and traceable source records before any data is reviewed in detail.
-
PIQ and HVPQ versions match the current submission cycle
Verify the questionnaire versions are the latest approved versions for this vessel and inspection request.
-
Data source documents are identified and traceable
Source documents for vessel particulars, certificates, and operating data are identified and available for review.
-
Last review date is recorded and within the required update window
Record the date and time the PIQ/HVPQ data was last reviewed for accuracy.
-
Open data gaps or unresolved discrepancies remain
Confirm there are no unresolved discrepancies, missing fields, or conflicting entries.
Vessel Identity and Particulars
This section verifies the vessel’s core identity and technical particulars so the submission matches official records.
-
Vessel name, IMO number, and call sign match official records
Confirm the vessel identity fields are identical across PIQ, HVPQ, certificates, and registry documents.
-
Flag state, port of registry, and owner/operator details are current
Verify ownership and registry data reflect the current operating status.
-
Principal dimensions and tonnage values are consistent
Verify length, breadth, depth, draft references, gross tonnage, net tonnage, and deadweight are consistent across records.
-
Vessel type, build year, and shipyard details are accurate
Confirm vessel type classification, year built, and shipyard information are correct.
Certificates, Surveys, and Statutory Status
This section checks whether the vessel’s compliance status, certificate dates, and survey history are current and accurately described.
-
Statutory certificates are listed with correct issue and expiry dates
Verify all required certificates are present and their dates are accurate.
-
Class status and survey status are current
Confirm class notation, class status, and survey due dates are current.
-
ISM, ISPS, and MLC-related compliance dates are accurate where applicable
Check the accuracy of management system and labor compliance records included in the submission.
-
Temporary or conditional certificates are identified and explained
Identify any temporary, interim, or conditional certificates and note the reason and expiry status.
-
Survey and inspection history entries are complete and accurate
Verify survey and inspection history fields are complete and reflect the latest records.
Equipment, Capacity, and Safety Data
This section validates the operational data that often changes after refit, repair, or replacement work.
-
Cargo, ballast, and tank capacities are accurate
Confirm capacity values and tank particulars match approved technical records.
-
Navigation, communication, and emergency equipment counts are correct
Check that equipment quantities and fitted systems are accurately represented.
-
Safety equipment service dates are current where listed
Verify service dates for safety-critical equipment are current and correctly entered.
-
Any equipment modifications or exemptions are documented
Record modifications, waivers, exemptions, or equivalent arrangements that affect the data set.
Consistency, Exceptions, and Final Approval
This section closes the loop by confirming both questionnaires align, exceptions are explained, and the submission is approved.
-
PIQ and HVPQ entries are consistent with each other
Confirm matching fields do not conflict between the two questionnaires.
-
All required comments, attachments, and evidence are included
Verify all mandatory supporting documents and explanations are attached.
-
Final reviewer approval obtained
Capture final approval from the responsible reviewer before submission.
-
Submission status
Final disposition of the PIQ/HVPQ verification review.
How to use this template
- 1. Load the current PIQ and HVPQ versions for the submission cycle and attach the source records that support each field.
- 2. Compare vessel identity, particulars, certificates, and equipment entries against official documents, class records, and internal fleet data.
- 3. Mark every mismatch, missing value, expired date, temporary certificate, or unresolved discrepancy as a finding that must be corrected or explained.
- 4. Confirm that PIQ and HVPQ entries are aligned with each other and that all required comments, attachments, and evidence are included.
- 5. Obtain final reviewer approval only after the source control check is complete and the submission is ready to file.
Best practices
- Use one named source of truth for each field, such as class records, statutory certificates, or the vessel’s controlled technical file.
- Record the last review date and the submission cycle on the checklist so reviewers can see whether the data is current.
- Flag temporary certificates, conditional approvals, and exemptions in plain language and explain the operational impact where relevant.
- Verify IMO number, call sign, and vessel name against official records before checking any secondary data fields.
- Treat changes in dimensions, tonnage, cargo capacity, or equipment counts as controlled updates that require re-verification.
- Photograph or attach evidence for any disputed item so the reviewer can trace the correction back to the source document.
- Do not approve the submission if PIQ and HVPQ contain conflicting values, even if the difference seems minor.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this SIRE 2.0 PIQ and HVPQ checklist cover?
It covers the pre-submission verification of Pre-Inspection Questionnaire and Harmonised Vessel Particulars Questionnaire data. The checklist walks through vessel identity, certificates, survey status, equipment, and final consistency checks before an inspection request is filed. It is designed to confirm that the data set is complete, current, and internally aligned.
When should this checklist be used?
Use it before every new inspection submission and again whenever vessel particulars, certificates, or equipment data change. It is especially useful after drydock, class survey, certificate renewal, ownership changes, or vessel modifications. The goal is to catch discrepancies before the request is sent to the receiving party.
Who should complete the verification?
It is usually completed by the vessel operator, technical superintendent, marine superintendent, or a designated vetting coordinator. A final reviewer with access to source records should confirm the entries before approval. If the organization uses a document control or compliance function, that team should also validate source traceability.
How does this relate to compliance expectations?
The checklist supports good record control and due diligence under maritime vetting practices and aligns with the broader expectations of class, flag, and port-state documentation accuracy. It also helps teams maintain consistency with statutory certificate records, survey status, and safety management documentation. It is a verification tool, not a substitute for the underlying regulatory or class requirements.
What are the most common mistakes this checklist helps prevent?
Common issues include mismatched IMO numbers, outdated certificate expiry dates, inconsistent vessel dimensions, and missing explanations for temporary certificates or exemptions. Teams also miss equipment changes that were made after the last questionnaire update. Another frequent problem is submitting PIQ and HVPQ versions that do not match each other or the current review cycle.
Can this checklist be customized for different vessel types?
Yes. You can tailor the equipment section, survey references, and exception fields for tankers, bulk carriers, container ships, gas carriers, or mixed fleets. Many operators also add company-specific evidence requirements, approval steps, or links to source documents. The core structure should stay the same so every submission is reviewed consistently.
How often should the data be re-verified?
At minimum, verify it before each submission and after any material change to the vessel or its compliance status. Many operators also run it on a scheduled cadence tied to certificate renewals, annual reviews, or vetting preparation windows. If the vessel has had recent repairs, modifications, or survey findings, re-check immediately.
How is this different from an ad-hoc spreadsheet review?
An ad-hoc review often depends on memory and scattered emails, which makes it easy to miss discrepancies or outdated fields. This checklist creates a repeatable control point with clear sections for source control, vessel particulars, certificates, equipment, and final approval. That structure makes it easier to prove what was checked and who signed off.
Related templates
Go deeper on the topic
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
MangoApps in Okta Integration Network automates user provisioning, SSO, and access management for stronger security and less admin work.
Ready to use this template?
Get started with MangoApps and use SIRE 2.0 PIQ and HVPQ Data Verification Checklist with your team — pricing built for small business.
