Coordinating Certificate Transfer Dates in MSC Fisheries Audits

Learn how to coordinate transfer dates between CABs to prevent certification gaps under MSC General Certification Requirements v2.7 rules.

By 4Auditee7 min read
Coordinating Certificate Transfer Dates in MSC Fisheries Audits
On this page
  1. What the transfer date requirement is, and why it exists
  2. Pre-transfer reviews and establishing the agreed transfer date
  3. Scheme database synchronization and transition rules
  4. Example
  5. Certificate validity, condition carry-over, and merged certificates
  6. Before your audit
  7. Questions people ask
  8. How far in advance must the MSC be notified of an agreed certificate transfer date?
  9. What happens if a preceding CAB cancels a certificate before the agreed transfer date?
  10. Does transferring a certificate to a new CAB extend the certificate expiry date?
  11. What deadline applies to preceding CABs when providing requested transfer files?
  12. How are transfer dates managed when merging certificates issued by different CABs?
  13. Reference documents

The short version

  • Succeeding CABs, current CABs, and clients must formally agree on the certificate transfer date under clause 4.11.12.
  • The succeeding CAB must notify the MSC of the agreed transfer date at least ten days in advance.
  • Current CABs cancel the old certificate on the transfer date while succeeding CABs simultaneously issue the new certificate.
  • Preceding CABs must not cancel certificates before the agreed transfer date to prevent gaps in certification validity.

What the transfer date requirement is, and why it exists

Under Section 4.11 of MSC General Certification Requirements v2.7, certificate holders maintain the right to transfer their certification from a preceding Conformity Assessment Body to a succeeding body. Clause 4.11.12 mandates that the succeeding body, the current body, and the fishery client must jointly agree upon a specific transfer date. On this agreed transfer date, all rights, duties, and contractual obligations for maintaining certification pass officially to the succeeding body.

Coordinating a precise transfer date exists to safeguard market continuity while preserving the integrity of the Marine Stewardship Council program. A single fishery scope can hold only one active certificate in the MSC scheme database at any point in time. Setting a binding transfer date ensures that the unique fishery certificate code generated under Section 7.5 remains continuous, preventing gaps in certification status that would otherwise block seafood sales. Quality managers, compliance leads, and internal auditors must master this coordination process to ensure uninterrupted ecolabel claims during auditor changes.

Pre-transfer reviews and establishing the agreed transfer date

Reaching agreement on a transfer date requires completing a structured series of pre-transfer due diligence steps. Under clause 4.11.3.b, the succeeding Conformity Assessment Body must secure a written non-disclosure agreement waiver from the client to receive historical audit records. Under clause 4.11.8, the preceding body must supply all requested certification data, outstanding conditions, and surveillance files within ten days of receiving a formal request.

  • Record the formal transfer request and obtain a signed non-disclosure agreement waiver from the client under clause 4.11.3.
  • Gather historical surveillance reports, open condition logs, and audit findings from the client or preceding body under clause 4.11.4.
  • Conduct a pre-transfer review under clause 4.11.5 and determine the appropriate audit entry pathway under clause 4.11.9.
  • Present proposed audit actions to the client and obtain written confirmation to proceed with the transfer under clause 4.11.10 and clause 4.11.11.
  • Contact the preceding body and client to negotiate and formally set the agreed transfer date under clause 4.11.12.

Following client acceptance, clause 4.11.12.a dictates that the current body must facilitate complete record transfers, even if a formal client contract is no longer active. The agreed transfer date serves as the operational anchor for all subsequent database actions. Setting this date ensures both certification bodies synchronize administrative workflows, preventing premature certificate cancellations or delayed issuances.

RequirementWhat the auditor checksEvidence to have ready
Pre-transfer review executionEvaluation of certificate scope, validity, outstanding conditions, complaints, and assurance audit findingsCompleted pre-transfer review file, historical surveillance reports, and open condition records
Data exchange authorizationVerification of a valid non-disclosure agreement or signed waiver permitting data sharing between bodiesSigned non-disclosure agreement waiver or client data transfer authorization letter
Transfer date agreementWritten consensus between succeeding body, current body, and client confirming the exact agreed transfer dateTripartite transfer date agreement correspondence and confirmed transfer timeline
Ten-day MSC notificationVerification that the succeeding body notified the MSC at least ten days prior to the transfer dateFormal notification confirmation log uploaded to the MSC database

Important: Under clause 4.11.13, the succeeding Conformity Assessment Body must inform the MSC of the agreed transfer date at least ten days before the transfer occurs.

Common finding: Succeeding bodies frequently attempt to set transfer dates without providing ten days advance notice to the MSC, resulting in administrative rejection and delayed database synchronization.

Tip: Internal auditors should establish the target transfer date at least four weeks in advance to allow adequate time for data exchange, pre-transfer review, and the mandatory ten-day MSC notification window.

Scheme database synchronization and transition rules

Executing the certificate transition in the MSC scheme database requires precise timing on the agreed transfer date. Clause 4.11.14 dictates that on the agreed transfer date, the current Conformity Assessment Body must cancel the existing certificate in the scheme database and update all client records. Simultaneously, clause 4.11.15 mandates that the succeeding body must issue the new certificate in the scheme database before or on the agreed transfer date, guaranteeing no gap in certification validity occurs.

