[gtranslate]

What Records Does a Ship Need to Prove Scrubber Washwater Compliance?

by Afshan

A compliant monitor reading is not the same as a defensible compliance record. Port state control inspectors, flag state surveyors and classification society auditors reviewing EGCS washwater compliance are not looking at a single number on a screen. They are reviewing a chain of documented evidence covering what was measured, where the vessel was, whether the monitoring system was functioning correctly, whether it was maintained, what happened when it malfunctioned and how any retained washwater was disposed of.

Under MEPC.340(77), the requirements for this evidence chain are now significantly more explicit than they were under MEPC.259(68). For ships where MEPC.340(77) applies, the EGCS Record Book is a named compliance document that must contain specific categories of entry. For the full explanation of which guideline applies to each vessel and what changed between the two resolutions, see What Is MEPC.340(77) and How Does It Differ From MEPC.259(68)?.

Key thing to remember

The evidence chain for scrubber washwater compliance has two dimensions: what the water measured, and whether the vessel was in a location where discharge was permitted. A monitoring record that shows compliant parameter values is still insufficient if the vessel was in waters where discharge was prohibited. Both the measurement record and the position-linked discharge record are required to demonstrate compliance.

Why Is a Monitoring Record Alone Not Sufficient for Compliance?

A continuous monitoring record showing that washwater parameter values were within the MEPC.259(68) or MEPC.340(77) limits is a necessary part of the compliance record. But it answers only one of the questions that inspectors and authorities need to resolve:

  • Was the washwater within the measured parameter limits? The monitoring data answers this.
  • Was the monitoring instrument functioning correctly and maintained? The maintenance and servicing records answer this.
  • Was the vessel in a location where discharge was permitted? Position-linked discharge records answer this.
  • When the vessel entered restricted waters, did discharge stop or mode change? Mode change records with position and time answer this.
  • When the monitoring system malfunctioned, what action was taken? Malfunction records and correspondence answer this.
  • Was retained washwater and residue properly disposed of ashore? Shore reception receipts answer this.

An inspector who finds a complete and consistent set of records covering all these questions has a complete compliance picture. An inspector who finds monitoring data but no mode change records, no maintenance log and no shore reception receipts has a compliance picture with significant gaps. Those gaps become deficiency findings.

What Is the EGCS Record Book and Who Must Keep One?

The EGCS Record Book is a named compliance document required under MEPC.340(77). It is the primary document in which all EGCS operational events, maintenance activities, malfunction events and residue management entries must be recorded. For vessels where MEPC.340(77) applies, maintaining an EGCS Record Book is mandatory. For vessels still under MEPC.259(68), best practice is to maintain equivalent records even where a formally named EGCS Record Book is not explicitly required, because inspectors will look for this level of documentation regardless of which guideline applies.

The EGCS Record Book must be kept onboard the vessel and be available for inspection at all times. It is not a document that can be reconstructed after the fact if an inspection reveals it was not being maintained. An absent or incomplete EGCS Record Book is a compliance finding in its own right, separate from any question about the washwater measurement data.

What Is the Complete Set of Records Required for Washwater Compliance?

The table below sets out the full set of records that a ship needs to demonstrate scrubber washwater compliance, what each record captures, where it is kept and the key notes on retention and use.

Record type What it captures Where it is kept Retention and notes
Continuous washwater monitoring data Continuous real-time readings of PAH, turbidity, pH and temperature at the discharge point; recorded at not less than 0.0111 Hz under MEPC.340(77) Data logging system integrated with the EGCS monitoring unit Retained onboard and available for inspection; duration specified by flag Administration; typically minimum 12 months
Alarm event log Record of every high-parameter alarm activation, the reading that triggered it, the time, the duration and the action taken by the crew EGCS monitoring unit data log and EGCS Record Book Retained onboard; each alarm event must be individually recorded with crew response documented
Discharge event log Record of each discharge operation: start time, stop time, EGCS mode active, vessel position and speed, whether parameters were within limits throughout EGCS monitoring unit data log and EGCS Record Book Retained onboard; position-linked records essential for demonstrating compliance in geographically restricted waters
EGCS mode change records Record of every change between open-loop, closed-loop and hybrid modes, with date, time and vessel position at the time of the mode change EGCS Record Book Critical for demonstrating that discharge stopped or mode changed before entering restricted waters such as OSPAR internal waters or port ban areas
Monitoring system maintenance and servicing records Record of all maintenance, calibration, servicing and replacement of monitoring system components, with dates and details of work carried out EGCS Record Book Required under MEPC.340(77); demonstrates that the monitoring data produced was from a correctly maintained instrument
EGCS residue management records Record of residue type, quantity generated, storage location onboard, and disposal method and location for all EGCS residues including sludge and washwater retained for shore disposal EGCS Record Book Required under MEPC.340(77); shore reception receipts should be retained alongside the EGCS Record Book entries
Monitoring system approval certificate Flag state Administration approval confirming that the discharge water monitoring system meets the requirements of MEPC.259(68) or MEPC.340(77) as applicable Ship’s certificate file Must be available for inspection onboard; renewal required where the monitoring system is replaced or significantly modified
Malfunction event records Record of every monitoring system malfunction, including the nature of the fault, duration, action taken and date of repair; reports made to flag and port state where required EGCS Record Book and correspondence file Required under MEPC.1/Circ.883/Rev.1; failures lasting more than one hour must be reported to flag and port state authorities
Shore reception receipts Receipts confirming delivery of retained washwater and EGCS residues to a shore reception facility, including facility name, date, quantity and waste type Shore reception receipt file; cross-referenced to EGCS Record Book Required to close the loop on retained washwater disposal records; inspectors will cross-check receipt dates and quantities against EGCS Record Book entries
EGCS technical file Technical documentation for the EGCS installation including system description, approved components, installation survey records and class certificates Ship’s certificate and technical file Must be available for inspection; demonstrates that the EGCS installation is approved and that the monitoring system is part of the approved configuration

 

