eCTD Submissions – EU & UK Electronic Dossier Management

Seamless compilation, validation, and lifecycle management of electronic Common Technical Document (eCTD) dossiers for medicinal products in Europe and the United Kingdom. Pharmafile provides both expert eCTD publishing and technical submission services (handling dossier assembly, electronic formatting, and gateway transmission) and end-to-end regulatory submission management (coordinating content preparation, managing eCTD lifecycles, and interfacing with authorities). We support all types of regulatory procedures Centralised, Decentralised (DCP), Mutual Recognition (MRP), National, and UK national ensuring your applications and variations are submitted in fully compliant eCTD format. The HMA eSubmission Roadmap (Annex 2, adopted by the eSubmission Expert Group on 18 October 2019) sets out the mandatory implementation milestones: eCTD has been required for all new DCP applications since 1 July 2015, for new MRP applications since 1 January 2017, and for all regulatory activities (variations, renewals, PSURs, ASMFs, etc.) in DCP/MRP procedures since 1 January 2018. Mandatory eCTD for new marketing authorisation applications in purely national procedures took effect on 1 July 2018, and for all regulatory activities in national procedures from 1 January 2019. The UK MHRA likewise requires eCTD format for all submissions via the MHRA Submissions Platform. Our robust processes ensure your eCTD sequences pass technical validation on the first attempt, are submitted via the correct portals, and maintain a flawless regulatory lifecycle  so you can focus on strategy while we handle the complexities of electronic submissions.

Who This Service Is For

This service is ideal for:

  • Pharmaceutical & Biotech Companies (Human & Veterinary): MA Holders or applicants who need to submit electronic dossiers for human or veterinary medicines in the EU or UK but lack in-house eCTD expertise or capacity. This includes small and mid-sized companies navigating their first eCTD submission (e.g. a startup biotech filing its maiden MAA in the EU, or a generic company moving from paper to eCTD format for a national licence) as well as larger companies that need to temporarily scale up their publishing resources for an influx of regulatory activities. The Annex 2 to the HMA eSubmission Roadmap applies to products for human use including ASMFs, since veterinary products are handled in another stream. For veterinary submissions, where the VNeeS format applies, we provide analogous electronic submission services. If you are overwhelmed by the technical demands of eCTD (specialised tools, XML backbone, PDF specifications, hyperlinking, etc.), we act as your external publishing department, ensuring every document is correctly formatted and every sequence is properly built and validated.
  • Companies Managing Complex or High-Volume Dossier Changes: Firms facing numerous or complex regulatory submissions such as a series of Type II variations across multiple markets, line extensions, or a large portfolio migrating to eCTD  who require additional support to compile and track these sequences without error. We assist companies that are integrating new products (through acquisitions or licensing deals) by preparing baseline eCTD submissions where beneficial. Baselines are recommended but not required — there is a clear agreement among the NCAs on this point. A baseline can be helpful to consolidate the dossier (especially Module 3) in eCTD format before new changes are added. We also help manage complicated lifecycle scenarios, like products with multiple related dossiers (common global dossiers requiring different regional Module 1s), and large safety or quality updates that involve multiple documents and data sets.
  • Regulatory Affairs Teams Seeking Quality Assurance or Compliance Auditing: Organisations that handle eCTD in-house but want an expert review to avoid technical validation failures or authority rejections. Even seasoned RA teams sometimes encounter eCTD lifecycle errors (e.g. incorrect sequence numbering, broken hyperlinks, missing operation attributes, or failing to include a required baseline of data), especially during time-critical submissions. Our specialists audit draft sequences before submission using stringent validation tools and the latest health authority checklists, identifying and correcting issues that would otherwise lead to a technical rejection. For example, we ensure that any modification of an eCTD application is reflected in a new eCTD sequence replacement sequences of a previously submitted eCTD application are not acceptable. By proactively fine-tuning your eCTD sequences, we give you confidence that regulators will accept and process them without technical queries.
  • Companies Without In-House eCTD Infrastructure: Some MAHs, including those in niche markets or semi-virtual companies, do not have dedicated eCTD software or publishing teams. We provide a full infrastructure for them: using validated eCTD publishing tools to compile submissions on their behalf, managing user accounts for authority portals, and acting as their liaison with agency technical staff. This service is also valuable for companies in markets where eCTD adoption has recently become mandatory the HMA roadmap notes that at the time of the revision, approximately half of all new MAAs for national procedures were already submitted in eCTD format in the EU, with some NCAs already at 100%. To ensure harmonisation, all types of national deviations to the eCTD format must be avoided and EU specifications and guidelines should be adhered to. We ensure compliance with these harmonised EU specifications so regulators find everything in order.

