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

1. Navigate to Audits in the Launchpad
2. Choose Create
3. 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
4. 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, Objective Text, and Criteria Text — free-text description of audit scope, goals, and the requirements (policies, procedures, standards) the audit is assessed against
5. Add Team Members — assign persons with their roles (auditor, auditee, etc.); see Audit Team & Roles for details
6. Save as draft. The audit stays in Draft status until explicitly planned.

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	Fieldwork concluded; question responses and the team are locked. Findings remain editable during this review stage
Findings Published	Findings have been formally published to relevant stakeholders
Cancelled	Audit was abandoned; cannot be reopened

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. Audit attachments can be added or removed in any status except Cancelled.

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

• Audit Lifecycle — understand status transitions
• Audit Team & Roles — assign auditors and other team members
• Conducting Fieldwork — record question responses and raise findings
• Audit Programs — grouping audits into a program