Skip to main content

Setting audit requirements for a location

Tell the system what must be audited where, and how often.

Written by Caim Hermoso

Who this is for: Users with Manage Audit Settings (Audit Administrator by default). Others can open Audit Requirements to see what is set, but can't add or change requirements. [CHECK: no dedicated permission exists in the role editor; confirm Manage Audit Settings is the one that controls requirements]

An audit requirement tells Audit365 that a location must be audited, and how often. Coverage and the Audit Plan are both worked out from these requirements.

Each requirement belongs to a location and is Required by a Standard or a Template. A requirement applies to the location and everything below it.

Adding a requirement

  1. Go to Audits > My Audit Templates > Coverage.

  2. Select Audit Requirements.

  3. Choose the Location. Anything already set there is listed under Set on this location.

  4. Select + Add requirement.

  5. Under Required by, choose Standard or Template, then pick the standard or template.

  6. Set Frequency (months). It starts at 12.

  7. Optionally choose an Audit type, tick Mandatory, tick Treat sublocations as separate entities (see How sublocations are covered, and the "separate entity" switch [LINK]) and add Notes.

  8. Select Save.

Once saved, the requirement is listed with its basis and frequency, for example “By standard · Every 12 month(s)”. A green message lists the templates that can be used to schedule it, including templates in the global library.

Requirements set on a location higher up the tree are listed under Inherited from above, with the location they are set on. They apply here too, and you edit them on that location. A requirement with Treat sublocations as separate entities ticked shows a Sublocations audited separately chip.

Note: A template-based requirement covers every standard the template is tagged with, and adds the template to that location.

Editing or deleting a requirement

Use the pencil to edit a requirement or the bin to delete it. Editing recalculates the cell. You can’t change a requirement’s Required by basis or its standard — delete it and add a new one instead. Deleting one means the cell is no longer required.

When there is no template for a standard

If no template, in your collection or the global library, covers the standard, the cell shows Awaiting template and the requirement shows an orange message: “No published template covers <standard> yet, so it shows as “Awaiting template” until one is published.” You can align an existing template with the standard, or select Request a template, which opens the Audit Template Request pre-filled with the standard’s name.

If this doesn't work

  • There's no + Add requirement button — you don't have permission to set requirements. Ask an Audit Administrator.

  • The cell still shows Awaiting template after adding a template — check the template is published and tagged with that standard.

Related articles

Did this answer your question?