The SMART ESM provides continuous data logging of PAH, turbidity, pH and temperature at the required frequency and stores the monitoring record in a format that supports inspection review and export to the EGCS Record Book system. Rivertrace can advise on how to integrate the SMART ESM data output with the vessel’s EGCS Record Book system.

Why Are Position-Linked Records Particularly Important Now?

The growing number of geographic restrictions on EGCS discharge — including OSPAR Decision 2025/01, Singapore port waters, Fujairah and Chinese territorial waters — makes position-linked discharge records more important than at any previous point. For a full map of current restrictions, see Where Is Open-Loop Scrubber Discharge Banned or Restricted?.

A monitoring record that shows compliant parameter values but lacks position data cannot demonstrate that discharge did not take place in restricted waters. If a vessel passed through Singapore, an OSPAR coastal state’s internal waters or another restricted area during a period covered by the monitoring record, an inspector will look for position-linked evidence that discharge was suspended or that the vessel switched to closed-loop mode during that transit.

Position-linked records must show:

  • The vessel position (latitude and longitude) at the time of each discharge event
  • The time and position at which EGCS mode changed from open-loop to closed-loop when entering restricted waters
  • The time and position at which discharge resumed when the vessel left restricted waters
  • Cross-reference to the vessel’s voyage log or AIS data to allow verification of position

 

Missing position records create the presumption of non-compliance

If a vessel cannot produce position-linked discharge records for a period when it transited restricted waters, an inspector cannot verify that discharge stopped at the correct point. In the absence of evidence to the contrary, the inspector may presume that discharge continued in restricted waters. The burden of proof lies with the operator. Position records are the primary evidence that resolves this.

What Should the EGCS Record Book Contain for Each Category of Entry?

Operational event entries

Each EGCS operational event must be entered in the EGCS Record Book with the date, time, vessel position, event type and name of the officer making the entry. Operational events include:

  • EGCS startup and shutdown
  • Change of EGCS operating mode between open-loop, closed-loop and hybrid
  • Discharge start and discharge stop
  • Entry into and departure from waters where discharge is restricted or prohibited
  • Any period of EGCS operation without discharge

Monitoring system maintenance and servicing entries

Each maintenance or servicing event for the washwater monitoring system must be entered with the date, nature of the work carried out, any components replaced, and the name of the person or service company carrying out the work. This record demonstrates that the monitoring data produced during the covered period was from a correctly maintained instrument.

Malfunction entries

Every monitoring system malfunction must be entered immediately on discovery. The entry must include the date and time of discovery, the nature of the fault, the duration of the malfunction, any action taken during the malfunction period to preserve interim compliance evidence, the date and nature of the repair, and whether a report was made to flag and port state authorities.

Residue management entries

Every generation and disposal of EGCS residue must be entered, including the residue type, quantity generated, storage method and location onboard, and disposal method, location, facility name and date. Shore reception receipts must be retained and cross-referenced to the residue management entries.

What Do Port State Control Inspectors Look for When Checking EGCS Records?

Port state control inspectors conducting an EGCS compliance check are experienced in identifying gaps in the evidence chain. The table below summarises what inspectors focus on and the consequences of deficiencies in each area.

