eCTD Validation Playbook: How to Prevent Technical Rejection
Preventing technical rejection
How agencies validate a sequence, the defects that cause rejection, and the practices that keep them out of your submissions.
Agencies validate before anyone reads
A failed sequence never reaches a reviewer, and the review clock does not start.
Criteria graded high, medium or low. High-severity errors lead to technical rejection; separate criteria apply to study data.
Pass/fail plus best-practice criteria. Any pass/fail failure rejects the sequence. Criteria v8.2 mandatory from 1 December 2025.
eCTD 4.0 check items published as configuration, including conditional rules and rules with effective dates.
Each authority publishes its own criteria and severity — the same defect can be a warning in one region and a rejection in another.
The usual causes
Envelope
Wrong application number, sub-type not valid for the submission type, sequence number not matching its folder.
Files and checksums
A file edited after the backbone was built, or a file on disk the backbone does not list.
Lifecycle
A replace pointing at the wrong document. Often passes validation and confuses the reviewer instead.
PDF properties
Security settings, unembedded fonts, image-only pages, unsupported versions.
Navigation
Hyperlinks and bookmarks that go nowhere after a target was renamed or moved.
Specification drift
Templates still on a Module 1 or DTD version the region has retired.
What prevents it
Validate from the first draft
Run the region’s criteria every time the sequence changes, not the night before the deadline.
Build the envelope from data
From the application record and the region’s vocabularies — not typed into a form.
Fix at the source
Re-render from the corrected document, or the defect returns with the next version.
Validate what you receive
Run the same criteria on sequences from partners and previous vendors.
The full validation playbook
For publishing, regulatory operations and quality teams.
- How FDA, the EU, PMDA and other regions grade validation findings
- Nine defect categories, with typical defects and root causes
- Seven operating practices that prevent rejection
- PDF and navigation standards to author to from the start
- How to triage a validation report
Frequently asked
What is a technical rejection?
A refusal by the agency’s receiving system because the sequence fails rejection-level validation criteria. The content is not reviewed and the review clock does not start until a corrected sequence is accepted.
Are FDA and EU validation criteria the same?
No. FDA grades criteria by severity and rejects on high-severity errors; the EU uses pass/fail criteria, where any failure rejects, plus best-practice criteria. Each region publishes its own list.
Does passing validation mean the submission is right?
It means it is technically acceptable. It does not confirm that the right documents are in the right places with the right lifecycle, which still needs a review of the cumulative view.
How often do validation criteria change?
Regularly. The EU’s criteria v8.2 became mandatory on 1 December 2025, and other regions update on their own schedules. Check each region you file in at least twice a year.
Validation that runs while you build
DnXT Publisher checks each sequence against the target region’s own criteria as it is assembled, graded at that region’s own severity.
