Filovara
EN
WorkspaceScreen a plot free
GuidesEvidence concept

Why EUDR technical checks need versions

Make geometry, completeness, mapping, and consistency results reproducible when rules or evidence change.

6 min practical guideReviewed 2026-07-26

A green result without its inputs and rule version cannot be reproduced. Versioned checks bind a deterministic result to the evidence snapshot, normalized data, rule set, execution time, and known technical limitations.

A practical preparation workflow

  1. 1

    Freeze the relevant input versions and selected rule set.

  2. 2

    Run the check deterministically and retain its evidence references.

  3. 3

    Mark the result stale when an input or rule changes, then rerun explicitly.

Bind every result to exact inputs

A plot result should identify the normalized geometry, source feature, CRS decision, and rule version. A DDS preflight should identify the confirmed facts and mapping version. Without those links, a later reviewer cannot explain why the result changed.

Do not overwrite stale results

When evidence or a rule changes, retain the earlier result, mark it stale, and create a new execution. This reveals whether the change came from new evidence, a corrected fact, or an updated rule.

Expose unavailable dependencies

If a dataset, service, or production algorithm is unavailable, the check should say so. A fixture, placeholder, or skipped dependency must never appear as a successful real-world result.

What to check

  • Input identifiers, versions, and hashes
  • Rule, mapping, dataset, and engine versions
  • Result, evidence references, and limitations
  • Stale, rerun, superseded, and export relationships
Keep this limitation visible

A deterministic technical result describes the rule that ran; it is not a legal conclusion and may depend on unavailable external data.

Questions teams ask

Why can the same plot receive a different result later?

The geometry, source evidence, rule set, or external dataset may have changed. The result should identify which input or version differs.

Can a stale result remain in an old Filing Pack?

Yes, if it was current for that frozen snapshot. A later pack should use a new execution and retain the relationship to the earlier result.

Does versioning make a check legally authoritative?

No. It makes the technical process reproducible and its limitations visible.

Continue the workflow

Browse all guides
Evidence provenance in an EUDR caseKeep every confirmed value connected to the exact file, page, row, cell, or geometry feature that supports it.Run a DDS technical preflightMap confirmed facts to versioned DDS fields and surface missing or conflicting data.Validate production plot dataReview format, CRS, coordinate ranges, topology, identity, and case associations.