eCTD vs NeeS: What Is the Difference and When to Use Each

Two electronic submission formats with very different histories — and very different futures. Here is what regulatory teams need to know about eCTD vs NeeS in 2026.

eCTD vs NeeS: A Complete Guide for Regulatory Affairs Professionals

For regulatory operations teams managing submissions across multiple markets, understanding the distinction between eCTD and NeeS isn’t just academic—it directly impacts your submission strategy, timeline, and compliance posture. As health authorities worldwide converge on eCTD mandates, the window for NeeS submissions continues to narrow. This guide provides a comprehensive comparison of eCTD vs NeeS to help you make informed decisions about your regulatory publishing approach.

Definitions: What Are eCTD and NeeS?

eCTD (Electronic Common Technical Document)

The Electronic Common Technical Document is the internationally harmonized format for regulatory submissions, developed under ICH (International Council for Harmonisation) guidelines M2 and M4. eCTD uses a standardized XML backbone to organize submission content into five modules:

• Module 1: Administrative and regional information (region-specific)
• Module 2: Summaries (Common Technical Document summaries)
• Module 3: Quality documentation
• Module 4: Nonclinical study reports
• Module 5: Clinical study reports

The XML backbone enables lifecycle management, allowing sponsors to add, replace, append, or delete documents across submission sequences while maintaining a complete audit trail.

NeeS (Non-eCTD Electronic Submission)

NeeS, or Non-eCTD Electronic Submission, represents a transitional electronic format that emerged as a bridge between paper submissions and full eCTD adoption. NeeS submissions are PDF-based collections organized according to CTD structure but without the XML backbone that defines eCTD. Navigation relies on a PDF table of contents with embedded hyperlinks rather than structured metadata.

Origins: How NeeS Served as the Bridge Format

When regulatory agencies began transitioning from paper to electronic submissions in the early 2000s, the full eCTD specification presented significant implementation challenges for both sponsors and agencies. NeeS emerged as a practical intermediate step—allowing electronic submission without requiring the technical infrastructure for XML processing.

The European Medicines Agency (EMA) was notably instrumental in defining NeeS specifications, recognizing that many sponsors and national competent authorities needed time to build eCTD capabilities. NeeS allowed the regulatory ecosystem to gain experience with electronic document management while the industry matured its eCTD publishing workflows.

However, NeeS was always intended as transitional. Without structured metadata and lifecycle management, agencies faced increasing difficulties managing growing submission volumes. This limitation drove the accelerated eCTD mandates we see today.

Structural Differences: eCTD vs NeeS Architecture

The fundamental distinction between eCTD and NeeS lies in their technical architecture. Understanding these differences is essential for evaluating migration requirements and long-term submission strategy.

eCTD Structure

eCTD submissions consist of three primary components:

1. XML Backbone: Machine-readable files that define the submission structure, document locations, and lifecycle operations. The backbone enables automated processing by health authority systems.
2. Leaf Documents: Individual content files (typically PDF, but also XML for structured data) referenced by the backbone. Each leaf has unique identifiers enabling precise lifecycle management.
3. Lifecycle Operations: The backbone specifies whether each document is new, replaces a previous version, appends to existing content, or deletes prior submissions. This creates a complete version history across sequences.

NeeS Structure

NeeS submissions lack the XML backbone entirely:

• PDF-Based Organization: Documents are organized in folder structures mirroring CTD modules, but relationships are implicit rather than explicitly defined.
• Table of Contents Navigation: A master PDF with hyperlinks provides navigation, requiring manual maintenance.
• No Lifecycle Operations: Each submission is essentially standalone. Tracking changes across submissions requires manual comparison.

Side-by-Side Comparison: eCTD vs NeeS

Health Authority Acceptance: Current Landscape

Agencies Requiring eCTD

The following major health authorities mandate eCTD for most or all submission types:

• FDA (United States): eCTD mandatory for all NDA, ANDA, BLA, and IND submissions
• EMA (European Union): eCTD mandatory for centralized procedures; national competent authorities have aligned requirements
• Health Canada: eCTD mandatory for all drug submissions
• PMDA (Japan): eCTD mandatory for new drug applications
• Swissmedic (Switzerland): eCTD mandatory
• MHRA (United Kingdom): eCTD mandatory post-Brexit transition
• GCC (Gulf Cooperation Council): eCTD required for centralized submissions
• ANVISA (Brazil): eCTD required for new registrations
• TGA (Australia): eCTD mandatory for prescription medicines

Where NeeS May Still Be Accepted