What inspectors check What they are looking for Consequence of a deficiency
EGCS Record Book completeness Whether the Record Book exists, is being maintained and covers the required entries — operational events, mode changes, maintenance, malfunctions and residue disposal Incomplete or absent EGCS Record Book is an immediate deficiency under MEPC.340(77)
Continuous monitoring data Whether continuous washwater data exists for the period being reviewed; whether alarm events are recorded and cross-referenced to crew response entries Gaps in continuous data, unexplained alarm events or missing crew response records create compliance questions
Position-linked discharge records Whether discharge records include vessel position data allowing the inspector to verify that discharge did not take place in geographically restricted waters Absence of position-linked records makes it impossible to verify compliance in restricted areas such as OSPAR internal waters or port ban zones
Monitoring system approval and maintenance Whether the monitoring system approval certificate is current; whether maintenance records show the system has been serviced according to the manufacturer’s schedule and MEPC.340(77) requirements Out-of-date approval or maintenance gaps undermine the credibility of the monitoring data
Malfunction records and reporting Whether malfunction events are recorded in the EGCS Record Book and whether required reports to flag and port state were made for failures exceeding one hour Unrecorded malfunctions or failures to report are direct breaches of MEPC.1/Circ.883/Rev.1
Shore reception receipts Whether receipts for retained washwater and EGCS residue disposal are held onboard and cross-reference correctly to EGCS Record Book disposal entries Discrepancies between Record Book entries and receipts suggest disposal records are incomplete or inaccurate

A vessel with a complete, consistent and well-maintained evidence record is in a significantly stronger position during a port state control inspection than one where the EGCS Record Book has gaps, alarm events are unaccounted for or position records do not cover the full period of discharge. Deficiency findings related to EGCS records can result in detention, requirement to rectify before departure, or referral to the flag state for further action.

What Records Are Required When the Monitoring System Malfunctions?

Monitoring system malfunctions require specific record-keeping actions under MEPC.1/Circ.883/Rev.1. The table below sets out the required actions and when each must be completed.

When Action required Regulatory basis
Immediate Record the malfunction in the EGCS Record Book with the date, time, nature of the fault and name of the officer making the entry. MEPC.1/Circ.883/Rev.1 — record immediately on discovery
Immediate Take action to preserve other available evidence of compliance during the period the monitor is non-functional: retain vessel position logs, voyage data recorder data, EGCS operational logs and any other data that demonstrates what the EGCS was doing and where the vessel was. MEPC.1/Circ.883/Rev.1 — preserve interim evidence
Within 1 hour if fault persists If the monitoring system fault cannot be rectified within one hour, report the malfunction to the flag state Administration and the port state Administration of the next port of call. MEPC.1/Circ.883/Rev.1 — mandatory reporting obligation
As soon as practicable Repair or replace the monitoring system equipment. Record the repair in the EGCS Record Book with the date, nature of the repair and the name of the person carrying it out. MEPC.1/Circ.883/Rev.1 — repair as soon as practicable
Consider immediately Where compliance cannot be demonstrated during the malfunction period, the vessel may need to stop EGCS discharge or switch to compliant fuel for the affected leg. Operator judgment — MEPC.1/Circ.883/Rev.1 implies continued operation requires evidence of compliance
Ongoing Retain all malfunction records, repair records and correspondence with flag and port state in the EGCS Record Book and correspondence file for the period specified by the flag Administration. Best practice — inspectors will review malfunction history

 

Repeated malfunctions attract particular scrutiny

A single malfunction that is promptly recorded, reported and repaired is a manageable compliance event. Repeated malfunctions of the same component, or patterns of malfunction that coincide with passages through restricted waters, attract significantly more scrutiny from port state control inspectors and flag state authorities. Repeat malfunction history visible in the EGCS Record Book may trigger a deeper investigation of the vessel’s EGCS compliance record.

How Does the Evidence Record Differ Between MEPC.259(68) and MEPC.340(77) Vessels?

The substantive content of the evidence chain is similar for both groups of vessels. The difference is in how explicitly each record requirement is defined in the applicable guideline:

  • Under MEPC.259(68): the continuous monitoring data record is required; alarm event logging is required; maintenance records are expected but not explicitly prescribed in a named document. The monitoring system does not require a standalone Administration approval step.
  • Under MEPC.340(77): all of the above applies, plus the EGCS Record Book is a named mandatory document; the monitoring system requires Administration approval; recording frequency must be not less than 0.0111 Hz; and maintenance, residue management and malfunction records must specifically be kept in the EGCS Record Book.

In practice, port state control inspectors reviewing vessels under MEPC.259(68) will still look for a comprehensive records package. The named EGCS Record Book requirement under MEPC.340(77) makes the expectation explicit, but operators of MEPC.259(68) vessels who maintain equivalent records will be in a much stronger position during inspections than those who rely only on the monitoring data log.

