Skip to main content

Setting the template's location(s), version and reference code

Where a template can be used, and the two metadata fields that identify it.

Written by Caim Hermoso

Who this is for: Needs Manage My Audit Templates.

Locations — the locations this template is saved to, set in the Locations panel at the top of the builder's right-hand column. This controls where the template can be used and sets the default location when someone schedules an audit from it. Remember that a template across several locations is one shared record — see 2.7.

Version and Reference are read-only metadata. They sit in the metadata block under the Global Template Library card, alongside Created by and Date created, and the system maintains them for you.

Field

Before the first publish

After publishing

Version

Draft — not yet published

v1, then v2, v3 and so on with each publish

Reference

Assigned on publish

A generated code, for example ISO14S001

The reference matters more than it looks. It is the stem every downstream code derives from: the audit record reference, then the finding references and root cause references all build on it. A template referenced ISO14S001 produces audit records and findings that trace visibly back to it.

Whether references are generated at all is a company-wide setting rather than a per-template one — see 10.8.

Related: 2.7 Using templates across several locations · 7.3 Understanding finding reference codes · 10.8 Reference codes

Did this answer your question?