Oil Record Book Part I Entry Verification Audit
Verify Oil Record Book Part I entries against machinery-space operations, signatures, and supporting records before PSC review. Use it to catch missing entries, unauthorized corrections, and reconciliation gaps early.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Commercial Shipping · Tanker Operations · Bulk Carriers · Offshore Marine
Overview
This template is an inspection audit for Oil Record Book Part I, focused on verifying that machinery-space entries are complete, signed correctly, and supported by the vessel’s actual operating records. It walks the reviewer through the record scope, entry completeness, authorization, tamper evidence, and reconciliation so the audit follows the same logic a PSC inspector or internal compliance reviewer would use.
Use it when you need to confirm that ORB Part I pages are current, that required entries were made for machinery-space operations, and that the record can be tied back to logs, transfer records, and other supporting documents. It is especially useful before port calls, after major maintenance, during officer handover, or whenever the vessel has had a period of high activity that increases the chance of missed entries.
Do not use it as a general ship safety checklist or as a substitute for the vessel’s approved recordkeeping procedure. It is not meant for cargo record books, deck operations, or unrelated compliance systems. If the vessel uses electronic recordkeeping, the same audit logic still applies, but the reviewer should also confirm access controls, audit trail integrity, and that printed or exported records match the live system. The template is designed to surface deficiencies early so they can be corrected and escalated before they become a PSC finding.
Standards & compliance context
- Oil Record Book Part I review is commonly driven by MARPOL Annex I recordkeeping expectations and Port State Control scrutiny of machinery-space operations.
- The template supports company SMS controls and marine audit practices that expect traceable, contemporaneous entries with clear sign-off authority.
- Tamper-evidence checks align with the general compliance expectation that official records remain legible, unaltered, and capable of withstanding external review.
- For electronic ORBs, the audit should also reflect the vessel’s approved procedures for access control, audit trail retention, and record export integrity.
- Any discrepancy should be documented as a non-conformance or deficiency according to the vessel’s corrective-action process and flag-state or company reporting rules.
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
Inspection Setup and Record Scope
This section matters because it defines exactly which vessel, pages, and time period are under review so the audit has a clear and defensible scope.
-
Vessel name, IMO number, and inspection period recorded
Document the vessel identity and the date range covered by this verification audit.
-
ORB Part I pages reviewed are identified and complete
List the page numbers or entry sequence reviewed and confirm the audit scope includes all relevant machinery-space entries.
-
Latest ORB Part I available onboard for inspection
Confirm the current controlled copy of Oil Record Book Part I is available for review.
-
Supporting records available for reconciliation
Select the supporting records used to verify ORB entries against actual operations.
ORB Entry Completeness
This section matters because incomplete entries are one of the fastest ways an otherwise legitimate operation becomes a compliance deficiency.
-
Required machinery-space operations entries are present
Confirm entries exist for applicable operations such as bilge water discharge, sludge handling, incineration, tank cleaning, and internal transfers as applicable to the vessel.
-
Each entry includes date, time, and location or tank identification where required
Verify entries are complete enough to identify when the operation occurred and the equipment or tank involved.
-
Entries are legible and written in permanent ink or controlled electronic format
Check that entries can be read without ambiguity and are not faded, smudged, or otherwise unclear.
-
No unexplained gaps in the entry sequence
Confirm there are no missing pages, skipped entry numbers, or unexplained blank periods in the record.
Signature and Authorization Verification
This section matters because the record is only valid when the right people sign it at the right time under the vessel’s approved procedure.
-
Entries signed by the officer in charge where required
Verify the officer in charge has signed or initialed the applicable ORB Part I entries in accordance with ship procedures.
-
Entries signed by the Chief Engineer where required
Verify the Chief Engineer has reviewed and signed the applicable entries requiring engineering authorization or verification.
-
Signature dates align with the corresponding entries
Confirm signatures are dated appropriately and correspond to the correct entry period.
-
Any delegated signatory is authorized by ship procedure
If a substitute signed any entry, verify the person was authorized and the delegation is documented.
Record Integrity and Tamper Evidence
This section matters because official records must show a clean correction history and no signs of unauthorized alteration.
-
No erasures, white-out, or obliterations present
Verify the ORB contains no erased text, correction fluid, or removed content.
-
Corrections are made by single-line strike-through and initialed per procedure
If corrections exist, confirm they are traceable, readable, and made in a controlled manner without obscuring the original entry.
-
No unexplained overwriting, backdating, or inconsistent handwriting
Check for signs of manual alteration or suspicious changes that could indicate non-conformance or falsification.
Reconciliation Against Actual Operations
This section matters because the ORB must match what actually happened onboard, not just what was written after the fact.
-
ORB entries match supporting operational records
Verify the recorded operations are consistent with logs, transfer records, maintenance records, and equipment status.
-
Any discrepancies documented and escalated
Confirm any deficiency or non-conformance has been recorded, investigated, and assigned corrective action.
How to use this template
- 1. Enter the vessel name, IMO number, inspection period, and the exact ORB Part I pages or date range you are reviewing.
- 2. Gather the supporting records used for reconciliation, such as engine room logs, transfer records, maintenance notes, and any electronic exports.
- 3. Review each ORB entry for required date, time, location or tank identification, legibility, and uninterrupted sequence.
- 4. Verify that each entry has the correct officer and Chief Engineer sign-off, and confirm any delegated signer is authorized by ship procedure.
- 5. Check for erasures, white-out, overwriting, backdating, or inconsistent handwriting, then document any discrepancy and assign follow-up action.
Best practices
- Review the ORB against the supporting records on the same day so memory gaps do not hide a discrepancy.
- Treat missing signatures, missing dates, and unexplained gaps as deficiencies that require follow-up, not informal notes.
- Photograph or capture a controlled copy of any page with a correction, then verify the correction method matches ship procedure.
- Confirm that the page sequence is complete before you start the line-by-line review, because missing pages can mask larger record issues.
- Use the vessel’s actual tank names, machinery identifiers, and watchkeeping titles when reconciling entries so the audit does not rely on assumptions.
- If the vessel uses electronic records, verify the audit trail and export consistency before accepting the entry as complete.
- Escalate any mismatch between the ORB and operational evidence immediately, even if the underlying operation was legitimate.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this Oil Record Book Part I Entry Verification Audit cover?
It covers the review of Oil Record Book Part I pages for machinery-space operations, including entry completeness, required signatures, record integrity, and reconciliation to supporting logs. The template is designed to confirm that the book reflects what actually happened onboard, not just that pages are filled in. It also helps identify missing pages, unexplained gaps, and corrections that do not follow the vessel’s procedure.
When should this audit be run?
Run it before a Port State Control inspection, after a period of heavy machinery-space activity, and any time there has been a change in Chief Engineer or officer watchkeeping practices. It is also useful as a scheduled internal compliance check so errors are found before the next external review. If the vessel uses electronic records, run it after any system change or export cycle to confirm the audit trail is intact.
Who should complete the audit?
A competent marine compliance lead, Chief Engineer, or designated officer familiar with ORB Part I requirements should complete it. The reviewer needs access to the supporting operational records and authority to question discrepancies with the engineering team. On larger vessels, the audit is often performed by the Chief Engineer and then spot-checked by the master or shore-side superintendent.
Does this template align with regulatory expectations?
Yes. It is built around the recordkeeping expectations commonly enforced under MARPOL Annex I and PSC review practices, with supporting attention to tamper evidence and traceability. It also fits well with company SMS controls and audit methods used in marine compliance programs. The template is not a substitute for the vessel’s approved procedures or flag-state instructions, but it helps verify that the onboard record will stand up to review.
What are the most common mistakes this audit catches?
Common issues include missing machinery-space entries, entries without the required date or tank identification, signatures applied by the wrong person, and corrections made with white-out or overwriting. Reviewers also often find gaps between the ORB and engine room logs, bunker or sludge transfer records, and maintenance notes. Those discrepancies are important because they can look like incomplete recordkeeping even when the operation itself was legitimate.
How do I customize this template for my vessel?
Add vessel-specific signatory roles, the exact supporting records used onboard, and any company procedure for delegated signatures or electronic recordkeeping. You can also tailor the inspection period, page range, and escalation fields to match your fleet’s reporting workflow. If your vessel has unique machinery arrangements or tank naming conventions, include those so reviewers can reconcile entries consistently.
Can this be used with electronic Oil Record Books?
Yes, as long as the electronic format preserves legibility, access control, and an auditable change history. The audit should verify that entries are time-stamped, traceable to the correct operation, and protected from unauthorized alteration. It should also confirm that exports or printouts match the live record and that the approval workflow follows the vessel’s procedure.
How is this different from a general ship inspection checklist?
This template is focused specifically on Oil Record Book Part I verification, not general vessel condition or safety checks. That narrow scope matters because PSC and internal auditors look for exact record completeness, sign-off discipline, and consistency with actual machinery-space operations. A general checklist may miss the record-integrity issues that create compliance findings even when the engine room is operating normally.
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...
-
MangoApps 2026 Winter Release adds native shift scheduling, structural AI for surveys and wikis, and a redesigned search—unifying frontline operations in one...
-
See how the Kansas City Chiefs unified communication for 600+ event staff with a branded app, achieving 90% adoption and reaching every employee on game day.
-
Transform business with AI strategies that automate work, boost productivity, and help teams stay competitive faster.
-
Discover how a mobile-first employee app transforms retail staff training—streamlining onboarding, standardizing SOPs, and reaching every frontline worker.
Ready to use this template?
Get started with MangoApps and use Oil Record Book Part I Entry Verification Audit with your team — pricing built for small business.