This service may not be needed by: Companies that already have a fully-staffed, expert regulatory operations team with established eCTD systems and a flawless track record of electronic submissions. However, even such companies often leverage our support during peak workload times or to double-check high-stakes submissions.

Regulatory Challenges We Address

Navigating Mandatory eCTD Requirements & Deadlines: The regulatory landscape has made eCTD the norm and the legally required format  for submissions in both the EU and UK. All dossiers in the Centralised Procedure (CP) are handled in eCTD format this step is considered completed. Applications for marketing authorisation within the Decentralised Procedure (DCP) have been submitted in eCTD format since 1 July 2015, and no major problems with this step have been identified. Applications within the Mutual Recognition Procedure (MRP) have been submitted in eCTD format since 1 January 2017. Since 1 January 2018, eCTD has been mandatory for all submission types for DCP/MRP dossiers including variations, renewals, PSURs, ASMFs and so on. Purely national procedures followed on 1 July 2018 for new MAAs and 1 January 2019 for all other submission types. The UK’s MHRA has likewise mandated eCTD format for national submissions and uses an electronic submissions portal for all application types. We help companies keep track of these requirements and ensure no submission is made in an outdated format. For instance, if you have an existing product still in NeeS format, we plan a controlled switch to eCTD at the next appropriate regulatory activity the change to eCTD format for a purely national product dossier should normally be done at the start of a new regulatory activity (e.g. a new variation application), so ongoing procedures should be continued in the same format as the starting submission. Once a format change to eCTD is made, all following submissions for that dossier should be handled in eCTD format.

 

Technical Validation & Rejection Risks: One of the biggest challenges is passing the stringent technical validations that agencies run on every eCTD sequence. These automated checks will flag everything from a single missing file or broken hyperlink to more subtle errors like incorrect attributes in the XML backbone. A sequence that fails validation is typically rejected, meaning the regulatory timeline is halted until a corrected sequence is provided. We eliminate this risk by rigorously validating each sequence with up-to-date tools before submission, catching errors such as:

 

  • Wrong or inconsistent sequence numbering or lifecycle links: We verify that each document is correctly set as new, replace, or delete, and that sequences follow the continuity. For example, if a format change to eCTD was done by the start of a PSUSA and sequence 0000 was sent to the PSUR repository only, the MAH should clearly state in the cover letter to the NCA that the earlier sequences were submitted to the PSUR repository only, and preferably provide a copy of those sequences to the NCA together with the first next eCTD sequence for another regulatory activity.
  • Document naming and placement issues: We ensure all files are in the proper modules and use acceptable naming conventions. Our team stays informed on the latest eCTD Module 1 guidance for both EU and UK. The MHRA, for example, now expects certain IRP-specific documents in specific m1-additional-data subfolders — such as the global regulatory history, justification for UK/GB indications, and adverse drug reaction justifications.
  • PDF formatting problems: We check that PDFs meet required specifications (bookmarks, fonts embedded, page orientation, maximum file size, no active content, etc.). We also verify that external and internal hyperlinks are functional and only point to allowed locations within the eCTD. By resolving these issues upfront, we save you from the embarrassment and delay of having authorities refuse your sequence due to technical errors.
  • Lifecycle Management & Version Control: eCTD is not a one-off submission format; it is a continuously evolving dossier. Managing the eCTD lifecycle preserving the integrity of cumulative sequences and ensuring reviewers have a clear view of current vs superseded content is a nuanced task. Mistakes here include failing to carry forward a change from one procedure to the next, or mis-sequencing submissions. The MHRA explicitly states that where applications are amended during evaluation, a new or consolidated eCTD sequence must be provided to maintain the eCTD lifecycle, and that replacement sequences are not acceptable. Any modification of an eCTD application must be reflected in a new eCTD sequence, and all subsequent sequences should be submitted via the MHRA Submissions Platform. We adhere to that strictly  we never advise sending a corrected document outside the eCTD context; instead, we compile a corrective sequence to preserve the history. Our approach prevents the chaos of having an “out-of-band” document that isn’t reflected in the official dossier.
  • Submission Logistics & Multi-Platform Coordination: With multiple gateways and platforms (EMA’s Gateway/Web Client for centralised procedures, the Common European Submission Portal (CESP) for many MRP/DCP and national submissions, and the MHRA Submissions Platform for UK), it can be challenging to manage the mechanics of submission especially when deadlines are fixed. We address this by handling all the technical submission steps: we prepare the final signed eCTD sequence, log into the appropriate portal well ahead of time, upload and submit it, and then monitor for successful receipt and validation acknowledgments. For the UK, submissions must be made through the MHRA Submissions Platform from the Human Medicines tab  this is the only acceptable route. Our team also stays alert for portal downtimes or technical notices and adjusts plans to avoid any compliance breach.
  • Transitional Cases and Special Scenarios: There are specific transitional challenges for products moving from older formats to eCTD. Even though the mandatory eCTD in DCP/MRP does apply also to ongoing regulatory activities, this is not the situation for mandatory eCTD in purely national procedures where the format change has not yet been done ongoing procedures should be continued in the same format as the starting submission, as long as no new regulatory activity is started in parallel after 1 January 2019. For PSUSA submissions specifically, the national product dossier format change to eCTD should preferably not be done at the time of a PSUSA submission  non-eCTD is accepted until the dossier format is changed to eCTD at the submission of another new regulatory activity submitted to the NCA directly. We navigate these nuances on your behalf, ensuring each product transitions at the appropriate time without disrupting ongoing procedures.

