BWTS Contingency Notification Pack: What to Send Flag and Port
Updated
A contingency notification should allow an authority to understand what happened, what was discharged or remains onboard, and what the master proposes next. This practical pack gives operators a fact-led structure without promising that any particular alternative will be accepted.
Request BWTS spare parts, annual calibration or ballast-water testing
Key takeaways
- Put the requested authority decision and vessel identifiers at the top.
- Separate verified facts, assumptions and the decision sought.
- Provide a navigable evidence index rather than an unstructured attachment archive.
- Describe safe controls and alternatives as proposals subject to authority direction.
- Record conditions, receipt, contacts and follow-up deadlines.
- Treat a notification as a request for direction, not as permission to act.
Define the initial request
Put the requested decision in the first paragraph: permission to hold ballast, instructions for a safe alternative, acceptance of a proposed exchange, direction for sampling, or advice on a delayed operation. Identify the ship, IMO number, agent, port, berth or anchorage, arrival and sailing windows, and the authority receiving the request.
Do not lead with a long technical narrative or an assertion that the vessel is compliant. Explain whether the system is unavailable, degraded, interrupted or producing a disputed indication, and distinguish facts observed onboard from assumptions still under investigation. Authorities can act faster when uncertainty is labelled rather than hidden.
Capture the ballast state
List the tanks, approximate volumes, uptake and discharge locations, dates, salinity or other relevant water conditions, treatment mode and current tank status. Identify whether the water was treated, partially treated, untreated, held, exchanged or discharged, and record any operation that was stopped before completion.
Include the next planned ballast movement and operational constraints such as cargo sequence, draft, stability, trim, tide and safe manning. These details explain urgency without turning commercial pressure into a justification for an unauthorised discharge. The master remains responsible for safe navigation and following the authority’s direction.
Assemble indexed attachments
Attach a concise alarm timeline, controller export, relevant screenshots, treatment trend data, valve line-up, pump flow, sensor and calibration status, maintenance history and photographs where useful. Name each file with vessel, event time and revision; provide a contact who can explain the data and its time zone.
Include the applicable Ballast Water Management Plan extract, Record Book entries, BWMS type-approval and installation references requested by the authority, plus any service report or maker advice. Do not send an undigested archive: an index with one-sentence descriptions lets the recipient find the evidence that supports each assertion.
State immediate controls and proposal
Set out immediate controls: stop or segregate the affected operation, retain ballast onboard, prevent cross-connection, protect personnel, preserve event data and arrange technical attendance. If an alternative such as exchange or discharge at another location is proposed, describe it as a request subject to authority approval, not as an entitlement.
Provide a recovery plan with responsible persons, parts or expertise required, estimated timing, verification steps and a reporting point. For a recurring alarm, separate temporary risk controls from the permanent corrective action. A credible plan states what cannot yet be confirmed and how that uncertainty will be reduced.
Route the pack and confirm receipt
Send through the established company, agent and authority channels and copy only parties who need the information. Confirm receipt by phone where time-critical, then retain the email, attachments, contact name and authority reference. Flag, port and coastal-state expectations can differ, so a previous port’s acceptance is not a standing permission.
For technical support, use the installed system’s manual and documented manufacturer contacts. Identify the system make, model, software revision and fault evidence in the request, and keep technical advice distinct from any authority decision.
Set response obligations
When direction arrives, restate it internally in an execution checklist: who may do what, where, by when and what evidence must be returned. Record any conditions, sampling requirements, reporting deadlines and restrictions. Brief the bridge, engine room, cargo team, agent and shore superintendent so the same instruction is followed.
Submit the promised follow-up with completion evidence, not merely an invoice or technician note. Update the contingency register, root-cause investigation and planned maintenance. If no authority response arrives, escalate through the designated channel; silence should not be treated as approval.
Frequently asked questions
Should a notification say the ship is non-compliant?
It should accurately state the known condition and uncertainty. Avoid legal conclusions unless issued by the competent authority; explain the failure, affected operation, controls and decision requested.
What is the most important attachment?
There is no universal single attachment. A concise event timeline backed by controller data, Record Book entries, tank details and the relevant management-plan extract is usually the most useful starting set.
Can an agent approve a contingency alternative?
An agent can transmit or coordinate a request, but acceptance must come from the applicable flag, port or coastal-state authority.
Should commercial cargo pressure be included?
Include operational timing and safety constraints factually, but do not present cargo schedule as permission to bypass ballast-water requirements or authority instructions.
Sources
- IMO — BWM Convention and Guidelines — Convention obligations and associated guidance.
- IMO — compilation of BWM guidance — Compilation identifying BWM.2/Circ.62 contingency and BWM.2/Circ.42/Rev.2 sampling guidance.
- IMO — BWMS Code, resolution MEPC.300(72) — Code framework for approval and testing of ballast-water management systems.
- IMO — commissioning resolution MEPC.325(75) — Commissioning testing and documentation context.
Related articles
- BWTS Failure During Cargo Operations: A Shipboard Decision Sequence
- BWTS Contingency Drills: Testing the Failure Response Before a Port Call
- BWTS Sampling Plan for Troubleshooting a Disputed Result
- Ballast Water Record Book: Requirements and PSC Findings
- What Is a Ballast Water Treatment System? Explained
- How Does BWTS Installation Work? Step by Step
Request spares, calibration or ballast-water testing
Include BWMS brand/model, vessel/IMO number, port/terminal, date/ETA and scope or part numbers. These links prepare an email draft; you must send it yourself.
- Request a parts quote — Sensors, TRO reagents, calibration kits and replacement parts. Confirm compatibility, availability and delivery for your installed system.
- Request a calibration booking — Annual instrument calibration with a calibration certificate for the work completed. OEM instructions, drift or applicable rules may require earlier work.
- Request testing coordination — Arrange sampling and testing with an appropriately qualified party for your IMO D-2, commissioning or other stated purpose.
Authorised Headway agent. Other-brand enquiries are independently reviewed; no OEM authorisation is claimed. Sea Clean is not an accredited laboratory or approving authority. Calibration does not demonstrate biological D-2 compliance. Attendance, testing scope and parts delivery are confirmed per enquiry.