Sanad is an early-stage concept for helping Pakistani textile exporters organize compliance evidence. We’re speaking with exporters to validate the real workflows and needs before building a product.
The current page frames this as a deadline for preparing a traceable evidence packet. Confirm regulatory copy before publication.
A market-access date highlighted in the existing page; keep this context tied to approved, current source copy.
Use ongoing buyer requests to ground the research conversation in real exporter workflows.
Different portals can show different values for the same facility when teams re-enter facts on different dates. The current page frames this as a workflow problem to validate with exporters.
Worldly FEM/FSLM, EcoVadis, Sedex, amfori, buyer spreadsheets, and other request channels.
One reported challenge is time spent re-keying facts that teams have already checked.
Buyers may keep requesting information through their own policies and processes.
Audits, portals, consultants, re-audits, and preparation work are part of the discovery conversation.
These concept modules show workflows we’re exploring with exporters. They are not finished or available product features.
Explore how certificates, registers, invoices, and audit reports might be kept with their expiry dates, citations, and version history.
Concept module · under researchWe’re testing whether a shared, evidence-linked workflow could reduce repeated work for supplier teams. The steps below describe the concept, not a finished product.
Bring in certificates, registers, payroll files, invoices, and source documents from familiar channels.
Extract facts, normalize units, and keep each claim tied to its source document, page, and date.
Approve, edit, or mark a field as a gap before it reaches a buyer. The team signs off.
Explore ways to return reviewed answers in a buyer’s original format with citations attached.
This is the principle the concept is built around: make the source and any missing information visible, with human review before a response goes out.
Document, page, period, and review state stay attached to the claim.
No invented workforce figures or made-up origin declarations.
A compliance team signs off before anything reaches a buyer.
The right compliance layer has to respect the records, languages, and handoffs exporters already work with. These are areas for research and validation, not a promise of available functionality.
The current page uses EUFLR as the clearest example of why teams may need a reconstructable evidence trail. Keep the deadline visible but do not turn it into a guarantee of regulatory outcomes.
Policies, roles, training records, and corrective actions in a reviewable record per facility.
Keep facility, subcontractor, and third-party evidence connected to the answers it supports.
Explore a coherent bale-in → yarn-out → fabric-out → garment-out trail for each purchase order.
Sanad is a workflow and evidence-management concept, not legal advice or an audit certification.
We’re exploring how one facility’s evidence could support a buyer request. Share a redacted example or talk with us—this is research validation, not a finished software pilot.