NeeS acceptance is increasingly limited to:

• Legacy products under renewal in certain European national procedures
• Some emerging market agencies still building eCTD processing capabilities
• Specific variation types in transitional regulatory environments

When NeeS Is Acceptable—and When It Isn’t

The practical guidance for eCTD vs NeeS decisions is straightforward: default to eCTD unless a specific regulatory pathway explicitly requires or permits NeeS.

NeeS may still be acceptable for:

• Products grandfathered under legacy procedures in certain EU member states
• Markets with documented NeeS acceptance and no eCTD mandate
• Specific submission types where the agency has confirmed NeeS acceptance in writing

NeeS is not acceptable for:

• Any submission to FDA, Health Canada, PMDA, or TGA
• New marketing authorization applications in the EU (centralized or decentralized)
• Any product where future lifecycle management will be required
• Submissions to agencies with published eCTD mandates

Migration: Moving from NeeS to eCTD

For organizations maintaining legacy NeeS dossiers, migration to eCTD is increasingly urgent. A structured migration approach includes:

1. Content Audit: Inventory all NeeS submissions and identify current regulatory status, pending variations, and lifecycle requirements.
2. Document Remediation: Review PDFs for eCTD compliance (bookmarks, hyperlinks, fonts, metadata). Many NeeS documents require updates to meet eCTD validation requirements.
3. Structure Conversion: Map existing content to eCTD granularity. NeeS documents often combine content that should be separate leaves in eCTD.
4. Validation: Run preflight and final validation against target agency criteria before submission.
5. Baseline Submission: Publish the initial eCTD sequence establishing the product’s electronic lifecycle with the health authority.

Cost and Effort Tradeoffs

While NeeS appears simpler initially, the long-term economics favor eCTD:

NeeS Hidden Costs:

• Manual tracking of document versions across submissions
• Increased review cycles due to navigation difficulties
• Compliance risk as agencies phase out acceptance
• Eventual forced migration under time pressure

eCTD Investment Value:

• Automated lifecycle management reduces ongoing effort
• Validation catches errors before submission
• Consistent format across global markets
• Future-proof compliance posture

The Future: NeeS Phase-Out Timelines

The trajectory is clear: NeeS is being systematically retired. The EMA has progressively tightened eCTD requirements, and national competent authorities across Europe have aligned their mandates. Emerging markets that previously accepted NeeS are implementing eCTD requirements as they modernize regulatory infrastructure.

Organizations still maintaining NeeS workflows should plan migration within the next 12-24 months to avoid compliance disruptions.

How Modern Publishing Tools Handle the Transition

During the transition period, regulatory teams need publishing solutions that can manage both formats while prioritizing eCTD readiness. DnXT Solutions addresses this through:

• Unified publishing engine: Generate eCTD submissions with full validation for FDA, EMA, Health Canada, PMDA, and other major agencies
• Integrated validation: Preflight and final validation against current agency criteria, catching issues before submission
• AI-powered document classification: Automatically map content to correct eCTD sections, accelerating both new submissions and NeeS-to-eCTD migration
• Lifecycle management: Track all sequences and operations across your product portfolio
• 12-week implementation: Purpose-built cloud architecture enables rapid deployment compared to legacy RIM platforms

Frequently Asked Questions

Can I convert an existing NeeS dossier to eCTD?

Yes, but it requires more than file format conversion. NeeS documents often need restructuring to meet eCTD granularity requirements, and all PDFs must be validated against eCTD technical specifications. A baseline eCTD sequence then establishes the product’s electronic lifecycle with the agency.

What happens if I submit NeeS to an agency that requires eCTD?

The submission will be rejected at the gateway or during technical validation. This results in delays, potential refusal to file, and the need to resubmit in the correct format—often under compressed timelines.

Is eCTD more expensive to produce than NeeS?

Initial eCTD setup requires investment in publishing tools and training. However, lifecycle management efficiencies, reduced error rates, and global format harmonization typically deliver lower total cost over the product lifecycle. The comparison of eCTD vs NeeS increasingly favors eCTD on both compliance and economic grounds.

How long does NeeS-to-eCTD migration take?

Timeline depends on dossier complexity, document quality, and available resources. A straightforward product with well-maintained documents might convert in 4-6 weeks. Complex dossiers with extensive documentation or quality issues may require 3-6 months.

Will NeeS ever be completely retired?

All indications point to eventual complete phase-out. While specific timelines vary by region, no major health authority is expanding NeeS acceptance. Regulatory teams should treat NeeS as a legacy format with a limited remaining lifespan.