These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Textiles and Apparel QMS
- Features
- Audits and findings
Audits and findings
Plan textile quality audits, assign requirement-linked findings and close after finding resolution.
OverviewOpen findings×
Textiles and Apparel QMS · Audits and findings
New
Open findings
Audit findings
| Audit | Requirement | Finding | Severity | Owner | Due date | |
|---|---|---|---|---|---|---|
| ADT-92836 | RQR-192 | FND-596 | Observation | 16 Oct | ||
| ADT-95663 | RQR-458 | FND-599 | Minor | 23 Oct | ||
| ADT-33945 | RQR-980 | FND-995 | Major | 19 Oct | ||
| ADT-75834 | RQR-277 | FND-862 | Observation | 03 Oct | ||
| ADT-80085 | RQR-450 | FND-998 | Minor | 15 Oct |
6 of 6 records
RQR-192Audit findings · AF-22643
ObservationAuditADT-92836
FindingFND-596
Due date16 Oct
What you can do
Keep audit scope and findings together
An audit records its number, scope, planned date, completion date, status and auditor. The status moves through Planned, in progress, Reporting and Closed. The auditor can use the scope to identify a supplier or internal textile quality review, then record each finding against its source requirement. Findings carry severity, due date, closure date and a named owner.
The audit workflow closes the audit only once every finding is closed. That rule keeps the audit’s completion decision tied to its detail. A Reporting audit with an open finding stays visible for follow-up. The owner can resolve the finding while the auditor checks whether the evidence addresses the named requirement.
How the work is organized
- Plan. Auditor sets scope and planned date before fieldwork starts.
- Record. Each finding names the requirement, observation, severity, owner and due date.
- Close. Auditor confirms all findings are closed before closing the parent audit.
What to agree during setup
Agree the source of requirements used for supplier and internal audits. The requirement text on a finding should be recognizable to the owner and auditor, even when a separate document controls the detailed wording. Decide what counts as an Observation, Minor or Major finding and what proof is needed to set a closure date.
Assign auditors and finding owners before the first audit cycle. Make clear who checks closure evidence, especially when a finding owner also works in the audited area. The planned date should reflect the intended fieldwork, while the completion date records actual completion. Quality Manager can use the open audit and finding lists to keep overdue follow-up visible.
Check the handoff on an actual case
An Auditor plans a supplier textile quality audit, writes the scope and assigns the planned date. During fieldwork, they record a Major finding against the exact requirement, describe what was observed, set a due date and assign an owner. The audit advances to Reporting while the finding remains open.
The owner addresses the finding and the auditor checks the response against the requirement. The finding receives a closure date when resolved. If another finding remains open, the audit stays in Reporting. Only after every finding is closed does the auditor close the audit and record the completion date. The audit number provides a stable reference for later review.
What your team sees
- Open audits — Planned, active and reporting work with the assigned auditor.
- Open findings — Requirement-linked items still awaiting closure.
Follow the work through
What it keeps track of
Data model- Audits
- Audits records for QMS for Textiles and Apparel.
- Audit findings
- Audit Findings records for QMS for Textiles and Apparel.
- People
- People records for QMS for Textiles and Apparel.
Who uses it
Permissions- Auditor
- Plans and closes audits.
- Quality Manager
- Watches the follow-up queue.
- Corrective Action Owner
- May own a finding assigned to them.
Set up Textiles and Apparel QMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.