Give every record a purpose
Evidence management starts with the claim being examined. Identify the product, material, facility, activity and period concerned. Then state what each source can support. An invoice, dispatch note, production log and labour-related assessment serve different purposes even if they arrive in the same supplier folder.
Retain original documents and the reference linking each document to the record being reviewed. Capture the issuer, date received, applicable period, version and review owner. Where a translation is used, retain the connection to the original so another reviewer can understand the basis of the assessment.
Use review states that explain the work
| State | Meaning |
|---|---|
| Reported | A supplier or other source has made an assertion; review is pending |
| Supported | A reviewer found relevant support, with the scope and limitations recorded |
| Contradicted | Sources conflict and the discrepancy needs resolution |
| Missing | The record needed to examine the relationship is unavailable |
| Needs refresh | The period, site or process has changed since the previous review |
Record who assigned the state, why and what action follows. Avoid a general compliance badge that turns a limited document review into a claim about all products or all legal frameworks.
Check relationships and limitations
Compare identifiers, entities, facilities, dates and quantities across the supporting records. A supplier statement naming a country may not connect to the material lot actually used. An assessment of one site may not cover an outsourced production step. Record those limits instead of treating document presence as a successful review.
Link labour-related concerns to the relevant facility and period while protecting sensitive information. Access controls should reflect the sensitivity of the evidence and the purpose of the review. Do not circulate worker details broadly merely because the product trace itself is shared with partners.
Separate framework-specific assessments
Use a common evidence index with separate EU and US assessment records. Each assessment should identify its legal basis, the question being answered, the evidence relied on, unresolved issues and the decision owner. A sourcing review, a UFLPA scope analysis and an EU investigation response are different tasks.
The EU Forced Labour Regulation and UFLPA pages describe their legal contexts. The index does not determine which evidence an authority will accept. In an actual case, follow the applicable official communication and procedural requirements.
Test retrieval and correction
Select a product lot and ask a colleague to reproduce its supplier and facility history from the index. Include a superseded document, an unresolved identity and a corrected quantity. Check whether the reviewer can explain both the conclusion and its limitations without relying on the person who assembled the file.
Preserve the reason for corrections and the prior review history. Assign follow-up owners and dates for missing information. Determine retention periods from the applicable legal, contractual and operational context rather than adopting one universal duration. Data governance provides the wider controls; responsible sourcing connects the record to purchasing and response decisions.
Sources and scope
Primary references checked on 4 October 2026. The process examples and implementation suggestions are editorial guidance. Formal standards are distinct from legal requirements.
The data fields, review methods and fictional examples below are editorial implementation suggestions. They are not a universal legal evidence checklist, certification scheme or guarantee of admissibility. Evaluate legal requirements within the relevant framework.