The latest revision of the FDA Study Data Technical Conformance Guide (sdTCG v6.2) introduces several important changes for sponsors managing SEND submissions. While the update does not completely overhaul existing SEND standards, it significantly strengthens FDA expectations around SEND dataset quality, verification, and submission readiness.
For pharmaceutical companies, CROs, regulatory operations teams, and SEND service providers, these updates create new compliance responsibilities that cannot be ignored. Sponsors submitting nonclinical study data must now demonstrate stronger validation, traceability, and documentation practices before submission.
Why the FDA sdTCG v6.2 Update Matters for SEND Compliance
The FDA continues to increase scrutiny on SEND (Standard for Exchange of Nonclinical Data) submissions due to recurring issues that delay regulatory review. According to the updated guidance, poorly structured SEND datasets can become unusable for FDA reviewers, creating avoidable submission risks.
The newest version of the Technical Conformance Guide focuses heavily on:
SEND pre-submission validation
SENDIG compliance checks
Improved nSDRG documentation
SENDIG-Genetox v1.0 implementation
Correct SEND file naming and folder structure
These changes directly affect sponsors preparing SEND datasets for IND, NDA, and BLA submissions.
Appendix I Introduces Formal SEND Pre-Submission Verification Requirements
The most important addition in sdTCG v6.2 is Appendix I: SEND Data Review Prior to Submission.
Previously, FDA expectations around SEND quality checks were largely informal. The new appendix formalises mandatory verification expectations that sponsors must complete before submission.
FDA identifies three major categories of SEND submission failures that commonly prevent efficient regulatory review:
1. Submission Issues
Common technical problems include:
Incorrect SEND dataset folder placement
Missing or improperly named XPT files
Multiple studies combined within a single directory
Invalid eCTD structure formatting
These errors can immediately disrupt FDA processing workflows.
2. SENDIG Conformance Issues
FDA specifically highlights:
Empty required SEND variables
Invalid data formats
Duplicate records
Broken dataset relationships
Cross-domain reference mismatches
Failure to comply with SENDIG standards can cause datasets to fail validation during review.
3. Study Design Representation Issues
FDA also emphasises scientific consistency problems such as:
Incorrect animal group definitions
Conflicting study results
Mismatched code-label terminology
Inconsistent group summaries across datasets and reports
The guidance makes it clear that SEND conversion alone is no longer sufficient. Sponsors must now prove that datasets accurately represent the underlying nonclinical study.
Expanded nSDRG Requirements Raise Documentation Expectations
The updated guidance significantly strengthens expectations for the nonclinical Study Data Reviewer’s Guide (nSDRG).
Generic boilerplate statements are now explicitly discouraged by FDA.
Sponsors must clearly document:
The organisation responsible for SEND dataset creation
Software and systems used during SEND generation
Validation and verification procedures performed
Any unresolved anomalies or known issues
Scientific rationale supporting unresolved discrepancies
For regulatory teams and SEND vendors, this means templated nSDRG language must be revised to include study-specific explanations and traceable documentation.
Why This Matters
FDA reviewers increasingly rely on the nSDRG to understand dataset quality and submission reliability. Poor documentation may trigger reviewer questions, technical rejection risks, or delays during regulatory assessment.
SENDIG-Genetox v1.0 Is Now Mandatory
A major compliance update in sdTCG v6.2 is the mandatory adoption of SENDIG-Genetox v1.0.
As of March 15, 2025, SENDIG-Genetox v1.0 is required for:
In vivo comet studies
Micronucleus genotoxicity studies
This requirement applies to:
CDER submissions
CBER submissions
NDAs
BLAs
Commercial INDs
Important Scope Clarifications
FDA clarifies that the requirement applies regardless of:
GLP or non-GLP study status
Draft or final study reports
Whether genetox endpoints are stand-alone or integrated into toxicology studies
The guidance also expands applicability beyond the drug substance itself to include:
Active pharmaceutical ingredients (API)
Impurities
Metabolites
Novel excipients
Additionally, sponsors must use SENDIG v3.1.1 together with SENDIG-Genetox v1.0 to generate the required SEND domains correctly.
FDA Clarifies SEND File Placement and Naming Conventions
Another important operational clarification involves SEND dataset folder structure and naming conventions.
FDA now explicitly states that SEND files must be located under:
m4\datasets\[study]\tabulations\send
The guidance also standardises SEND file naming requirements:
File names must only contain the domain abbreviation
Only the .xpt extension is permitted
Study IDs, sequence numbers, and version identifiers should not be appended
This update is designed to improve submission consistency and reduce technical review issues during eCTD processing.
Five Critical Actions Sponsors Should Take Immediately
1. Update SEND Submission SOPs
Map every Appendix I verification requirement to a documented quality control step within your SEND submission workflow.
2. Revise nSDRG Templates
Remove generic validation statements and replace them with detailed, study-specific documentation fields.
3. Audit Genotoxicity Studies
Review all applicable in vivo genetox studies initiated on or after March 15, 2025 for SENDIG-Genetox v1.0 compliance readiness.
4. Verify eCTD Packaging Standards
Ensure SEND file placement and naming conventions are reflected in your eCTD publishing checklist and submission automation systems.
5. Strengthen SEND QC and Reconciliation
Implement reconciliation checks between SEND summary outputs and final study report tables before submission.
Final Thoughts on FDA SEND Compliance in 2026
The FDA Study Data Technical Conformance Guide v6.2 signals a broader regulatory shift toward higher SEND data integrity expectations.
The guidance places increased accountability on sponsors to ensure SEND datasets are:
Scientifically accurate
Technically compliant
Fully validated
Traceable to the study report
Submission-ready before FDA review begins
Organisations that continue treating SEND as a simple conversion exercise rather than a verified regulatory deliverable may face higher submission risks, validation failures, and regulatory delays.
For sponsors, CROs, and regulatory operations teams, proactive SEND quality management is now essential for successful FDA submissions.
Source: FDA Study Data Technical Conformance Guide (sdTCG) current version. This article represents editorial commentary by Auxochromofours and does not constitute regulatory advice.
FAQs
1. What is the FDA Study Data Technical Conformance Guide (sdTCG) v6.2?
The FDA Study Data Technical Conformance Guide v6.2 is the latest regulatory guidance outlining technical requirements for submitting study data to the FDA, including SEND datasets for nonclinical studies. It introduces updated expectations for SEND validation, documentation, and submission quality.
2. What is the biggest SEND update in sdTCG v6.2?
The most significant update is the addition of Appendix I: SEND Data Review Prior to Submission, which formalises FDA expectations for SEND pre-submission verification and quality checks before datasets are submitted.
3. Why is Appendix I important for SEND submissions?
Appendix I identifies common SEND submission failures such as invalid dataset structures, missing variables, broken references, and study design inconsistencies. FDA now expects sponsors to proactively identify and resolve these issues before submission.
4. Is SENDIG-Genetox v1.0 mandatory now?
Yes. SENDIG-Genetox v1.0 became mandatory on March 15, 2025 for applicable in vivo comet and micronucleus genotoxicity studies submitted to CDER and CBER, including NDAs, BLAs, and commercial INDs.
5. Which studies require SENDIG-Genetox v1.0 compliance?
The requirement applies to both stand-alone and integrated genotoxicity studies, including GLP and non-GLP studies involving APIs, impurities, metabolites, and novel excipients.
6. What are the new nSDRG documentation expectations?
FDA now expects sponsors to provide detailed, study-specific information in the nSDRG, including dataset creation methods, validation procedures, software used, responsible organisations, and explanations for unresolved anomalies.
7. What are the FDA requirements for SEND file naming and placement?
SEND datasets must now be placed under the folder structure:
m4\datasets\[study]\tabulations\send
File names should contain only the domain abbreviation with the .xpt extension and should not include study IDs, version numbers, or sequence identifiers.
8. How can sponsors improve SEND submission readiness?
Sponsors can improve SEND compliance by implementing stronger QC workflows, updating SEND SOPs, performing dataset reconciliation checks, revising nSDRG templates, and validating all submissions against SENDIG and FDA technical conformance requirements before submission.