Source hierarchy
Claims about named standards are checked against official specifications or the issuing organisation. Legal claims are checked against official legislation and relevant government sources. Framework pages identify the jurisdiction, legal basis and source-review date. Standards, voluntary guidance, sourcing practices and binding legal requirements are labelled separately.
Separate legal scope and operational recommendations
EU Forced Labour Regulation coverage is kept separate from US Section 307 and UFLPA coverage. A shared supplier map or evidence file does not create a shared legal test. Framework-specific conclusions require the applicable scope, procedure and evidence rules to be assessed independently.
Operational fields, workflow examples and pilot checklists are editorial suggestions unless explicitly identified as a sourced requirement. The site does not label products legally cleared, promise that an authority will accept a document package, or treat traceability as proof of responsible labour conditions.
Examples and recommendations
The lab and product journey use fictional identifiers, facilities and timestamps. They explain relationships and are not complete formal schemas. Recommendations about pilots and data ownership are editorial implementation suggestions, not requirements imposed by a standard.
Review and corrections
Guide pages show publication dates and primary-source references. When a substantive claim changes, the relevant guide should be reviewed and its date updated. To report a correction, provide the page URL, the claim in question and an authoritative source through the publisher’s contact page.