The product file contains a signed supplier declaration, an audit summary and a completed questionnaire. The documents are real. The temptation is to turn their presence into one clean status: cleared.
That status would say more than the file can necessarily show.
Fact: the issue in 30 seconds
Direct answer. Regulation (EU) 2024/3015 will, from 14 December 2027, prohibit within its stated EU scope the placing or making available on the Union market, or export, of products made with forced labour. It defines due diligence but does not itself create additional due-diligence duties. A product file can preserve product, supplier, source, check, gap and corrective-action records without turning incomplete evidence into a conclusion.
The hidden variable is the boundary between evidence gathered and a substantive conclusion.
Why the file feels conclusive
Declarations and questionnaires create comparability. They can show that a question was asked and an answer received. Audit material can add another source and chronology.
Each source has limits. A supplier may describe one facility, period, tier or product. An audit summary may omit method or underlying evidence. A declaration may be a representation rather than independent verification. These observations do not prove the statement false; they explain why the file must preserve source type and scope.
PARAVEILUX inference. One traffic-light status can erase the difference between evidence present, evidence reviewed and a conclusion supported.
What the source record supports
Regulation (EU) 2024/3015 is the official EU source for the future prohibition and its stated scope. ILO Convention No. 29 provides institutional context for the forced-labour concept.
This draft does not assess whether a product, supplier, place or operator is within scope. It makes no allegation and draws no geographic, sectoral or enforcement-risk conclusion.
Action: separate the evidence layers
Build the file so a reviewer can distinguish:
- Product identity: product, version, batch or range under review.
- Supplier identity: entity, facility or tier described by each source.
- Source record: declaration, contract response, audit or other material, with date and scope.
- Review record: who checked what, against which question, and what remained inaccessible or conflicting.
- Corrective-action record: stated action, owner, evidence, status and follow-up.
- Decision record: bounded operational decision and limitations.
Do not let an absent document become proof of an absent event. Do not let a present document become proof of every fact the team hopes it covers.
Signal: signals and counter-signals
Investigate when a declaration is called verification; supplier and product scope are missing; inaccessible evidence is treated as absence; later corrections overwrite the earlier source; or a final status hides unresolved conflicting material.
Counter-signals include proposition-level sources, dated representations, typed evidence roles, contrary evidence, explicit access limits, Not assessed fields and a review trigger. These improve fairness and traceability. They do not prove the presence or absence of forced labour.
The hidden variable
The hidden variable is evidentiary reach: how far each item can support a proposition. A signed statement may prove that the supplier made that statement on a date. It may not independently prove every underlying condition. A public source may describe a wider pattern without establishing facts about this product.
The owner protects both seriousness and fairness by keeping those roles separate and sending unresolved conclusions to qualified reviewers.
Limitations: what this does not prove
This draft does not prove the presence or absence of forced labour. It does not determine product applicability, authority process, evidentiary sufficiency, investigation exposure, penalties or required due diligence. It does not identify high-risk geographies or entities.
It does not prescribe an audit, contract or remediation programme. Product scope, supplier facts, legal duties and enforcement remain Not assessed.
Owner Q&A
Is a supplier declaration worth keeping?
Yes, as a dated representation with defined scope. Record who made it, what it covers and what it does not independently verify.
Should the file have a traffic-light status?
If used, define it narrowly and preserve the underlying evidence and unknowns. Do not use “clear” or “compliant” without a supported, reviewed meaning.
What should reopen the file?
Possible triggers include a product or supplier change, conflicting source, correction, new official measure or material evidence. Specialists should design the final triggers.
Next verification
Ask whether each document can be tied to the product, supplier, place, period and proposition it is being used to support. Before treating the EU framework as applicable, check the current date, operator role, product scope and evidence rather than importing the rule as a universal conclusion.
Sources and limitations
- Regulation (EU) 2024/3015 — official EU source; general application begins 14 December 2027, while product and operator applicability remain Not assessed.
- ILO Convention No. 29 — institutional context for the forced-labour concept.
This is general risk education, not professional or certified advice. The source describes a bounded EU context with a future general-application date; whether it applies or a comparable evidence gap can arise for you depends on current rules, product, role, market, supply chain and evidence.