Compliance & review records
Requirement/checklist reference, owner, review date, status and stated scope where maintained.
TDG / Source system
QMSQuality Management System
A QMS may organize compliance records, certificates, inspections, test reports, non-conformities and corrective actions. These materials can support product-data work when source, scope, subject, validity and review status are clear; simply storing a document does not make its claims independently verified.
QMS / Typical contribution
What this source may contribute.
Compliance records, certificates and test reports. Use these examples to guide discovery—not as a guarantee that every field is captured or a final DPP requirement list.
Certificates
Issuer, reference, covered organization/product, scope, validity dates and source document.
Test reports
Sample, method, attribute, result, laboratory, date and product/lot reference where available.
Scope check: A certificate or test report has a defined issuer, subject and scope. Its presence is not proof that every product claim is correct or independently verified.
Make the relationships explicit
Fields matter when they can be linked and reviewed.
A TDG data map records the source, identifier, owner and review status alongside the value.
| Example field or checkpoint | Question to resolve |
|---|---|
| Document ID, issuer and source | Is the issuer known, and can the source document be retrieved? |
| Subject and scope | Does the scope match the claim and product journey being discussed? |
| Validity and status | Who checks expiry, renewal, version changes and withdrawal? |
| Sample, method and result | Can the sample be linked to the style, material or batch in scope? |
Illustrative only. Actual field names, formats and disclosure permissions depend on client systems, business process, data rights and applicable product-specific rules.
From source to governed handoff
A practical way to map QMS data.
Make the product-data journey understandable before selecting an integration or platform.
Create an evidence register
List document/result, owner, issuer, subject, scope, date and source location.
Check product or facility fit
Link evidence only to products, materials, facilities or periods actually covered.
Label review status honestly
Distinguish declared, document-reviewed, expired, pending and independently assured data.
Plan maintenance
Assign responsibility for renewal, expiry, corrections and controlled disclosure.
Compliance boundary: A system record, certificate or readiness map is not by itself proof of compliance. Confirm evidence scope and applicable DPP rules for the product and market.
Explore related sources
Follow the product data across systems.
A product record is usually assembled across more than one source. Select another system to continue.
The connected data journey
Start with the question. Then map the systems.
Explore how TDG can connect records, owners, evidence and approved data exchange.