What Regulators Expect

Regulatory agencies in the EU and UK expect flawless electronic submissions that comply with both technical and process requirements:

  • Adherence to eCTD Format by Mandated Dates: Fundamentally, authorities expect all applications to be in the correct format by the mandated dates. All submission types for DCP/MRP dossiers  variations, renewals, PSURs, ASMFs  must be in eCTD since 1 January 2018. The requirement is applicable for all MRP submissions from that date whatever the current format of the concerned dossier. For purely national procedures, eCTD format has been mandatory for new national MAAs since 1 July 2018 and for all other submission types from 1 January 2019. The UK MHRA expects all marketing authorisation applications and variations to be in eCTD. Regulators also expect that the content is placed in the correct CTD modules and sections, following ICH and regional guidance. For the UK’s International Recognition Procedure, all modules of the eCTD should be in EU format (Modules 1–5), with UK-specific information included in Module 1, and eCTD M2–M5 should include all relevant information required for the MHRA application, complying with any EU regional requirements of the ICH eCTD standards.
  • Proper Lifecycle Management and Adherence to Guidelines: Authorities expect applicants to maintain a coherent eCTD lifecycle meaning each new sequence should build on the previous ones in a consistent chain. The MHRA explicitly states that replacement sequences of a previously submitted eCTD application are not acceptable  any modification of an eCTD application must be reflected in a new eCTD sequence. When a format change to eCTD is made for a product dossier, all following submissions for that dossier should be handled in eCTD format. Authorities also expect companies to comply with harmonised technical guidance across the network: all types of national deviations to the eCTD format must be avoided and EU specifications and guidelines should be adhered to. Otherwise, benefits of using eCTD in regard to harmonised processing, simplification of dossier management, and quality improvement cannot be achieved.
  • Technical Validity & Completeness: Before a submission is accepted for review, it undergoes a technical validation by the authority. Regulators expect a technically valid eCTD sequence on first submission. This includes:
    • Accurate XML backbone and metadata: The eCTD XML must correctly describe the sequence contents, with all required attributes present and correct. For the UK, the MHRA requires specific information in both the cover letter area and in m1-additional-data to facilitate processing of the application. Supporting data relevant to the application should not be placed in m1-additional-data; wherever possible, it should be placed in the relevant eCTD section. [
    • All files present and virus-free: No missing files (every leaf referenced in the XML must be included) and no unacceptable file types.
    • Valid hyperlinking and bookmarks: Long documents require bookmarks, and cross-references must use relative hyperlinks within the eCTD.
    • No extraneous or disallowed content: Documents not meant for the authorities must be kept out of the eCTD or placed in “Working Documents” outside of the eCTD structure where appropriate. The MHRA notes that there are areas where it is useful to provide documents in Word format — where appropriate, these should be provided in ‘Working Documents’ outside of the eCTD structure, following the same or similar nomenclature to any PDF documents provided in the relevant section. Word versions of UK/GB proposed SmPC, label and leaflet are specifically required by the MHRA.
  • Baselines  Recommended but Not Required: Regulators do not demand mandatory baselines when transitioning to eCTD. No baseline submissions are required; however, it is recommended to consider a submission of baseline for Module 3 in which case the relevant guidance should be followed. There is a clear agreement among the NCAs that baselines are recommended but not required  the applicant decides whether to submit a baseline or not. That said, a well-prepared baseline can smooth future reviews, and we advise clients on when this step adds value.
  • Efficient Use of Portals and Timely Submission: Regulators expect applicants to use the designated electronic submission portals and meet deadline expectations. For the UK, all submissions must go through the MHRA Submissions Platform this is the only acceptable route for IRP submissions, and the same portal is used for post-authorisation applications. For EU procedures, CESP or the EMA Gateway serves as the primary portal. Submitting to the wrong portal or missing a distribution to a Concerned Member State can delay or invalidate a procedure.
  • Simplified Registrations  Optional Timelines: For registrations according to Article 14 or 16a of Directive 2001/83/EC (simplified registration procedure either for homeopathic medicinal products or traditional herbal medicinal products), the timelines of the eSubmission Roadmap are considered optional companies should refer to regional guidance of the member states.

Our eCTD Submissions Delivery Model

Our approach to eCTD submission management is structured, end-to-end, and quality-driven, ensuring every step from planning to archival is handled expertly.

eCTD Strategy & Submission Planning

At the outset of any project or product lifecycle stage, we formulate a clear strategy for your electronic submissions:

  • Regulatory Submission Roadmap: We develop a submission roadmap that aligns with your regulatory strategy and timelines. For a new MAA, this means mapping out all anticipated sequences (initial MAA, expected clock-stop responses, potential post-opinion updates, etc.). For an existing product, we review its current format and lifecycle: is it already in eCTD? If not, we schedule the format transition. If a product approved years ago in NeeS or paper needs to move to eCTD, we advise doing so at the next major variation or renewal  the format change should normally be done at the start of a new regulatory activity. We also examine if a baseline sequence would be beneficial — while not mandatory, a baseline can be helpful to consolidate the dossier (especially Module 3). Our plan considers these factors and includes buffer time for quality control and any unforeseen technical issues.
  • Content Readiness & Interdepartmental Coordination: eCTD submission is the final assembly of many parts, so we coordinate with your regulatory, CMC, clinical, and PV teams (or with external contributors like ASMF holders or translation vendors) to make sure all necessary documents will be ready in the correct format. We provide contributors with templates and guidelines for eCTD-compatible documents. We also plan for language versions: if your procedure requires multiple languages (as in MRP or DCP), we schedule the translation and QC of product information so that the eCTD sequence includes all required language PDFs in Module 1. Our planning extends to technical requirements: if an active substance master file (ASMF) is part of the submission, mandatory use of eCTD is also applicable for ASMF submissions used for marketing authorisation for all types of applications in all procedure types  the eCTD ASMF dossier remains a standalone dossier and is distinct from the marketing authorisation dossier and lifecycle. We liaise with the ASMF holder to ensure their separate eCTD (applicant’s and restricted parts) is submitted in a timely manner and our main dossier references it correctly.
  • Validation Strategy & Risk Mitigation: In planning, we outline a validation strategy  how we will test the sequence internally and what checks the health authority will perform. For high-stakes submissions, we may do a trial compile of an earlier draft to catch structural issues well before the deadline. We identify anything likely to trigger a technical question from the authority and plan how to mitigate it. For example, if a prior sequence for a PSUR was only submitted to the EU PSUR Repository and not to NCAs, we plan to provide that sequence to NCAs with the next variation  the MAH should preferably provide a copy of the PSUR submission sequences to the NCA together with the first next eCTD sequence sent to the NCA for another regulatory activity, using the next sequential number and taking the previously submitted PSUR sequences into account.

Dossier Assembly, Publishing & Validation

We take charge of the hands-on process of building your electronic dossier, utilising specialised software and rigorous quality checks:

  • CTD Content Compilation: Our regulatory operations specialists gather all final documents (Module 1 forms and cover letters, quality/clinical/non-clinical Modules, product information, etc.) and ensure they are in the correct formats for eCTD. This includes converting files to PDF/A where appropriate, applying consistent naming conventions, and inserting metadata. We verify that each document is in its designated CTD section. Our Pharmafile team has extensive experience in this area  internal processes show that once PSUR documentation is finalised, the PSUR writer passes the PSUR to the RA department for preparation of the eCTD submission, demonstrating the seamless integration of content creation and eCTD publishing within our workflow.
  • Hyperlinking and Bookmarking: We enhance the navigability of the dossier by adding electronic bookmarks and hyperlinks in lengthy documents, as per guidelines. Regulators appreciate well-bookmarked documents, as it speeds their review. All hyperlinks are tested to ensure they are relative (i.e., they work within the eCTD context and do not point to an external path) and unbroken.
  • Lifecycle Integration & Sequence Building: We incorporate the new submission into the existing eCTD lifecycle by using the appropriate “operation attributes” for each file (new, replace, append, delete). Every sequence we build is assigned the next incremental sequence number and we maintain a master log of sequence history. If a baseline is being submitted, we clearly identify it as sequence 0000  a baseline submission refers to submission of all current valid documents along with a statement that the content has not changed, only the format. Our expertise here prevents the common error of lifecycle mismatch  for instance, a scenario where the agency sees two “current” versions of a file because an applicant mistakenly used the wrong operation attribute.
  • Technical Validation & QC: Before dispatch, we run the compiled eCTD through a comprehensive validation check using industry-standard tools configured to EMA/MHRA rules. This catches technical issues such as: missing leaf files, errors in the XML structure, invalid PDF versions, oversized submissions, and more. Our quality control process is four-eye: one publisher compiles the sequence and a second senior publisher reviews the entire structure and performs a test import to emulate the authority’s experience. Only once the sequence passes 100% of the criteria do we package it for submission. The MHRA’s explicit requirement that replacement sequences are not acceptable means there is no second chance for a botched initial upload our rigorous QC ensures this scenario does not arise.

Lifecycle Management & Technical Maintenance

Our service extends beyond one-time submission we provide ongoing support to maintain the eCTD dossier throughout the product’s lifecycle:

  • Centralised Tracking of Dossier Status: We maintain a live eCTD dossier tracker for each product, recording every sequence number, type of submission, date, and regulatory outcome. This tracker is invaluable during inspections or internal audits to demonstrate control over regulatory activities. It also avoids mistakes like preparing a sequence on an outdated baseline or referencing a superseded version of a document.
  • Change Control and Version Harmonisation: In complex scenarios, especially for products approved via multiple routes (say a Centralised EU licence and separate UK licence post-Brexit), keeping content harmonised is challenging. We help by implementing a regulatory change control process: every time a change is introduced in one region’s eCTD, we evaluate if and when it needs to be mirrored in another. The MHRA requires that eCTD M2–M5 should include all relevant information required for the MHRA application and will form the baseline of the required information as approved by the Reference Regulator at the MHRA submission date this is particularly important when aligning EU and UK dossiers post-Brexit. Our comprehensive approach minimises discrepancies that could raise questions.
  • Responding to Authority Technical Queries: We stand ready to respond to any technical or structural questions from authorities. Because we prepared the dossier, we can quickly provide the explanation or, if needed, a corrected sequence. Our familiarity with authority validation logs and error codes means we can interpret regulator feedback swiftly and provide corrective action within hours.

Inspections, Deficiencies & Common eCTD Pitfalls

Thanks to our deep experience, we help you avoid (and if needed, handle) the frequent pitfalls and inspection findings related to electronic submissions:

  • Avoiding Common Deficiencies: A poorly managed eCTD can attract negative attention from regulators. Examples of issues we pre-empt include:
    • Inconsistencies between sequences: e.g. the submitted cover letter says one thing but the eCTD metadata says another, or a file is updated in one sequence but the corresponding section elsewhere is not updated. We maintain consistency by cross-reviewing every change in context.
    • Unreadable or un-navigable submissions: We ensure high quality PDFs and thorough bookmarking/hyperlinks. Before any submission, we open the compiled sequence in an eCTD viewer to simulate the regulator’s perspective.
    • Misplaced documents: We strictly follow the CTD structure and regulators’ guidance on where to put each document. Supporting data relevant to the application should not be placed in m1-additional-data; wherever possible, it should be placed in the relevant eCTD section.
  • Regulatory Inspections & Audits: In GMP or PV inspections, inspectors sometimes extend their review to regulatory compliance aspects including how you manage your dossiers and variations. With our service, you will have a clear audit trail through the eCTD: every change is documented by sequence number and date. By having us manage the eCTD, you gain not only compliance but also transparency.
  • Training & Continuous Improvement: We provide training to your team on best practices in electronic submissions. We also perform post-project reviews on large submissions internally we analyse whether there were any validation warnings or minor authority comments about the submission structure, and we feed those learnings into our processes.
  • Emergency Troubleshooting: In the unlikely event that a serious issue arises for example, if a submission was made and a critical document was unintentionally omitted  we act immediately to rectify it. We would contact the authority’s helpdesk within hours, explain the situation, and provide a corrective sequence or solution as appropriate. We conduct a root cause analysis on our side to prevent reoccurrence.

Jurisdictions Covered

Our eCTD submission services cover regulatory requirements in all European Economic Area (EEA) countries and the United Kingdom, and we align with global standards:

  • European Union & EEA: We handle eCTD dossiers for all EU member states plus EEA affiliates (Norway, Iceland, Liechtenstein). This includes procedures via EMA (centralised) and via CMDh/CMDv (DCP/MRP), as well as purely national filings. We strictly follow the EU eCTD specification and the latest EMA and HMA guidance the HMA eSubmission Roadmap provides the authoritative milestones, with mandatory eCTD for centralised products (completed), DCP since 1 July 2015, MRP since 1 January 2017, all DCP/MRP activities since 1 January 2018, and national procedures from mid-2018 / early-2019. The requirement from 1 January 2017 also includes Repeat Use Procedures (RUP) and so-called duplicates of new or previously submitted DCP or MRP applications. We are experienced with the CESP portal and know the few country-specific quirks that remain. For veterinary submissions, where the VNeeS format is used instead of eCTD, we provide analogous electronic submission services in case an ASMF dossier in eCTD format is to be used for a veterinary submission, the document “Exceptions to the VNeeS format” should be referred to. Depending on the size and the business model of a pharmaceutical company there are major differences in how regulatory affairs activities are organised a more centralised approach can be followed when eCTD capabilities are associated with a European headquarter, while a more decentralised approach is usually implemented when eCTD capabilities are available at affiliates. We accommodate both models.
  • United Kingdom: We have been deeply involved in UK submissions both pre- and post-Brexit. The UK’s MHRA accepts eCTD for human medicines, with all modules in EU format (Modules 15) and UK-specific information included in Module 1. Post-1 January 2021, the UK largely mirrors the EU’s eCTD requirements for human medicines but with some procedural differences for example, using the MHRA Submissions Platform as the only acceptable route. The MHRA’s eCTD guidance (updated 21 January 2026) reiterates that consolidated sequences should be used to maintain lifecycle integrity for any changes during review and that replacement sequences are not acceptable. We also manage sequences for the Innovative Licensing pathways (like IRP) which have additional Module 1 document expectations  the MHRA prescribes exactly how to include reference regulator documents and where to put them in the eCTD structure, including assessment reports, approval letters, and global regulatory history tables in designated subfolders.
  • Other International Regions (as needed): While our primary remit is EU and UK, the eCTD has become a global standard. We are experienced with submitting to other ICH regions which use either eCTD or very similar formats. By using one provider for multiple regions, you reduce the chance of discrepancies and maximise efficiency.

Typical Timelines

The timeline for eCTD preparation and submission can vary depending on the size of the dossier and the complexity of the procedure. Below is an approximate guide for key eCTD-related activities (assuming the core documents are ready; these timelines are for the publishing and submission steps). Actual durations should be confirmed based on project specifics:

Activity Typical Timeline Notes
Initial eCTD Publishing Setup (for new dossier) 1–2 weeks Setting up eCTD metadata (product, substance, manufacturers) in publishing software, confirming Module 1 specifics for all target countries, and creating templates for lifecycle management. If converting an existing dossier from NeeS/paper to eCTD, add ~1–2 extra weeks to handle baseline sequence preparation (if needed) and content migration.
Single Sequence Compilation & Validation (Standard Variation or Response) 2–5 business days per sequence Once all input documents are final, a straightforward sequence typically takes a couple of days to compile, hyperlink/bookmark, and validate. More complex sequences (e.g. an initial MAA with hundreds of files) may take 1–2 weeks to prepare thoroughly.
Simultaneous Multi-Country Submission (via CESP or Gateway) Same day as compile completion Using CESP or EMA Gateway does not add significant time once submitted, the files are distributed to agencies within hours. We typically plan submissions early in the working day to allow time for any immediate troubleshooting.
Authority Technical Validation & Acknowledgement 1–3 business days after submission Many agencies provide automated acknowledgments within minutes or hours. Some national agencies may take a day or two to send human-confirmed acknowledgments.
Overall Turnaround (Document Finalisation to Submission) ~1–2 weeks for moderate content changes For larger filings (initial MAAs), we recommend starting publishing activities ~8 weeks before the target submission date, overlapping with final proofreading of Module texts.
Life-Cycle Ongoing Management Continuous We maintain and update the eCTD dossier throughout the product’s life. Products typically have sequences for PSURs (frequency varies) and multiple variations per year.

Note: Starting eCTD activities early is crucial. For an initial MAA, we often begin assembly and validation of draft sequences ~2 months ahead, performing a dry-run validation to catch issues. We recommend building a 3–5 day buffer before official deadlines for any major submission. Verify all estimates against current internal performance data before publication.

Common Mistakes We Help You Avoid

Common Mistakes We Help You Avoid

Our rigorous approach and experience help eliminate numerous frequent mistakes in eCTD submissions:

  • Submitting in the Wrong Format: A common error is sending a national variation in NeeS or PDF when eCTD was required. Since 1 January 2019, eCTD format has been mandatory for all submission types in purely national procedures. This usually results in authorities rejecting the submission outright. We verify the required format for every submission before proceeding.
  • Missing or Mismatched Documents: A frequent error is failing to include all necessary documents, or including inconsistent versions. For instance, submitting an updated SmPC in Module 1 but forgetting to update the corresponding section of the Clinical Overview leading to a mismatch. We use detailed content checklists (tailored per procedure and country) to ensure nothing is overlooked. The MHRA, for example, requires specific documents in designated locations for IRP applications: assessment reports in m1-additional-data, eligibility forms in m1-eu-12-form, and clinical trial inspection reports in m1-eu-19. Missing any of these triggers a deficiency.
  • Incorrect Lifecycle Operations: Another common pitfall is misusing eCTD lifecycle operations for example, unintentionally “adding” a new document that should have replaced an old one, resulting in duplicate content. We systematically apply lifecycle operators and verify their effect by opening the compiled sequence in an eCTD viewer before submission.
  • Ignoring Baseline Recommendations: While not mandatory, baseline submissions are recommended by agencies when transitioning to eCTD  there is a clear agreement among the NCAs that baselines are recommended but not required, and the applicant decides whether to submit a baseline or not. A mistake some companies make is ignoring this advice and submitting a small change as the first eCTD sequence on a product with a long paper history. The result can be an eCTD that contains only fragments of Module 3, forcing assessors to hunt through old archives for context.
  • Mishandling the NeeS-to-eCTD Transition: Companies sometimes attempt to change the dossier format to eCTD at an inappropriate time for instance, at the time of a PSUSA submission to the PSUR Repository. The CMDh guidance is clear: preferably, the national product dossier format change to eCTD should not be done at the time of a PSUSA submission; non-eCTD is accepted until the dossier format is changed to eCTD at the submission of another new regulatory activity submitted to the NCA directly. We prevent this mistake by carefully timing the format conversion to align with the next appropriate regulatory activity.
  • Failed Portal Submission or Late Dispatch: A surprisingly common error is missing a regulatory deadline because of technical issues e.g. waiting until the last minute to upload to the portal and then encountering a slow connection or portal maintenance. By entrusting us, you avoid these. We plan portal uploads with time to spare and always confirm submission completion.
  • Inadequate Archiving and Retrieval: After a submission is done, some companies fail to adequately archive the eCTD or store it in a way that’s easily retrievable. We maintain archives of all sequences (securely stored with version control). Even if you discontinue our services, we provide you with a full copy of the cumulative eCTD dossier.

Yes  for human medicines in the EU and UK, eCTD format is effectively mandatory for nearly all regulatory submissions. In the EU, eCTD has been required for centrally authorised products since that step was completed, for all new DCP applications since July 2015 and MRP since January 2017, and for all submission types (variations, renewals, PSURs, etc.) in DCP/MRP procedures since January 2018. Purely national submissions must be in eCTD for new MAAs since July 2018 and for all regulatory activities since January 2019. The UK follows the same practice. For registrations under simplified schemes (homeopathic or traditional herbal), the eSubmission Roadmap timelines are considered optional — companies should refer to regional guidance of the member states.

When you initiate a new regulatory activity on an existing product, you will likely need to switch to eCTD at that point (if the product is within scope of the eCTD requirements). The change to eCTD format should normally be done at the start of a new regulatory activity (e.g. a new variation application), so ongoing procedures should be continued in the same format as the starting submission. Once a format change is made, all following submissions for that dossier should be handled in eCTD format. You do not need to resubmit all historical data at once  baselines are recommended but not required, and the applicant decides whether to submit one or not. A baseline can establish a clean starting point, especially for Module 3

We provide a turn-key eCTD solution covering: Planning (setting up the eCTD backbone with all product metadata, advising on document preparation); Document processing (formatting PDFs to meet technical requirements, adding bookmarks and headings); Building sequences (placing documents into the correct CTD structure, assigning lifecycle attributes); Technical validation (running the compiled sequence through validation software to catch errors); Submission (uploading the sequence via the appropriate portal EMA Gateway, CESP, MHRA  and ensuring it’s successfully received); Lifecycle management (tracking sequence numbers and ensuring consistency across submissions); and Archiving & support (maintaining an archive and assisting in any queries or audits related to your dossier).

We use a combination of advanced validation tools and manual quality control. Before we submit any sequence, we run it through an industry-standard eCTD validator configured to EMA/MHRA rules. This tool checks hundreds of criteria. We treat any error as unacceptable and fix it. After tool-based validation, our publishers perform a manual review: we open the sequence exactly as an assessor would, to confirm everything looks right. Only when we are fully satisfied do we submit. This rigorous process ensures compliance with the requirement that any modification must be reflected in a new sequence since replacement sequences are not acceptable, there is no room for error in the initial submission.

Common mistakes include: submitting in the wrong format (e.g. sending a national variation in NeeS when eCTD was required since January 2019); technical dossier errors (broken hyperlinks, missing files, poor-quality scanned documents); lifecycle mistakes (not using the correct sequence number, including superseded content); metadata and envelope mistakes (not updating the sequence description or related sequence references); and late submissions due to portal issues. We systematically prevent these errors through our robust QC and process management.

Related Services & Resources

Our eCTD Submissions service works in concert with many of our other offerings, ensuring that the technical act of submission is integrated with the broader regulatory and development process:

  • Regulatory Affairs Management: The content that goes into an eCTD comes from robust regulatory work. Our Regulatory Affairs Management team prepares the scientific and regulatory documents (Module 2 summaries, Module 3, 4, 5 content, responses to questions, etc.) which our eCTD team then compiles. Close collaboration between the RA strategists and eCTD publishers ensures that what is promised in regulatory strategy is delivered exactly. (See our Regulatory Affairs Management page for how we manage overall regulatory strategy and content preparation.)
  • Pharmacovigilance & PSUR Services: Electronic submission extends to pharmacovigilance documents. Periodic Safety Update Reports (PSURs) must often be submitted in eCTD format. Our internal PSUR processes demonstrate this integration  once a PSUR is finalised, it is passed to the RA department for preparation of the eCTD submission, and the RA team informs the PV department of submission dates and tracking information. (Our Pharmacovigilance Services page details how we handle safety reports and integrate with eCTD submissions.)
  • Quality & Compliance Services: Our Quality Assurance experts oversee the operational processes we use for eCTD compilation, making sure they are compliant with data integrity and validation requirements. If an inspection specifically looks at your electronic submissions process, our Quality Services can provide the necessary SOPs, records of validation, and training records. (Refer to our Quality Services page.)
  • Medical Writing & Document Preparation: Our Regulatory Affairs services include preparation of product information texts (SmPC, labelling, and patient information leaflet), performance of patient information readability testing, Braille and verification, and compilation and assembly of all required documentation for Module 1. Our medical writers prepare eCTD-ready documents that integrate seamlessly with the publishing workflow. (See our Medical Writing & eCTD Publishing service page.)
  • Readability Testing & Labelling Compliance: Any updates to product information that result from a variation or initial MAA must be reflected in the eCTD. Our Readability User Testing service ensures patient leaflets meet regulatory requirements, with reports included in Module 1.3.4. Similarly, our Braille Compliance service ensures Braille declarations are properly included. (See our Readability User Testing and Braille Compliance pages.)
  • Licensing & Dossier Transfer: If you are involved in a licensing deal, the eCTD is a key asset to be transferred or replicated. Our Licensing Facilitation service often overlaps with eCTD work: for example, preparing an eCTD baseline for a product being divested so the new owner can take over a clean eCTD. (Refer to our Licensing In & Out Facilitation page.)