Audits
Plan an audit, name the auditors and hosts, record findings and report.
Tasks
Do a task
Lifecycle
Select a status to see who acts there and the article for that step.
-
1Draft
DraftStatus 1 of 7
- Who acts
- Lead AuditorAdditional AuditorsHosts
- What happens
- The audit is created here. Sign to move it to Planned.
- Signature
- Yes
- 2Awaiting Preliminary Reviewer sign-offOptional
-
3Planned
PlannedStatus 3 of 7
- Who acts
- Lead AuditorAdditional AuditorsHosts
- What happens
- The audit is scheduled for its Planned Date. Move it to In Progress, or straight to Audit Performed.
- Signature
- Yes
-
4In Progress
In ProgressStatus 4 of 7
- Who acts
- Lead AuditorAdditional AuditorsHosts
- What happens
- Carry out the audit and add its findings. Move it to Audit Performed.
- Signature
- Yes
-
5Audit Performed
Audit PerformedStatus 5 of 7
- Who acts
- Lead AuditorAdditional AuditorsHosts
- What happens
- The audit work is done. Move it to Reported.
- Signature
- Yes
-
6Reported
ReportedStatus 6 of 7
- Who acts
- Lead AuditorAdditional AuditorsHosts
- What happens
- Sign to close the audit. This is possible only when every finding of the audit is Closed.
- Signature
- Yes
- 7Closed
Select a status above to see who acts there.
Audit findings — each has its own lifecycle
- OpenResponsible Users
- Pending ApprovalHosts, Lead Auditor, Additional Auditors
- Closed
- Open
- Work on the finding, then sign to send it for approval.
- Pending Approval
- One Host signs to close the finding on an Internal audit; the Lead Auditor or an Additional Auditor on a Supplier audit. Or it goes back to Open with a reason.
- Closed
- The finding is done.
Other moves
- Send backPlannedtoDraftThe form asks for a Reason and also requires Additional Auditors, so an audit without them cannot be sent back.How an audit moves from Draft to Closed
- Send backIn ProgresstoPlannedThe form asks for a Reason and also requires Additional Auditors, so an audit without them cannot be sent back.How an audit moves from Draft to Closed
A dashed status is not used on every record. Each finding has its own lifecycle — Open, Pending Approval, Closed — and an audit moves from Reported to Closed only when every finding is Closed.
Status names and colours as Complere shows them.
The whole workflow, step by step: How an audit moves from Draft to Closed
Who can do what
Who can take the key actions. A status name in a cell means the action is allowed in that status only.
| Your system role | Named on the audit | |||||||
|---|---|---|---|---|---|---|---|---|
| Action | Administrator | Supervisor | Regular User | Read Only User | Lead Auditor | Additional Auditors | Hosts | Responsible Users |
| Create an audit How to: Create an audit | Yes | Yes | Yes | No | Not a role on the audit for this action | Not a role on the audit for this action | Not a role on the audit for this action | Not a role on the audit for this action |
| Sign to move the audit on Closing from Reported needs every finding Closed. | No | No | No | No | DrafttoReported | DrafttoReported | DrafttoReported | Not a role on the audit for this action |
| Add a finding How to: Add a finding to an audit In the audit statuses your company allows under Audits › Settings & Master › Settings (Permissible Statuses For Finding Management). | No | No | No | No | In Progress, Audit Performed | In Progress, Audit Performed | In Progress, Audit Performed | Not a role on the audit for this action |
| Send a finding for approval How to: Send an audit finding for approval Signed. | No | No | No | No | No | No | No | Open |
| Approve a finding (Internal audit) How to: Close an audit finding From Pending Approval. One Host's signature closes the finding. | No | No | No | No | No | No | Yes | No |