01 / Missing
A DPP field gap is found
The manufacturer sees a passport draft blocked by missing supplier-held evidence, not an abstract compliance checklist.
Gap: recycled content evidence
Product scopeDPP versionRequired fieldDue date
Evidence-chain proof
A DPP claim is only as strong as the evidence chain behind it.
Redy shows the operational chain competitors often hide: the missing field, supplier request, source evidence, human review, versioned record, and passport-ready output.
Proof artifact
gap -> request -> evidence -> claim -> version -> output
Evidence path
6 states
Missing, requested, submitted, approved, versioned, published.
Supplier role
First-class
The supplier owns source evidence and grants, not just an upload box.
Review model
Human-gated
AI and OCR can propose values; authorized reviewers decide what commits.
Output shape
Portable
Approved evidence can feed portal views, APIs, exports, and public passport surfaces.
The chain at a glance
Six states from missing field to published passport.
Every claim Redy publishes moves through the same evidence chain. Each state names who acted and what artifact changed — so any published value can be traced back.
01Detected
Missing
A required passport field has no trusted value yet.
02Manufacturer
Requested
The gap becomes a scoped supplier evidence request.
03Supplier
Submitted
The supplier attaches source documents and values.
04Reviewer
Approved
A reviewer commits the value from the evidence.
05System
Versioned
The approved claim becomes an immutable record.
06Output
Published
Feeds passport views, APIs, exports, and resolvers.
Evidence chain
The hard work happens before the passport page exists.
This is the chain buyers should ask every DPP vendor to explain. Redy makes each state explicit so teams can see who acted, what evidence changed, and what became publishable.
Manufacturer
02 / Requested
The request is scoped
Redy turns the gap into a targeted supplier ask with product context, requested fields, and the reason the evidence is needed.
Request: recycled material declaration
Supplier orgRequested useField listResponse workspace
03 / Submitted
The supplier answers once
The supplier attaches source documents, reviews extracted values, and decides what can be shared for the request.
Submission: certificate + declaration
Source filesExtracted valuesSupplier attestationGrant terms
04 / Approved
The claim is reviewed
The manufacturer reviews the proposed claim, source context, confidence, and supplier grant before it enters a passport record.
Decision: claim accepted
ReviewerDecision timeEvidence referenceReason code
05 / Versioned
Provenance is preserved
The approved value is tied to source evidence, actor trail, grant state, and DPP version instead of becoming a naked spreadsheet cell.
Snapshot: DPP v1.0 claim set
Version idSource chainGrant idAudit event
06 / Published
Passport-ready output is delivered
The approved record can support public passport pages, API consumers, exports, resolver paths, and downstream consumer views.
Output: passport-ready record
Public viewAPI payloadExport packageResolver path
Record anatomy
A claim needs context, not just a value.
The difference between a weak DPP page and a trustworthy DPP workflow is the metadata that survives review and publication.
Claim
recycledMaterialPercentage
The reviewed DPP field value, not a raw attachment name.
Supplier source
Northline Apparel declaration
The supplier record and document context behind the value.
Grant
request-scoped reuse
The permission boundary that explains why this buyer can use it.
Review
manufacturer approved
The human decision state before the claim becomes publishable.
Version
DPP v1.0
The passport version that consumed the approved evidence.
Delivery
page + API + export
The same reviewed record can feed multiple downstream surfaces.
Sample reviewed record
Passport-ready evidence payload
{
"claim": "recycledMaterialPercentage",
"value": 42,
"unit": "percent",
"status": "manufacturer_approved",
"supplierEvidence": {
"recordId": "evidence_rec_42",
"supplierOrg": "Northline Apparel",
"source": "recycled-polyester-declaration.pdf",
"attestation": "supplier_confirmed"
},
"grant": {
"scope": "JACKET-TS-2408",
"consumer": "manufacturer_org_18",
"state": "active"
},
"passportVersion": "dpp_v1_0",
"auditRef": "audit_evt_927"
}Control proof
The controls answer the questions buyers will ask.
Question
Who can create the request?
Redy path
Manufacturer workspace users with request authority.
Failure mode avoided
Any teammate emails every supplier the same spreadsheet.
Question
Who owns the source evidence?
Redy path
The supplier workspace maintains source files, records, grants, and reuse decisions.
Failure mode avoided
The manufacturer copies files into a private folder and loses supplier context.
Question
When does AI become truth?
Redy path
Never by itself. AI output stays proposed until authorized review confirms it.
Failure mode avoided
Extracted values are pasted into a passport without source review.
Question
What survives publication?
Redy path
Source references, review state, grant metadata, version id, and audit trail.
Failure mode avoided
A public DPP page shows claims but cannot explain how they were approved.
The published surface
What the approved chain produces.
The published Digital Product Passport as consumers see it: verified issuer signature, signed-field markers, and the QR resolver link.
Outputs
One evidence chain can support many surfaces.
The proof is not a single mock screen. It is the same governed record moving through manufacturer, supplier, public, and integration surfaces.
Manufacturer portal
Evidence readiness board
Teams see missing fields, supplier requests, approvals, and blocked publication states.
Supplier workspace
Reusable evidence record
Suppliers preserve documents, extracted values, and grant choices for future requests.
Public DPP
Provenance-safe passport view
Consumers and buyers see useful passport facts without exposing private workroom data.
External systems
API and export package
Approved records can move to PLM, PIM, ERP, LCA, and external DPP platforms.
Use proof to pressure-test DPP platform claims.
Ask every provider how a missing supplier field becomes a reviewed, versioned, revocable, exportable passport claim.