Submission should be treated as a controlled handoff, not the moment when the team discovers missing information. Prepare the mapped fields, source references, technical issues, and final human decisions before anyone enters or uploads data in the external system.
A practical preparation workflow
- 1
Map confirmed facts to a versioned DDS field set.
- 2
Review blockers, warnings, references, and unresolved judgments.
- 3
Export the reviewed snapshot for authorized manual submission.
Make the handoff reproducible
The person submitting should be able to see the exact case snapshot used for every field. Store the mapped value, its source fact, the source file reference, and the mapping version together. If the case changes after export, create a new handoff version.
Separate blockers from warnings and decisions
A missing required value is not the same as an unusual but reviewed value. Use explicit states so the submitter knows what must be resolved, what needs attention, and what has already received a documented human decision.
- Blocker: a required technical input is absent or invalid.
- Warning: the data can be exported but warrants review.
- Decision: an authorized person accepted or corrected a candidate.
Record the boundary between systems
Keep the external submission reference and time with the Filing Case after manual submission. Do not represent a prepared export as proof that the external submission succeeded.
What to check
- Confirmed field values and source references
- Mapping and rule versions used
- Open blockers and accepted limitations
- Reviewer, export time, and submission responsibility
Filovara does not currently submit directly to TRACES or guarantee that an external system or authority will accept the prepared data.
Questions teams ask
Does Filovara submit directly to TRACES?
No. The current product prepares and exports reviewed technical data for an authorized person to submit externally.
Can a prepared export become stale?
Yes. Any change to relevant facts, evidence, rules, or decisions should produce a new export version.
Is a successful technical preflight a compliance decision?
No. It is a completeness and consistency check under a stated mapping version.