Versioning

Check templates support versioning to maintain an accurate audit trail when templates are updated over time.

Why versioning matters

In a compliance environment, it's important to know exactly which version of an inspection form was used for each check. If you change a template — adding a question, adjusting fail criteria, or updating the scoring model — the system needs to distinguish between checks performed under the old version and the new one.

How versioning works

Each template has a version number. When you edit a template:

• The version number is incremented
• A link to the parent template (the previous version) is maintained
• New check instances are created against the latest version
• Historical check instances retain a reference to the template version they were performed under

What gets versioned

Any change to a template's questions or settings creates a new version:

• Adding, removing, or reordering questions
• Changing question text, input types, or fail values
• Modifying scoring model, fail logic, or frequency rules
• Updating the auto-defect or mandatory attachment settings

Viewing version history

From the template detail page, you can see:

• The current version number
• A history of previous versions
• Which version was used for each completed check

Impact on scheduled checks

When a template is updated:

• Existing scheduled checks that haven't been started yet will use the latest version when performed
• Completed checks are permanently linked to the version they were performed under — they are never retroactively changed
• Check instances record the template_version at the time they are created

TIP

If you need to make a significant change to a template (e.g. a fundamentally different set of questions), consider creating a new template rather than editing the existing one. This makes it clearer in the audit trail that a new inspection regime was introduced.