---
sourceDocument: Brazil Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/governance-risk-compliance

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Template versioning

# Template versioning {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Template versioning

Template versioning in the Smart Assessment Engine allows organizations to manage multiple versions of assessment templates over time while maintaining continuity of ongoing assessments.
It ensures that even when templates are updated or retired, existing assessments remain linked to their original template versions.
This capability addresses challenges of previous methods that required copying templates, which disrupted response continuity and reporting.
Show full answer Show less  

## Template version lifecycle

* **Draft:** The version is editable, but assessments cannot be triggered, and post-assessment actions cannot be configured or published. Draft versions can be deleted.
* **Published:** The version is active for triggering new assessments. Direct editing is limited; minor edits are possible with Quick Edit, while major changes require creating a new version.
* **Retired:** The version is no longer used for new assessments but remains linked to existing assessments triggered from it. When a new version is published, the prior published version is automatically retired.

## Publishing behavior

Publishing a new template version automatically retires the previous version. Existing assessments retain their original version and are not migrated. New assessments use the newly published version. Trigger points configured on the template continue working without changes.

## Impact on copy response and reporting

Copy response and reporting rely on structural comparisons of questions across versions. If a question's type and label remain unchanged, responses are copied and aggregated across versions for consistent reporting. Structural changes to questions cause them to be treated as new, with responses not copied and reported separately, preserving accurate historical data.

## Impact on post-assessment actions

Post-assessment actions from the previous version are copied to the new version and set to draft. They must be reviewed and republished after the new version is published. Post-assessment actions can only be configured on published versions, ensuring actions referencing modified questions are validated before activation.

## Benefits for ServiceNow customers

* Enables evolving assessment templates without disrupting active assessments.
* Maintains permanent, version-specific records for conformance auditing and historical analysis.
* Preserves response continuity and reporting integrity across template updates.
* Eliminates manual updates to trigger points, flows, scripts, and related lists after template changes.
* Supports multi-language templates, ensuring internationalized content is versioned without loss.  
Template versioning enables organizations to maintain multiple versions of assessment templates over time. The ongoing assessments continue to exist even if a their related version is retired or superseded by new
versions.

## Template versioning overview {#template-versioning__section_cqf_ks5_23c}

As organizational requirements evolve, assessment templates must be updated to reflect new conformance standards, improved question sets, or refined evaluation criteria. Template Versioning provides a structured approach to
managing these changes while maintaining control over assessments that are already in progress.

When a template manager publishes a new version of an existing template, the system automatically retires the previous version. This promotes a clear version lineage and prevents confusion about which template version should be
used for new assessments. Template versioning introduces lifecycle management for assessment templates.

Before template versioning, updating a published template required copying it, modifying the copy, and updating every trigger move to use the new copy. This approach broke continuity. Copy responses from previous assessments did
not carry over, because the new template was technically a different template. Reporting was also impacted, and the historical evolution of the template was not preserved. Template versioning solves these problems by treating each
version as part of the same template lineage. Trigger points, copy responses, and reporting continue to work without reconfiguration.

From the template builder, the current version is shown in a version bar at the top of the template. The version bar displays the version number, lets you open the full version history.

## Template version lifecycle {#template-versioning__section_lifecycle_25c}

A template version moves through the following states:

Draft
:   The version is open for editing. You can modify question text, question type, option sets, sections, instructions, and the rest of the template structure. Assessments can't be triggered from a draft version. Post-assessment
    actions can't be configured or published while a version is in draft state. You can also delete a draft version using the Delete template action. This action is available only while the version is in the
    draft state; published and retired versions can't be deleted.

Published
:   The version is active and is used as the source for all new assessments triggered from this template. Direct editing of the published template is restricted; to change a published template, either use Quick edit for minor
    corrections (see [Quick edit for published templates](https://www.servicenow.com/docs/kMYGluuhtKoX8SIK9VPPzw "Quick Edit lets template managers make minor corrections to published templates without creating a version, enabling rapid fixes for typos and formatting issues while assessments remain in progress.")) or create version.

Retired
:   The version is no longer used as the source for new assessments. When a new version is published, the previously published version is retired automatically. Assessments that were already triggered from the retired version
    continue to use the version they started with.

You can create version from a published or retired version that already has at least one assessment triggered from it. You can't create version from a draft version and from a published template that has no assessments yet. If a
template is published but has no assessments, you can edit the published template directly until the first assessment is triggered.

## What happens when a version is published {#template-versioning__section_publish_impact_25c}

When you publish a new version of a template, the system applies the following behavior automatically:

* The previously published version is moved to the Retired state.
* Assessments that have already been triggered from the previous version continue to use the version they were triggered from. They aren't migrated to the new version.
* New assessments triggered after the publish use the newly published version.
* Trigger points configured against the template continue to work without any change.
{#template-versioning__ul_pub_impact_25c}

## Impact on copy response and reporting {#template-versioning__section_copy_response_impact_25c}

Copy response and reporting both rely on matching a question across template versions. A structural comparison determines whether two questions represent the same logical question.  
* If a question's type and label are unchanged in the new version, the question is treated as the same question across versions. Responses copied from a previous assessment are placed against this question in the new assessment, and reports continue to aggregate responses across versions.
* If a question's type or label has changed in the new version, the question is treated as a different question. Responses for the modified question aren't copied across versions, and the question is reported as a separate question across the lifetime of the template.
{#template-versioning__ul_question_identity_25c}

For example, consider a template with five questions where only question 3 is structurally modified. Questions 1, 2, 4, and 5 receive copied responses and are reported as the same question. Question 3 is treated as a new question starting from the new version.

## Impact on post-assessment actions {#template-versioning__section_paa_impact_25c}

Post-assessment actions from the previously published version are carried forward, but remain in draft state until you re-publish them.

* When you create version, all post-assessment actions from the previous version are copied to the new version and set to Draft.
* While the new template version is in draft state, you can't configure or publish post-assessment actions. Post-assessment actions can only be configured on a published template.
* After you publish the new template version, review the carried-over post-assessment actions, update any actions that depend on questions you modified, and publish them.

{#template-versioning__ul_paa_carryover_25c}This protects against publishing actions that reference questions you may have changed in the new version. For more information about post-assessment actions, see [Configure post-assessment actions](https://www.servicenow.com/docs/bYhyfPSpzmzcHAUjLTYhUA "The post-assessment actions feature in Smart Assessment Engine enables you to automate actions based on assessment responses. The template designers can predefine actions using a rule engine, such as updating fields, creating follow-up assessments, or generating other records.").

## Benefits of template versioning {#template-versioning__section_zgr_155_23c}

Template versioning in Smart Assessment Engine provides the following benefits:

* Organizations can evolve assessment templates to meet changing requirements without disrupting ongoing assessment programs.
* Completed assessments remain unchanged, maintaining a permanent record of which template version was used for each assessment.
* The system maintains complete version lineage, supporting conformance auditing and historical analysis.
* Reduces manual tracking of which assessments must be restarted or updated after template changes.
* Automated policy execution eliminates the need for administrators to manually review and update assessments after template changes.
* Trigger points continue to work after publishing a new version, eliminating the must manually update flows, scripts, or related lists that reference the template.
* Copy response from previous assessments continues to work for questions that have not been structurally changed across versions.
* Reports continue to aggregate responses across versions for unchanged questions, preserving longitudinal reporting.
* Supports templates maintained in multiple languages, so internationalized templates can be versioned without losing translated content.
{#template-versioning__ul_sf2_255_23c}
**Related topics**   

* [KB3013746](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3013746)