Why SEND Validation Matters for Your FDA and PMDA Submissions
Your nonclinical study data must clear FDA validation before a reviewer ever sees it. A malformed dataset, missing Trial Summary file, or mismatch between your SEND package and study report can trigger a refuse-to-file decision that delays your entire program by weeks or months.
The Standard for Exchange of Nonclinical Data (SEND) is the CDISC-endorsed format the FDA requires for toxicology, carcinogenicity, and safety pharmacology studies. PointCross Life Sciences helps biopharma teams and CROs generate submission-ready SEND datasets that align with both FDA and PMDA expectations from day one.
This guide walks you through the validation workflow, the most common blockers that cause submission delays, and how to keep your datasets synchronized with your final study reports.
Key Takeaways: SEND Dataset Validation for FDA and PMDA
- FDA Technical Rejection Criteria check your SEND package before human review, and failures mean immediate rejection.
- PMDA does not mandate SEND but expects CDISC-compliant clinical data, so dual-region filings need separate validation workflows.
- Dataset-to-report mismatches pass automated validators but trigger reviewer queries that stall approvals.
- PointCross SEND-ASSURE automates reconciliation between your study reports and SEND datasets to close compliance gaps.
- SENDIG version selection depends on study start date, not submission date, so plan version mapping early in your program.
What Is SEND and Why Do Regulators Require It?
SEND organizes animal study data into machine-readable domain files that regulators can load directly into review tools. Each domain covers a specific data type: demographics, body weights, clinical observations, laboratory results, macroscopic findings, and microscopic findings.
The FDA mandates SEND for in-scope nonclinical studies submitted in INDs, NDAs, ANDAs, and BLAs to both CDER and CBER. Sponsors carry the regulatory obligation, though CROs typically generate the datasets on their behalf.
Standardized data lets reviewers analyze toxicity signals consistently across every submission. This consistency speeds first-cycle reviews and reduces back-and-forth queries that extend timelines.
Which Studies Require SEND Datasets in 2026?
The requirement keys off your study’s start date and type, not the date you submit. The FDA Data Standards Catalog lists the deadlines that determine which SENDIG version applies.
Core study types requiring SEND include single-dose toxicity, repeat-dose toxicity, and carcinogenicity studies. Safety pharmacology studies covering cardiovascular and respiratory endpoints also fall under the mandate.
CBER began requiring SEND for biologics submissions in March 2023. If your pipeline includes biologics-focused programs, this milestone shapes your data strategy.
SENDIG-DART and SENDIG-Genetox Timelines
The SENDIG-DART v1.1 guide covers embryo-fetal development studies. It became required for NDA submissions in March 2023 and for INDs in March 2024.
SENDIG-Genetox v1.0 addresses in vivo micronucleus and comet assay data. Studies starting after March 15, 2025 must use this guide for genetic toxicology endpoints.
Studies that fall outside these guides still need a simplified Trial Summary (ts.xpt) file so the submission clears technical validation.
How SENDIG Versions Differ and How to Choose the Right One
The SEND Implementation Guide comes in several versions. The one you must use depends on when your study started, not which version is newest.
SENDIG v3.1.1 is the current baseline for general toxicology and carcinogenicity studies that started after March 15, 2023. It refines how pharmacokinetic concentration (PC) and parameter (PP) domains handle timing variables.
Using the wrong version or mixing versions across a submission creates conformance findings that delay approval. Map each study to the correct SENDIG version before you begin dataset creation.
What SENDIG v4.0 Means for Future Submissions
CDISC projects SENDIG v4.0 publication for Q4 2026. This release introduces domains for immunogenicity, cell phenotyping, and ophthalmology data while revising the Microscopic Findings domain.
Because publication dates can shift during public review, confirm the active requirement against the FDA Data Standards Catalog before you lock your approach.
FDA Technical Rejection Criteria: The Gatekeepers of Your Submission
The FDA enforces Technical Rejection Criteria (TRC) through automated eCTD checks. A failure at this stage means rejection before a reviewer opens your package.
The high-severity codes to know are 1789 (Study Tagging File must exist), 1734 (Trial Summary ts.xpt required for each study), 1735 (correct STF file tags), and 1736 (required dataset files present).
These checks run in sequence. An early failure stops the rest, so a missing ts.xpt file prevents the system from evaluating anything else in your package.
How to Avoid Common TRC Failures
Generate the Trial Summary file for every study referenced in Modules 4 or 5, even legacy studies with no full SEND package. Validate your define.xml metadata against the current CDISC schema. Check that your file naming conventions match FDA expectations exactly.
Run your package through eDataValidator before submission. This catches structural errors early when you still have time to fix them.
PMDA Requirements: How Japan Differs from the FDA
Japan’s PMDA requires CDISC standards for clinical data but does not currently mandate SEND for nonclinical studies. This distinction matters for sponsors filing across both regions.
PMDA enforces its own set of validation rules for SDTM and ADaM datasets. Your clinical data must pass these checks even when your nonclinical data follows FDA SEND requirements.
For dual-region programs, build nonclinical data to SEND for the FDA and validate clinical data against PMDA rules separately. PointCross validation tooling accounts for both rule sets so one workflow can serve multiple regulators.
Planning Global Submissions with Mixed Requirements
Start with the strictest requirement. If you build your nonclinical data to FDA SEND standards, you have a machine-readable foundation that could adapt if PMDA or EMA adopt similar mandates.
Track regulatory updates from both agencies. International harmonization discussions continue, so SEND requirements could expand to additional regions in future years.
Why Passing the Validator Is Only Half the Battle
A dataset can pass every conformance rule and still contain errors that reviewers catch. Validators check structure and controlled terminology. They do not confirm that your body-weight numbers, incidence tables, and findings match the signed study report.
Discrepancies between datasets and reports erode reviewer confidence. A body weight that reads 245g in your SEND file but 254g in your study report raises questions about your entire data management process.
This reconciliation step separates technically valid files from review-ready submissions. SEND-ASSURE from PointCross automates this report-to-dataset consistency check so you catch mismatches before the FDA does.
How Study Report Alignment Prevents Submission Delays
Traditional workflows create SEND datasets after the study report is finalized. This sequential approach introduces risk. Any transcription error during dataset creation goes undetected until a reviewer compares numbers.
The solution is parallel processing. When your study report and SEND datasets draw from the same data source and generate simultaneously, alignment happens by design rather than by manual QC.
PointCross Single Track Processing delivers both the study report and SEND datasets from a single data source. This eliminates the reconciliation gap and cuts turnaround time by two weeks or more.
Automated QC Findings and Protocol Deviation Tracking
Single Track Processing flags QC findings automatically and generates a master list of protocol deviations for review. Your team sees discrepancies as they occur rather than discovering them during final validation.
This approach shifts quality control from a submission bottleneck to a continuous process. Errors surface early when correction costs less time and effort.
Common SEND Validation Mistakes That Trigger Rejections
Most SEND problems fall into a short list of repeat offenders. Catching these issues early saves the weeks a rejected submission costs.
Missing or Malformed Trial Summary Files
The ts.xpt file is the single most common cause of a 1734 rejection. Every study referenced in your submission needs one, including studies with no full SEND package.
Check that your Trial Summary includes all required parameters and uses current controlled terminology. A missing study objective or outdated species term can trigger validation errors.
Version Mismatches Across Studies
Applying the newest SENDIG to a study whose start date calls for an earlier version produces conformance findings. So does the reverse: using an outdated guide when a newer version is required.
Map each study in your submission to the correct SENDIG version based on its start date. Document this mapping in your nonclinical Study Data Reviewer’s Guide (nSDRG).
Controlled Terminology Drift
Free-text entries or outdated terms where the standard expects a specific codelist value create validation failures. The FDA expects you to use the controlled terminology version that matches your SENDIG version.
Review CDISC controlled terminology updates regularly. A term that was acceptable last year may have been deprecated or replaced.
Building a Validation Workflow That Scales
Sponsors and CROs managing multiple studies need a repeatable validation process. Ad-hoc checking introduces inconsistency and leaves gaps that surface at the worst time.
Start by centralizing your validation tools. PointCross XBIOM Metadata Repository automates metadata governance and enforces consistency across studies so your validation baseline stays stable.
Define clear checkpoints: after data lock, after dataset generation, and before final submission packaging. Run validation at each stage rather than only at the end.
Cross-Study Analysis for Historical Control Comparisons
Standardized SEND data enables analysis across your entire study portfolio. You can compare findings against historical controls, identify background lesion incidence, and spot trends that inform future study design.
PointCross Nonclinical Insights aggregates SEND data from completed and ongoing studies into a searchable warehouse. This turns submission artifacts into research assets.
How PointCross Ensures 100% Dataset-to-Report Alignment
PointCross addresses the full SEND workflow from data ingestion through validated submission. The XBIOM platform ingests data from LIMS, EDC systems, or PDF study reports and maps it to SEND domains with automated smart transformation.
SEND-ASSURE performs automated QC checking of SEND datasets against toxicology reports. It catches the dataset-to-report mismatches that validators miss but reviewers catch.
The result is 100% consistency and traceability between your study report and SEND dataset. Final submission-ready packages generate only after study data lock and report approval, so you submit with confidence.
Firm Fixed Price Quotes and Guaranteed Turnaround
PointCross delivers firm fixed price quotes with guaranteed turnaround times within 24 hours. Free no-commitment indicative quotes let you plan your budget before committing to a project.
With experience processing over 1,500 studies and trusted relationships with 5 of the top 15 pharma clients, PointCross brings proven technology and global team presence across the US, India, and Europe.
In Conclusion: How to Achieve Submission-Ready SEND Datasets
SEND validation determines whether your nonclinical data reaches a human reviewer or stops at the automated gate. Getting it right requires attention to version selection, controlled terminology, and the often-overlooked reconciliation between datasets and study reports.
Build validation into your workflow from study start. Map each study to the correct SENDIG version, validate incrementally at defined checkpoints, and automate the dataset-to-report comparison that catches the errors validators miss.
PointCross Life Sciences helps biopharma R&D teams and nonclinical CROs deliver FDA and PMDA compliant SEND datasets faster, with 100% alignment between study reports and submission files. Contact our team to discuss your next submission.
FAQs About SEND Dataset Validation for FDA and PMDA
What Is SEND Dataset Validation?
SEND dataset validation is the process of checking your nonclinical study data files against FDA conformance rules, CDISC standards, and controlled terminology requirements. The FDA runs automated checks before human review, and failures result in immediate rejection.
PointCross eDataValidator checks both structural conformance and FDA-specific business rules so you catch issues before submission.
Does PMDA Require SEND Datasets for Nonclinical Studies?
No. As of 2026, PMDA requires CDISC standards for clinical data (SDTM and ADaM) but does not mandate SEND for nonclinical studies. If you file in both Japan and the US, you need separate validation workflows for each region.
PointCross validation tooling supports both FDA and PMDA rule sets in a single platform.
What Causes Most SEND Submission Rejections?
The most common cause is a missing or malformed Trial Summary (ts.xpt) file. Other frequent issues include using the wrong SENDIG version for a study’s start date, controlled terminology errors, and mismatches between dataset values and study report figures.
How Do I Know Which SENDIG Version to Use?
The required version depends on your study’s start date and type, matched against the FDA Data Standards Catalog. SENDIG v3.1.1 is required for general toxicology studies starting after March 15, 2023. SENDIG-DART, SENDIG-AR, and SENDIG-Genetox have their own effective dates for specialized study types.
How Does PointCross Ensure Dataset and Study Report Alignment?
PointCross SEND-ASSURE automates reconciliation between SEND datasets and toxicology study reports. It compares values record by record and flags discrepancies that automated validators miss. Single Track Processing generates both deliverables from the same data source so alignment happens by design.