MARPOL Annex VI Fuel Changeover and Sulphur Compliance Log

Complete it for each voyage segment where the vessel is approaching or entering an Emission Control Area, and update it at the time of changeover rather than from memory later. It is most useful when the crew needs a contemporaneous record of planned entry, actual entry, and the point at which compliant fuel was fully in use. If your route includes multiple ECAs or repeated entries, create a separate record for each event. The goal is a time-stamped trail that can be checked against the vessel log and bunker records.

The officer responsible for fuel management or the bridge/engine watch team should complete the operational fields, with review by the chief engineer or another designated officer. The submitted-by field helps show accountability without over-collecting personal data. If your company uses a shore-side compliance review, this form can be handed off after submission for verification and filing. Keep the workflow clear so the person entering the data is also the person who can confirm the timing and tank status.

It helps show that the vessel changed over to compliant fuel before ECA entry, that the fuel in use matched the sulphur limit, and that the BDN supports the fuel grade claimed. It also captures vessel position and engine load so the record can be reconciled with operational conditions. If there is a deviation, the form preserves the reason and the corrective notes. That combination is what makes the record useful during internal review or an external inspection.

This template is built for documenting the operational steps tied to MARPOL Annex VI sulphur compliance when entering an ECA. It does not replace the regulation or the vessel’s SMS procedures, but it gives the crew a structured record of the evidence inspectors usually ask for. Use it alongside your voyage plan, engine room logs, and bunker documentation. If your company has stricter internal limits than the regulatory minimum, you can add those as custom fields.

The most common issues are recording the planned ECA entry instead of the actual entry, leaving the changeover completion time blank, and failing to note which tanks were involved. Another frequent problem is copying the BDN details without checking that the fuel grade and sulphur content match the fuel actually used. Some crews also forget to document deviations or assume a verbal explanation is enough. A complete record should be specific, time-stamped, and consistent with the vessel’s operational logs.

Yes. You can add vessel-specific tank names, company sulphur thresholds, route notes, or extra verification fields for your SMS. If your fleet operates in multiple ECAs, use the ECA name field and the other option to capture the exact zone. You can also add conditional logic so deviation details only appear when a deviation occurred. Keep the form lean by using only the fields your crew actually needs at the point of entry.

This log works well alongside voyage planning tools, engine room logs, bunker management records, and document storage for BDNs. If your workflow supports it, link the submission to a vessel compliance folder or an audit trail so the record is easy to retrieve later. Some operators also connect it to incident or nonconformance tracking when a deviation is reported. The key is to avoid duplicate manual entry while preserving the original signed record.

Start with one vessel or one route, confirm the required fields match your operating procedure, and train the crew on when to record planned versus actual times. Then standardize the naming of tanks, ECAs, and fuel grades so records are comparable across ships. Review the first few submissions for missing fields or unclear discrepancy notes before scaling fleet-wide. A short rollout with feedback usually produces cleaner records than a broad launch with no review.