A human-medicine dossier reaches the Saudi Food and Drug Authority as an eCTD uploaded through the eSDR (Saudi Drug Registration) portal. You fill in the application form online, pay the fees there and upload the product file. The SFDA does not take CDs or DVDs for new applications in eSDR. Modules 2 to 5 follow the ICH eCTD specification. Module 1 follows the GCC Module 1 Specifications, version 1.5 (November 2015) on sfda.gov.sa.
The time is lost in the regional rules: Module 1 folders, sequence numbers and submission types, when a baseline is compulsory, and which missed deadlines become a rejection. For what Modules 1 to 5 contain in general, see our CTD dossier structure guide.
The short answer: how a dossier reaches the SFDA today
- Confirm your company has an account in the DENR system, which the SFDA lists as a precondition for eSDR (Guidance for Submission v5.0, section 3.1).
- Fill in the application form in eSDR, pay the fees and upload the eCTD with the cover letter for initial submission. Human products go as eCTD, herbal and health products as CTD, veterinary products as VNeeS (section 3.2).
- The system validates the submission technically and emails the result (Regulatory Framework v6.3, 3.1.2.1). Regulatory Affairs then validates the content: accepted, or deficiencies back through eSDR with the status "the file is incomplete" (Guidance 3.3).
- Assessment questions arrive as waves, which you answer in Module 1.9 and the affected sections. The decision is posted in eSDR.
What the SFDA requires: format, language and file rules
Start from the Guidance for Submission v5.0 (19 October 2022). It covers new marketing authorisations, variations, renewals, the baseline and migration, and points to the GCC data requirements for module content (Appendix F). Its file rules:
- Language. Supporting documents such as certificates and approval letters must be in Arabic or English. Anything else needs an English translation from an authorised translation office, authenticated by the Saudi Embassy in the country of origin (section 8.2).
- PDF. Legible with PDF version 1.4 or higher, A4 pages, files no larger than 100 megabytes, and generated from electronic source wherever possible. Key Module 1 documents (cover letter, form, SPC, labelling, PIL) must be text-searchable, and Module 2 and 3 files are highly preferred searchable (Appendix D).
- No passwords, no digital signatures. File-level security and password protection are not acceptable (section 8.6). Digital signatures are not fully supported and should not be used (Appendix D).
- Virus checking. You scan with an up-to-date tool and the SFDA scans again on receipt; a virus can be grounds for refusal (section 8.7).
Module 1: the Saudi regional module
ICH leaves Module 1 to each region, so this is the one module you cannot reuse from an EU or US dossier. The GCC Module 1 Specifications (version 1.5) define the folder tree, the XML backbone and the file naming; Saudi-specific elements sit under the country code sa. Appendix 2 gives the sections:
| Section | Content |
|---|---|
| 1.0 | Cover letter (a country-specific one goes in 10-cover/sa/sa-cover.pdf) |
| 1.1, 1.2 | Table of contents (replaced by the XML backbone) and application form |
| 1.3 | Product information: SPC (1.3.1), labelling (1.3.2), patient leaflet in Arabic (1.3.3.1) and English (1.3.3.2), artwork and mock-ups (1.3.4), samples (1.3.5) |
| 1.4 to 1.6 | Expert information (quality, non-clinical, clinical); environmental risk assessment (non-GMO, GMO); pharmacovigilance system (1.6.1) and risk management plan (1.6.2) |
| 1.7 | Certificates: GMP certificate (1.7.1), CPP or free-sale (1.7.2), certificates of analysis for substance, finished product and excipients (1.7.3, 1.7.4), alcohol-content (1.7.5) and pork-content (1.7.6) declarations, TSE certificate (1.7.7), diluents and colouring agents (1.7.8), patent information (1.7.9), letter of access to a DMF (1.7.10) |
| 1.8 | Pricing: price list (1.8.1) and other documents (1.8.2) |
| 1.9 | Responses to questions |
The alcohol and pork declarations, the Arabic leaflet folder and the pricing section have no counterpart in the harmonised CTD. Section 1.7.1 matters beyond paperwork: the site behind that GMP certificate may then be inspected, as our SFDA GMP inspection preparation guide explains.
What the specification fixes technically
- The backbone is
m1/gc/gc-regional.xml, valid against the GCC regional DTD. Its root element holds an envelope and the Module 1 catalogue. The specification publishes a checksum file for the DTD, so use the DTD files SFDA publishes, unmodified. - The envelope carries the country (
sa), the agency codeSA-SFDA, the application number issued for the sponsor and product (it stays for the whole lifecycle), applicant, procedure (gccornational), invented name, the sequence number and optionally a related sequence. - File and folder names are lower case. The first name component is the country code, the second the document type, and a third variable part is optional (
sa-cover.pdf,sa-form.pdf). - No placeholder files for empty sections; justify missing data in the Module 2 summaries and overviews (section 2.3).
Validation: technical and business
Technical validation. The Regulatory Framework v6.3 says the SDR system validates the submission automatically after upload and emails the result (section 3.1.2.1). The SFDA does not publish the full rule set, but the Module 1 specification's Annex 1 shows the grading: some PDF criteria moved from Pass/Fail to Best Practice (relative bookmarks, "inherit zoom" bookmarks, Fast Web View, valid link targets), while using the reformat unit with submission type none became Pass/Fail.
Business validation. A Regulatory Affairs reviewer checks that the information matches the requirements. If something is missing or wrong, an electronic inquiry goes to you and you have 30 working days to complete the file (Framework section 3.1.2.2). This stage catches the content problems: missing certificates, a leaflet in one language only, an application form that does not match the dossier.
The submission portal: eSDR
The portal is eSDR at esdr.sfda.gov.sa, which also hosts the user manual. The Guidance for Submission describes how it behaves:
- Waves. Inquiries from all departments are released to you together, as one wave, after each department has evaluated the file. You answer them in one upload.
- Response format. Module 1.9 holds a document that lists each question with your narrative answer, the section name, the page number and a hyperlink to where the answer sits in the relevant module. The response sequence contains only that document and the changed sections, with the SFDA cover letter for response to inquiries (section 3.4.1.1).
- Laboratory inquiries. After you submit, wait for the laboratory inquiry in eSDR, then send the samples and working standards. Add a scan of the stamped and signed sample submission form under 1.3.5 Samples (section 3.4.1.2).
- Decision. You are notified in eSDR. For an accepted application you request the certificate from the "my products" screen. An appeal has to be filed within 60 calendar days (Framework, section 3.4).
Baseline and lifecycle sequences
Sequences are numbered from 0000 and increase by one for each later submission on the same product. The envelope's related-sequence field ties a response to the sequence that opened the activity. In the specification's example, 0001 and 0002 relate to 0000 (a new generic application), while 0003, an extension of indication, relates to nothing because it opens a new activity.
The submission types (Appendix 5) include new-nce, new-gen, new-bio, new-rad, var-type1, var-type2, renewal, extension, transfer-ma, withdrawal, psur, rmp, asmf and none. The submission unit says what the sequence does inside the activity: initial, response, additional-info, closing, correction or reformat. One trap: the baseline document types a variation plain var in an example table, but the controlled vocabulary lists only var-type1 and var-type2. Use the vocabulary.
The baseline rule
If a product was filed as CTD or NeeS and you now file a variation or renewal as eCTD, you must first submit a technical baseline. The Baseline eCTD Submission Requirements v1.1 made it optional from 17 July 2016 and mandatory from 1 January 2017 for any new regulatory activity. Its rules:
- The baseline resubmits the currently valid documents in eCTD format and contains no new information. The cover letter must declare that only the format has changed.
- It goes in as sequence 0000 with submission type
noneand submission unitreformat, and it is never combined with a new application. - It is submitted after the end of the product's current regulatory activity at the SFDA, not during one.
- It is not assessed, and hyperlinks between documents are not required.
- Minimum content: Module 1 cover letter, last approved application form, product information and the CPP or free-sale certificate (1.7.2); Module 3 drug substance, drug product and appendices.
- Once a product is in eCTD, going back to another format is not accepted. Products registered through the SDR system as eCTD need no baseline.
Strengths, forms and extensions
Under Guidance v5.0 Appendix A, different strengths, package types or sizes under one product number can go as one combined eCTD with one sequence number and a cover letter listing the related applications. Different dosage forms go as separate sequences inside the same dossier, and the envelope reference number carries the product and sub-product numbers. A later extension is a new sequence of type extension with only the new data; the specification adds "consult your local regulatory authority before submission", so ask first.
Variations and renewals
Under the Framework v6.3, up to three variation applications (administrative, quality, safety) can be open in parallel for one product. Renewal is due every five years, and the framework allows a request within six months of the certificate's expiry.
Why submissions are rejected
The SFDA does not publish a ranking of the content errors it sees in eCTD uploads. The procedural triggers, though, are published and precise:
| Trigger | Applies to | Source |
|---|---|---|
| No response within 30 working days to a business validation inquiry | New application, variation, renewal | Framework v6.3, 3.1.2.2, 4.1.2, 5.1.2 |
| Unacceptable clarifications after the third wave | New application | Framework v6.3, 3.1.2.2 |
| Unacceptable clarifications after the second wave | Variation | Framework v6.3, 4.1.2 |
| Unacceptable clarifications after the first wave | Renewal; a rejected renewal must be submitted again as a new request | Framework v6.3, 5.1.2, 5.3 |
| No response within 60 working days during assessment, or failure after the fourth wave (four waves in total for evaluation, inspection and pricing) | New application | Framework v6.3, 3.2 and 3.3 |
| Password protection or file-level security | Any electronic submission | Module 1 spec 2.4.4; Guidance 8.6 |
| Virus detected on receipt | Any electronic submission | Guidance 8.7 |
eSDR labels the outcomes. "The file is incomplete" starts the clock from the date of rejection. "The file is rejected due to exceeding the time limit" and "The request was rejected due to lack of requirements" are the two terminal statuses (Guidance section 3.3). The practical lesson is the wave count at business validation: a new application gets three waves, a variation two and a renewal one, so the first response has to answer everything.
How it differs from an EU or US submission
- Module 1. The SFDA uses the GCC Module 1 specification, shared with the other GCC authorities, with its own DTD and the
SA-SFDAagency code. The EU uses its EU Module 1 eCTD Specification (version 3.1, June 2024, on the EMA eSubmission site). The US has its regional Module 1 inside FDA's eCTD submission standards. - Channel. The SFDA route is the eSDR portal, with the application form and fees in the same session. FDA asks for an Electronic Submissions Gateway account, and the EMA's harmonised technical guidance (version 4.0, April 2016, so check for newer text) makes the eSubmission Gateway or Web Client mandatory for EMA submissions and describes the CESP platform for national and mutual-recognition or decentralised submissions.
- Specification version. FDA publishes submission standards for both eCTD v3.2.2 and v4.0, and from 16 October 2026 supports forward compatibility from v3.2.2 into v4.0. The SFDA texts cited here refer to "the ICH eCTD Specification" without a version and say nothing about v4.0 for human products, so confirm with the SFDA before planning a v4.0 build.
- Pre-approval inspection. The SFDA's registration process checks whether the manufacturing line is already approved, and if it is not, schedules a visit and sends the inspection report to the company (Framework 3.2.1). The GMP evidence in 1.7.1 and the site status travel together.
Tracking registrations and variations in RENOVA-RDX
The submission mechanics live in your publishing tool. A regulatory team also needs the register around it: which dossier is filed where, which sequence is next, which licence expires when, which variation is open. RENOVA-RDX registration and variation tracking keeps those records. A dossier record holds the product, country, authority, procedure, submission type and status, with a sequence register beneath it (sequence number, type, submission date, authority reference, status) and a CTD checklist by module and section. Registration licences carry expiry and renewal dates, and variation requests run through an approval workflow. RENOVA-RDX tracks submissions; it does not build, publish or validate eCTD sequences.
Pre-upload checklist
- DENR account confirmed, eSDR user set up, fees ready (Guidance 3.1).
- Module 1 built to GCC Module 1 v1.5 folders with lower-case
sa-file names and the DTD files unmodified. - Envelope reviewed: country,
SA-SFDA, application number, procedure, submission type and unit, sequence, related sequence. - Sequence number is the next unused number for the product, and a baseline exists if the product was filed as CTD or NeeS.
- No placeholders for empty sections, no password protection, no digital signatures.
- PDFs at version 1.4 or higher, A4, under 100 MB, text-searchable where required, bookmarks and hyperlinks resolving.
- Arabic and English leaflets, alcohol and pork declarations and the GMP certificate present in Module 1.
- Origin documents in Arabic or English, or translated and authenticated; virus scan done and noted in the cover letter.
- A named response owner and a 30-working-day diary entry for any business validation inquiry.
Frequently Asked Questions
Is eCTD mandatory for human medicines at the SFDA?
Yes for human products. The SFDA Guidance for Submission v5.0 (section 3.2 and Appendix A) names eCTD as the file format for human products, CTD for herbal and health products and VNeeS for veterinary products. The SFDA Baseline eCTD Submission Requirements v1.1 state that eCTD is mandatory for human drug applications from 3 January 2015 under the Drug Sector's implementation plan.
Can I send the dossier on a CD or DVD?
Not for a new application in eSDR. Guidance for Submission v5.0, section 8.3, says the SFDA does not accept CD or DVD submissions for new applications in eSDR. The upload goes through the eSDR portal.
Do I need a baseline sequence?
You need one when you use eCTD for the first time on a product that was filed as CTD or NeeS and you then file a variation or renewal as eCTD. Products registered through the SDR system as eCTD need no baseline. The baseline is sequence 0000, carries no new information and is not assessed.
Which GCC Module 1 specification version applies?
On 16 November 2026 the current version on sfda.gov.sa was GCC Module 1 Specifications version 1.5, dated November 2015. The document itself tells readers to check the SFDA website for the latest update, so confirm the version before you build a sequence.
What happens if I miss the 30 working days after a business validation inquiry?
The Regulatory Framework for Drugs Approval v6.3 says a new application, a variation or a renewal is rejected if the applicant does not respond within 30 working days. A rejected renewal obliges the applicant to submit a new one.
Does the SFDA accept digital signatures on eCTD documents?
Not at present. Guidance for Submission v5.0 (Appendix D) and the GCC Module 1 specification (section 2.4.1) both say digital signatures are not fully supported and should not be used.
Sources
- SFDA, Guidance for Submission, version 5.0 (document control entry 19 October 2022), DS-G-003-V05-090511, read 16 November 2026
- SFDA, GCC Module 1 Specifications, version 1.5 (November 2015), read 16 November 2026
- SFDA, Baseline eCTD Submission Requirements, version 1.1 (revision dated 29 June 2016; baseline mandatory from 1 January 2017), read 16 November 2026
- SFDA, Regulatory Framework for Drugs Approval, version 6.3 (23 February 2022 entry; implementation date 1 October 2020), DS-G-001-V6.3, read 16 November 2026
- SFDA, Guide to Good Manufacturing Practice for Medicinal Products, version 4.4 (revision table 21 May 2026), read 16 November 2026
- FDA, Electronic Common Technical Document (eCTD), page content current as of 29 October 2026
- EMA, Harmonised Technical Guidance for eCTD Submissions in the EU, version 4.0 (April 2016)
- EMA eSubmission, EU Module 1 eCTD Specification v3.1 (June 2024)
Tracking registrations and variations in Saudi Arabia?
RENOVA-RDX holds the dossier, sequence and licence records for each product and market, so the sequence you file next is never a guess. It tracks submissions; it is not an eCTD publishing tool.
Explore RENOVA-RDX