1. Send issue counts first
Run the browser check and paste blockers, warnings, file type, field names, commodity, source country, and buyer deadline. Do not include raw coordinates or confidential supplier rows.
Documented pilot
TraceReady still needs a permissioned real-world case. If you have a coffee or cocoa farm file that is creating buyer-review rework, start with non-sensitive issue counts. If the cleanup is useful, we can document the before/after without publishing your company, suppliers, buyers, or coordinates.
Run the browser check and paste blockers, warnings, file type, field names, commodity, source country, and buyer deadline. Do not include raw coordinates or confidential supplier rows.
If the file is in scope, TraceReady replies with the cleanup scope, quote, and the exact anonymized facts that could become proof.
A case study needs explicit approval for anonymized issue counts, before/after structure, and one short quote. No company name, supplier names, coordinates, or buyer files are published.
Permission boundary
Anonymized issue counts, file type, row count, cleaned-pack contents, remaining follow-ups, and one approved sentence.
company name, supplier names, buyer names, coordinates, source rows, shipment references, and buyer documents.
If permission is no, TraceReady still treats the cleanup as private work and does not turn it into public proof.
Case capture packet
The template keeps the pilot honest: no public company names, supplier names, buyer names, source rows, or farm coordinates. Publish only with explicit written approval.
TraceReady is operated by Passive Print Labs LLC. A documented pilot is operational file cleanup and proof collection only: not legal advice, not certification, not TRACES submission, and not proof of deforestation-free status.