Defining the scope of a requirement audit
 |
 |
 |
 |
 |
This article is valid for the new Audit (AU001) unified menu in system version 3.0.
- Access the release notes for further details about the significant changes in the unification of the menu.
- Click here to access the documentation valid for the old audit execution menu.
Prerequisites
- Access to the Audit (AU001) menu.
- Audit created in the system, in the planning step.
- Requirement with audit enabled.
Introduction
Once an audit is created in the system, while it is in the planning step, it is necessary to define its scope and associate the objects that will be audited.
The editing of this data varies according to the configurations applied to the Scope tab of the audit category.
See how to define the scope of an audit:
Defining the scope of a requirement audit
1. Access the Audit (AU001) menu.
2. Locate the audit and right-click on it.
3. Select the Open data option.
4. Click on the Audit scope tab.
5. Specify which business unit will be audited. If no business unit is selected, the audit will not be restricted to a specific unit.
6. In the Audited company representative field, insert the representative of the business unit that will be audited. The representative is the person who will accompany the auditor during the execution of the audit and will be available in case of any doubts or needs.
7. Select the start and end dates of the audit scope.
8. If necessary, enter a description about the audit scope in the Scope field.
9. Select the Requirement tab to associate the requirements that will be part of the audit scope. Watch the video below for more details:
Buttons available in the scope structure
The toolbar, located at the top of the Audit scope screen, provides buttons and tools that allow for editing the structure and interacting with its data:
| Disassociate | It disassociates the reference requirement and the structure that belongs to it. |
| Delete | Allows for deleting the objects selected in the scope structure. If the object has sub-objects, they will also be deleted. |
| Associate requirement | Opens the requirement association wizard, which allows for associating requirements already recorded in the system with the structure. In the association wizard, locate the base requirement whose structure will be detailed on the left side of the screen. The right side will display all the requirements that are already part of the current structure. Select the desired items and import them to the current requirement structure. |
| Expand | It allows for expanding the requirement structure. |
| Collapse | It allows for collapsing the requirement structure. |
- For 2nd party - Supplier audits, the Audited business unit field will be replaced with the Supplier field.
- Use it to insert the supplier company that will be audited. The suppliers must have been previously created in SoftExpert Supplier.
- The business units available for selection were previously recorded in SoftExpert Administration. If a new unit needs to be added, click on the
button. Refer to the documentation of the Administration component for more details on how to create it. - It is important to point out that the scope period is not equal to the audit execution period. The start and end dates of the scope represent the period during which the processes, activities, and requirements will be analyzed, that is, the time interval covered by the audit. The audit execution dates, in their turn, refer to the specific days on which the audit will be conducted, including tasks such as document revision, interviews, inspections, and closure meetings. For example, an audit may comprehend records and processes dating from January to June of a year (scope), but be conducted in person in October (execution).
- See more details on creating evaluation criteria by clicking here.
- Check more information about the creation of evaluation checklists by clicking here.
- See how to associate audit tests in the requirement structure.
Conclusion
According to the configurations applied to the category, after adding the requirements to the audit scope, it is also necessary to add the objects that will be audited so that the planning can be closed.