STEP 1
Scope
Clarify products, CN/HS codes, shipment flows, supplier roles, and who carries the operator obligation.
Scope document
Methodology
An evidence operating system for EUDR implementation.
LamNova does not sell another dashboard. The methodology is to make supplier evidence collectable, checkable, explainable, DDS-ready, and repeatable across importer and Vietnamese supplier teams.
“Operating system” here means process, roles, evidence structure, and recurring workflow - not proprietary software or a compliance certificate.
Process
STEP 2
Collect
Gather supplier contacts, geolocation, legality documents, species data, chain-of-custody records, and existing certificates.
Supplier data baseline
STEP 3
Validate
Check coordinates, GeoJSON format, document consistency, supplier red flags, and whether evidence matches the actual supply chain.
Red flags report
STEP 4
Structure
Turn scattered files into an evidence pack with ownership, naming, gap registers, escalation paths, and repeatable SOPs.
Evidence schema
STEP 5
Prepare
Translate the evidence into DDS-ready logic: product data, plot data, risk conclusions, and TRACES submission readiness.
DDS-ready submission
STEP 6
Monitor
Maintain supplier records, reference numbers, corrections, and recurring checks so compliance survives beyond the first shipment.
Recurring evidence cycle
Evidence principles
Data collection is not enough.
A due-diligence file is only useful if the team can explain where the evidence came from, how it was checked, and what changed over time. Audit-ready means structured and reviewable - not guaranteed compliant.
Provenance
Every data point needs a source: who provided it, when, and under which supplier or shipment context.
Integrity
Evidence must be controlled well enough that later changes, corrections, and document versions stay explainable.
Methodology
The reasoning path matters: how data was checked, which red flags were assessed, and why a conclusion was reached.
Reproducibility
A reviewer should be able to follow the same evidence chain and understand the same due-diligence conclusion.
Tool-agnostic
The method can work with your existing stack.
LamNova can work around spreadsheets, shared drives, procurement exports, GIS files, certification documents, or dedicated traceability platforms. The goal is not to force a tool; the goal is to make the evidence process operational.
If a software platform is the right fit, LamNova can help evaluate and implement it. If not, the workflow can start with a lean evidence pack and clear ownership model.
Clear boundary
What this is not
Not a law firm - LamNova does not replace qualified legal counsel.
Not a certification body - LamNova builds evidence workflows, not certificates.
Not another SaaS dashboard - LamNova is tool-agnostic and implementation-led.
Built for the messy middle between EU compliance teams and Vietnamese supplier reality.
Practical output
What the method creates
Evidence maps, supplier gap registers, red flag reports, SOPs, DDS-ready documentation logic, reference tracking, and a team rhythm that can survive beyond the first project.
Next step
Build an evidence process your team can explain.
Use the first call to discuss whether your current supplier evidence is collectable, checkable, and ready to become a repeatable DDS workflow.