Guidance 4.11.14.a outlines severe operational risks associated with miscoordinated database actions. The current body must never cancel the certificate prior to the agreed transfer date, as premature cancellation leaves the client without a valid certificate. If a certificate is cancelled before the new certificate is issued, Guidance 4.11.14.a confirms that the client cannot make any certification claims or sell certified catch until re-certified by a body.

Example

A certified cod fishery decides to transfer its certification to a new Conformity Assessment Body midway through its five-year cycle. The succeeding body completes its pre-transfer review under clause 4.11.5, finding no unmanaged risks, and proposes to continue the existing surveillance program under clause 4.11.9.b.iii. On 1 October, the succeeding body, preceding body, and client formally agree on 1 November as the agreed transfer date under clause 4.11.12.

On 15 October, sixteen days prior to the transfer date, the succeeding body notifies the MSC of the 1 November transfer date, fully satisfying the ten-day notification requirement in clause 4.11.13. On 1 November, the preceding body cancels the original certificate in the scheme database, while the succeeding body issues the new certificate on the same day. Because both database actions occur on the agreed transfer date, the fishery maintains continuous certificate validity, allowing uninterrupted seafood processing and sales under its original certificate code.

Note: Under clause 4.11.12.a, preceding Conformity Assessment Bodies remain obligated to facilitate complete record transfers even for clients whose original contracts have expired or been terminated.

Certificate validity, condition carry-over, and merged certificates

A certificate transfer changes the managing Conformity Assessment Body without resetting the underlying certification cycle or technical requirements. Under clause 4.11.16.a, the expiry date of the certificate issued by the succeeding body must remain identical to the expiry date of the original certificate. Furthermore, clause 4.11.16.b dictates that all open conditions, milestones, and non-conformities set by the preceding body remain fully applicable until formally closed or revised during an on-site assessment.

Under clause 4.11.16.c, the succeeding body must adhere to the surveillance audit plan established by the preceding body. If the succeeding body proposes changes to the surveillance schedule, clause 4.11.16.c.i mandates that the revised schedule must be justified, documented, and communicated to the MSC at least 30 days prior to the next scheduled audit date. These rules prevent clients from utilizing certificate transfers to delay audit timelines or avoid condition closeouts.

When a client group seeks to merge multiple certified fisheries issued by different Conformity Assessment Bodies under Section 7.28 of MSC Fisheries Certification Process v2.3 and v3.0, transfer coordination rules apply directly. Clause 7.28.1.a.i requires that all certificates intended for merging must first be transferred to a single Conformity Assessment Body following Section 4.11 procedures. Under clause 7.28.2.c.i, the resulting merged certificate adopts the expiration date of the certificate with the shortest remaining duration, ensuring that transfer and merging workflows maintain rigorous compliance oversight.

Before your audit

  • Confirm that the current fishery certificate is valid and in good standing.
  • Execute a written non-disclosure agreement waiver authorizing data exchange between certification bodies.
  • Request all historical audit reports and open condition logs from the preceding Conformity Assessment Body.
  • Verify that the pre-transfer review is complete and accept the proposed audit pathway in writing.
  • Formally agree upon a specific transfer date with both the preceding and succeeding certification bodies.
  • Verify that the succeeding body submitted formal notification to the MSC at least ten days before the transfer date.
  • Confirm that the preceding body will not cancel the database certificate prior to the agreed transfer date.
  • Ensure that all open conditions, milestone timeframes, and original expiry dates are accurately transferred to the new certificate file.

Questions people ask

How far in advance must the MSC be notified of an agreed certificate transfer date?

Under clause 4.11.13 of MSC General Certification Requirements v2.7, the succeeding Conformity Assessment Body must inform the MSC of the agreed transfer date at least ten days in advance of that date.

What happens if a preceding CAB cancels a certificate before the agreed transfer date?

Under Guidance 4.11.14.a, cancelling a certificate before the agreed transfer date leaves the client without a valid certificate. The client is immediately barred from making certification claims or selling certified seafood until re-certified by a Conformity Assessment Body.

Does transferring a certificate to a new CAB extend the certificate expiry date?

No, clause 4.11.16.a explicitly mandates that the expiry date of the new certificate issued by the succeeding body must be identical to the expiry date of the original certificate issued by the preceding body.

What deadline applies to preceding CABs when providing requested transfer files?

Under clause 4.11.8, the preceding Conformity Assessment Body must supply all requested certification records and information within ten days of receiving the formal request.

How are transfer dates managed when merging certificates issued by different CABs?

Under clause 7.28.1.a.i of the MSC Fisheries Certification Process, certificates issued by different bodies must first be transferred to a single Conformity Assessment Body following General Certification Requirements Section 4.11 before merging can occur.

Reference documents

  • MSC General Certification Requirements v2.7
  • MSC Fisheries Certification Process v2.3
  • MSC Fisheries Certification Process v3.0
ShareLinkedInEmail

Manage this work in 4Auditee

Keep audit plans, problems, corrective actions and document versions in one place. See the records behind each change and decision.

Book a demo

Get new articles by email

Pick your topics. A short digest every Monday, or each new article as it is published.

You’ll get: MSC Fisheries · MSC Fisheries · Weekly digest

We email you a link to confirm. Nothing else is sent, and every email lets you unsubscribe. How we handle your address