Does eValidator ONE validate eCTD 4.0?

The current LORENZ edition matrix says ONE covers all profiles excluding eCTD 4.0. Obtain the exact edition/profile proposal when v4.0 is required.

Does FDA use eValidator?

FDA's current eCTD v4.0 standards table lists eValidator 25.2 in use as of August 25, 2026. This is a dated tool-use statement, not an endorsement or a guarantee for a sponsor's package.

Can Assyro Validation check a package from another publisher?

That is within its published intended workflow for supported sequences. Qualify the authority/version/operation and test the actual external package before adopting it for release.

Is a report with no errors sufficient for filing?

No. Confirm the correct criteria/configuration and complete input, address warnings or unexplained omissions, and retain content approval and the organization's release decision separately.

Comparison/Updated October 2026

Assyro Validation vs LORENZ eValidator

Compare the profile, criteria revision and reproducible report—not a generic validation checkmark.

Assyro Validation

by Assyro AI

Cloud technical checks for supported eCTD sequences, including packages produced by other tools.

Supported regional checksExternal packagesCloud workflowRelated eCTD

LORENZ eValidator

Edition-based technical submission validation

Basic, ONE and FIVE editions with different profile, deployment and reporting boundaries.

Basic / ONE / FIVEEdition-specific profilesFIVE batch/server toolsFree Basic edition

The verdict

Evaluate Assyro Validation when the required sequence is inside its approved FDA, Health Canada or EMA centralised scope and shared cloud review is part of the job. Evaluate eValidator when its licensed profiles, formats, reporting or server/batch workflow are required. Name Basic, ONE or FIVE: the current matrix explicitly excludes eCTD 4.0 from ONE. Neither a matching tool name nor an error-free report guarantees receiving-authority acceptance.

Individually researched by Assyro AI, a compared vendor. Live LORENZ edition documentation fetched directly and FDA's mutable v4.0 standards table reopened October 13, 2026. Tool-use date and rule revision are identified. No cross-validator performance benchmark was executed.

Start with profile and operating requirements

A validator purchase needs both technical coverage and a reviewable evidence workflow.

Validation qualification
Requirement	Assyro	eValidator
Supported external package	Approved regional scope	Licensed edition/profile
v4.0	FDA; EMA initial MAA	Confirm edition; ONE excludes it
Batch/server/customization	Require demonstration	Evaluate FIVE scope
Low-volume single-region use	Workflow quote	Evaluate free Basic

Supported external package
Assyro
Approved regional scope
eValidator
Licensed edition/profile
v4.0
Assyro
FDA; EMA initial MAA
eValidator
Confirm edition; ONE excludes it
Batch/server/customization
Assyro
Require demonstration
eValidator
Evaluate FIVE scope
Low-volume single-region use
Assyro
Workflow quote
eValidator
Evaluate free Basic

[1][3][5]

Validator agreement is not the same as complete coverage

Two reports can agree because both used an old profile or skipped a file. Define expected findings from the actual criterion and sample defect; then compare the reports. Preserve check identity, severity, file location and explanation.

FDA's current v4.0 page lists validation criteria version 1.6 with support beginning August 28, 2026. Retain the actual applicable revision when qualifying a validator; an accessible URL or familiar product name does not prove revision parity.

[2]

Feature by feature

Published capabilities, related applications and evidence still to request.

Validate existing packages
Assyro Validation
Supported sequences from other publishers[3]
eValidator
Technical submission validation[1]
eCTD v3.2.2
Assyro Validation
FDA, Health Canada, EMA centralised[3]
eValidator
Select licensed region and profile[1]
eCTD v4.0
Assyro Validation
FDA; EMA initial MAA scope[3]
eValidator
ONE excludes v4.0; qualify the required edition/profile[1]
Other formats or regions
Assyro Validation
Outside the approved validation scope[3]
eValidator
Broader formats/profiles; confirm licence[1]
Batch, custom profiles, server operation
Assyro Validation
Demonstrate required volume and customization[3]
eValidator
FIVE functions; module and contract scope apply[1]
Price basis
Assyro Validation
Custom, unlimited users[5]
eValidator
Basic free; ONE annual; FIVE licence/subscription[1]

