The Audit process

Introduction

The audit process is triggered only from the audit schedule.

*Note*: The configuration of visible fields (read-only or mandatory) is defined during the solution configuration. Some fields present in the example below may therefore differ from your application.

The audit process consists of 3 steps:

• The preparation
• The realization
• The summary

Audit preparation

The audit preparation step is similar to the items offered from the schedule.

The user can:

• Send a convocation (pdf format) and an appointment (in ics format)
• Add documentation for the auditors
• Form their audit team and designate by question group the assigned auditor

Audit realization

At the start of an internal audit, each auditor receives an email to inform them that they have a task to process for this realization step.

The top banner allows identifying the audit number. The header part contains the elements, read-only, defined during planning. Each auditor completes the "Evaluation" tab containing the chapters on which they were designated as auditor.

In an audit, all questions/requirements must imperatively be completed before the audit validation.

Evaluating a group of requirements

To facilitate evaluation, it is possible to apply an evaluation to the group of questions/chapters.

By clicking on the group, it is possible to select an evaluation in the right part which is automatically applied to all requirements. The user can nevertheless modify the evaluations on a few questions.

Evaluating a requirement

By clicking on a question/requirement, the auditor visualizes on the left a panel offering several collapsible sections.

In the "Learn more" section we will find the description of the requirement:

• the name of the question/requirement
• The comment/description specifying the question

In the "Evaluation" section we will find the information relating to the evaluation of the requirement:

• The rating types
• A result field to indicate the retained value
• A comment
• The possibility of adding attachments

In case of non-conformity, the "Anomaly" section is offered to complete the characteristics of the anomaly:

• The anomaly/non-conformity type
• The comment
• The immediate actions implemented (curative actions)
• The proposed or suggested actions

Finally a last "History" section offers for each question a table of previous evaluations made to facilitate monitoring.

Adding a finding

Each anomaly, or non-conformity detected during the audit, automatically creates a finding taken up in the tab for this purpose.

The auditor can add additional findings during their evaluation step

Audit summary

Once all realization tasks are completed, the audit responsible receives an email to inform them that they have a task to process for this summary step.

The summary includes all previously entered information (metadata, detailed evaluation grid, all entered findings and non-conforming evaluations).

The audit responsible has the possibility to modify the evaluations and to add new findings before validating this summary step.

They also have the possibility to create immediate actions and to propose additional actions.

*Note*: Each finding present automatically generates an instance of the "Non-Conformity" process.

Updated on: 20/03/2026