Audits
An audit in qportal represents a single examination or review. It brings together an audit team, a scope defined by an org unit and a question catalog, findings, and action items.
Creating an Audit
Section titled “Creating an Audit”- Navigate to Audits in the Launchpad
- Choose Create
- Fill in the required fields:
- Title — a descriptive name for the audit
- Audit Type — e.g. Internal Audit, Supplier Audit (configured in Master Data)
- Org Unit — the organisational unit being audited
- Question Catalog — the checklist to use during fieldwork
- Planned Start / End Date
- Optionally add:
- Location — specific site within the org unit
- Audited Business Partner — for supplier or customer audits
- Lead Auditor — designated lead for this audit
- Scope Text and Objective Text — free-text description of audit scope and goals
- Add Team Members — assign persons with their roles (auditor, auditee, etc.)
- Save as draft. The audit stays in Draft status until explicitly planned.
Audit Statuses
Section titled “Audit Statuses”See Audit Lifecycle for the full status flow and allowed transitions.
| Status | Meaning |
|---|---|
| Draft | Being prepared; all fields and team can still change |
| Planned | Scheduled; team and catalog are set, fieldwork not yet started |
| In Progress | Fieldwork underway; question responses and findings can be recorded |
| Completed | Audit concluded; findings and responses are locked |
| Findings Published | Findings have been formally published to relevant stakeholders |
| Cancelled | Audit was abandoned; cannot be reopened |
Attachments
Section titled “Attachments”You can attach files (documents, photos, evidence) directly to an audit using the Attachments section on the audit object page. This is separate from attachments on individual findings.
During Fieldwork
Section titled “During Fieldwork”When an audit is In Progress, auditors work through the assigned question catalog. For each question:
- Select a Rating Option (defined by the catalog’s rating scheme)
- Choose a Severity Classification (Conform / Observation / Minor NC / Major NC)
- Enter a Response Text and optional Notes
- Mark as Not Applicable if the question does not apply
- Create Findings directly from a question response when a deviation is identified
See Findings for details on documenting findings.
Change History
Section titled “Change History”All changes to an audit — including field edits and status transitions — are automatically tracked. The Change History section at the bottom of the audit object page shows who changed what and when.
Next Steps
Section titled “Next Steps”- Audit Lifecycle — understand status transitions
- Findings — how to document findings during fieldwork
- Audit Programs — grouping audits into a program