Who this is for: Users with Manage Audit Settings.
Locations can have sublocations beneath them. A requirement set at a parent applies down its whole branch, so you decide once how the sites beneath it are covered.
How coverage works by default
By default, a completed audit at the parent covers its sublocations. Sublocation cells show Via and the parent's name, and each parent row shows a roll-up of its branch, for example “0 of 4 covered, 4 overdue or never audited”.
Open the Coverage view.
Expand a parent row to see its sublocations and the roll-up.
Making each sublocation need its own audit
Open Audit Requirements and choose the parent location.
Select the pencil on the requirement to edit it, or add a new one.
Tick Treat sublocations as separate entities.
Select Save.
When it is off, an audit at the parent also covers every location below it. When it is on, each location below needs its own audit, and shows Never audited until one is completed there.
Note: The setting belongs to the parent's requirement, so it applies to the whole branch. You can't tick it for some sublocations and not others.
If this doesn't work
A sublocation shows Never audited even though the parent was audited — Treat sublocations as separate entities is ticked on the parent's requirement, so the sublocation needs its own completed audit.
You can't edit the requirement — you need Manage Audit Settings.
Related articles
Audit coverage: what the Coverage view shows [LINK]
Setting audit requirements for a location [LINK]
Why is a location showing as not covered? [LINK]