Process · Audit to closure

Audit to closure

Plan a textile quality audit and close it only after every requirement-linked finding is resolved.

Step by step

Plan Auditor

Auditor records audit number, scope and planned date for a supplier or internal quality review.
- Establishes scope, schedule and auditor
- Updates Audits, People
Conduct Auditor

Auditor carries out fieldwork and moves the audit into active work.
- Records active fieldwork
- Updates Audits
Record findings Auditor

Each finding names the source requirement, what was observed, severity, owner and due date.
- Ties observations to requirements
- Updates Audit findings, Audits
Report Auditor

Auditor gathers the findings while the audit remains open for follow-up.
- Keeps follow-up visible
- Updates Audits, Audit findings
Resolve Auditor

Finding owners address assigned issues and the auditor checks the response against the requirement.
- Records finding ownership and closure
- Updates Audit findings
Close Auditor

Auditor closes the audit after every finding has a closure date and records completion.
- Ends the audit after all findings close
- Updates Audits, Audit findings

And how to keep it from happening.

A finding describes an issue without the source requirement. Add the requirement so the owner can respond to the right control.
The audit is marked Closed while a finding remains open. The closure workflow waits for every finding.
The planned date is used as the actual completion date. Keep the dates distinct so review timing stays clear.

Start free, then use Proto to change fields, steps and approvals before your team goes live.