Assyro Validation and LORENZ eValidator: feature comparison
Capability	Assyro Validation	eValidator
Validate existing packages	Supported sequences from other publishers[3]	Technical submission validation[1]
eCTD v3.2.2	FDA, Health Canada, EMA centralised[3]	Select licensed region and profile[1]
eCTD v4.0	FDA; EMA initial MAA scope[3]	ONE excludes v4.0; qualify the required edition/profile[1]
Other formats or regions	Outside the approved validation scope[3]	Broader formats/profiles; confirm licence[1]
Batch, custom profiles, server operation	Demonstrate required volume and customization[3]	FIVE functions; module and contract scope apply[1]
Price basis	Custom, unlimited users[5]	Basic free; ONE annual; FIVE licence/subscription[1]

Product details and recommendations reflect publicly available information and our own assessment as of October 2026, provided for comparison. LORENZ eValidator is a product of LORENZ Life Sciences; trademarks belong to their respective owners.

Which one should you choose?

Choose Assyro Validation if

Your authority, version and operation are within approved validation scope.
You want to evaluate a shared cloud findings workflow.
Drafting and publishing in related Assyro eCTD are part of a separately scoped project.

Choose eValidator if

Required formats or regional profiles extend beyond Assyro scope.
A verified FIVE batch/server/custom-profile workflow is necessary.
A single-user Basic profile meets the complete requirement.

The detailed comparison

What is the exact validation configuration?

Assyro Validation

Retain the authority, format/version, rule revision, product release, configuration and input identity. FDA/HC/EMA names alone do not qualify a report.

eValidator

Name the edition and selected profile, including any custom severities or extensions. The current matrix distinguishes free single-region Basic, multi-region ONE excluding v4.0, and configurable FIVE.

[1][3]

Does regulator tool use make a sponsor report conclusive?

Assyro Validation

Compare findings with the applicable published criteria and inspect the actual output. Resolve unexplained missing findings before relying on the validator for release.

eValidator

FDA's current v4.0 standards table lists LORENZ eValidator 25.2 as in use as of August 25, 2026. That dated agency fact does not establish your edition/profile/configuration parity or guarantee acceptance.

[2][3]

Price the edition and the report-handling work

Match required regions/formats, users, deployment, profiles, updates, support and reporting. Basic's free licence does not price a multi-user server workflow. Confirm support and maintenance terms for the selected edition.

Add configuration, intended-use acceptance, training, report retention, discrepancy resolution and profile-update review. Include related Assyro eCTD only if drafting/publishing is in scope. No matched pricing or universal cost advantage is asserted.

[1][4][5]

Build a findings-reconciliation worksheet

For each sample record input identity, profile, criterion, expected/observed finding, severity, location, explanation, owner and disposition.

Valid control

Use a retained valid sample and explain every unexpected finding rather than hiding it.

Invalid package

Seed an applicable checksum, structural or reference defect; require the correct criterion and location in the report.

Ambiguous profile

Provide an unsupported or ambiguous input and verify the operator sees an explicit unresolved scope instead of a misleading pass.

Repeatability

Rerun the same input/configuration, reconcile findings and retain the release/profile details with the exported report.

Where eValidator is stronger

No tool wins on everything. Here is where eValidator is the better choice today.

A free Basic edition for a qualifying single-region workflow.
A documented broader format/profile family with edition-specific operating tools.
Dated FDA primary evidence identifies a version of eValidator in the agency's v4.0 validation workflow.

Adopting Assyro Validation

A validation transition changes the release evidence, even when the publisher stays. Compare the same retained inputs and investigate differences instead of selecting whichever report is shorter.

1Retain input packages and existing reports with profile/release metadata.
2Build an authorized sample of valid, invalid and historical cases.
3Run both proposed configurations and reconcile findings by criterion and file.
4Document expected differences, unsupported checks and release ownership.
5Approve acceptance, report retention, update assessment and fallback to the prior validator.

Sources and evidence

Product documents establish published scope. Evaluation scenarios and recommendations are Assyro's analysis. Confirm availability, configuration and contract scope with each vendor.

LORENZ eValidator edition matrix
Basic/ONE/FIVE, explicit ONE v4.0 exclusion, operating/report scope and terms; fetched directly October 13, 2026 after web-tool failure; no revision displayed
FDA eCTD v4.0 standards and tools in use
Current standards table: criteria 1.6 supported August 28, 2026; tools table: eValidator 25.2 in use August 25, 2026; reopened October 13, 2026
Assyro Validation product scope
Published product definition and capability scope; checked October 13, 2026; related applications require their own quoted scope
Assyro eCTD product scope
Published product definition and capability scope; checked October 13, 2026; related applications require their own quoted scope
Assyro pricing
Published custom pricing and unlimited users on every plan; checked October 13, 2026; no competitor price advantage inferred