How Does the Monitoring System Support the Evidence Record?

A well-specified and well-maintained monitoring system does more than measure parameter values. It generates and stores the data record that underpins the compliance evidence chain. For this reason, the reliability and completeness of the monitoring system’s data logging function is as important as the accuracy of its measurements.

The monitoring system should:

  • Record continuously at the frequency required by the applicable guideline, without gaps caused by power interruptions, sensor faults or software issues
  • Log alarm events with accurate timestamps that can be cross-referenced to the EGCS Record Book entries
  • Store data in a format that can be exported for inspection review and for entry into the EGCS Record Book system
  • Support integration with vessel position data so that monitoring records can be linked to vessel position and EGCS mode without manual data entry
  • Provide self-diagnostic information that allows crew to identify monitoring system faults promptly and make accurate malfunction log entries

For marine vessel operators reviewing their current EGCS monitoring arrangement, Rivertrace can advise on whether the SMART ESM configuration meets the data logging requirements of MEPC.340(77) and supports the full evidence record described in this article. For the full washwater compliance framework, see the exhaust scrubber washwater discharge monitoring explainer page.

Frequently Asked Questions

What records does a ship need to prove scrubber washwater compliance?

A ship needs ten categories of record to prove comprehensive EGCS washwater compliance: continuous monitoring data for PAH, turbidity, pH and temperature; an alarm event log; position-linked discharge event records; EGCS mode change records; monitoring system maintenance and servicing records; EGCS residue management records; the monitoring system approval certificate; malfunction event records; shore reception receipts for retained washwater and residues; and the EGCS technical file. Under MEPC.340(77), all relevant entries must be kept in the EGCS Record Book.

What is the EGCS Record Book?

The EGCS Record Book is a named compliance document required under MEPC.340(77). It must contain records of EGCS operational events including startup, shutdown and mode changes; maintenance and servicing records for the washwater monitoring system; malfunction records and crew response; EGCS residue storage and disposal entries; and records of any exceptional circumstances. It must be kept onboard and available for port state control inspection at all times.

Why are position-linked discharge records important?

Position-linked discharge records demonstrate that discharge did not take place in geographically restricted waters such as OSPAR internal waters, Singapore port waters or other ban areas. A monitoring record showing compliant parameter values cannot demonstrate geographic compliance without position data confirming where the vessel was when discharge took place. In the absence of position records, an inspector cannot verify that discharge was stopped at the correct point when entering restricted waters.

What must a ship do when the washwater monitoring system malfunctions?

Under MEPC.1/Circ.883/Rev.1, the crew must immediately record the malfunction in the EGCS Record Book, preserve interim compliance evidence during the period the monitor is not functioning, repair the equipment as soon as practicable, and report failures lasting more than one hour to the flag state and port state Administration. All malfunction records, repair records and correspondence must be retained in the EGCS Record Book.

Do MEPC.259(68) vessels need to keep an EGCS Record Book?

The EGCS Record Book as a formally named document is required under MEPC.340(77). MEPC.259(68) vessels are not explicitly required to maintain a document with this name. However, port state control inspectors reviewing EGCS compliance on MEPC.259(68) vessels will still look for a comprehensive and consistent records package covering monitoring data, maintenance history, malfunction events and residue disposal. Maintaining equivalent records in a structured format is strongly recommended for all scrubber-equipped ships regardless of which guideline applies.

How long must EGCS compliance records be retained onboard?

The retention period for EGCS compliance records is specified by the flag state Administration. As a minimum, records covering at least the previous 12 months are typically expected to be available onboard for inspection. Some flag states specify longer retention periods. Operators should confirm the applicable retention requirement with the flag state Administration and ensure that records are accessible in a form that allows inspection review.

What happens if the EGCS Record Book is incomplete during a port state control inspection?

An incomplete or absent EGCS Record Book is a deficiency finding under MEPC.340(77). Depending on the severity and nature of the gaps, the deficiency may result in a requirement to rectify before departure, a referral to the flag state for further action, or in serious cases, detention of the vessel. Gaps that coincide with passages through restricted waters or with known operational events attract the most scrutiny and the most serious consequences.

Related content

→ Exhaust Scrubber Washwater Discharge Monitoring: EGCS Compliance, Regulations and Geographic Restrictions

→ What Is MEPC.340(77) and How Does It Differ From MEPC.259(68)?

→ What Is OSPAR Decision 2025/01 and What Does It Mean for Scrubber-Equipped Ships?

→ Where Is Open-Loop Scrubber Discharge Banned or Restricted?

→ SMART ESM: Washwater Monitor product page