When you roll over an engagement, you can choose which engagement template version the new engagement should be based on. This allows you to pull in changes made to an engagement template since the prior engagement was created, helping your team stay aligned with the latest methodology.
This page explains how template updates work during rollover, what gets updated, what doesn’t, and how Fieldguide resolves conflicts between the prior engagement and the selected template version.
Before you begin
Your engagement must be linked to an engagement template that has at least one new version saved. Without this, the Select Version step won't appear in the rollover wizard.
Be prepared to complete the engagement rollover steps that occur before and after template version selection.
How it works
During engagement rollover, you'll see a step called Select version. Here, you can:
Keep the same template version the engagement already uses, or
Select a newer version of the engagement template.
Click View changes to see a side-by-side comparison of updates between the version currently in use and each newer template version available.
You can select any version that is equal to or newer than the version used in the original engagement.
This is part of the rollover flow, not a manual push. Selecting a template version happens only while you roll over an engagement, on the Select version step. It isn't a separate "update" button in the engagement template's options menu. To push specific template changes into an existing engagement outside of rollover, use the Update active sheets tool instead.
To learn how to access and complete the full rollover flow, see Engagement rollover.
What updates during rollover
Template updates apply to Sheets, Workflows, Documents, and Reports. These entities are fully replaced or updated according to the selected template version.
Supported entities
Sheets (includes primary sheets, document sheets, and scoping sheets)
Sheet structure
Sections
Rows
Columns
Views
Scoping sheet rules:
Row-level scoping rules
Section-level scoping rules
Sheet-level scoping rules
Sheet AI Actions
Workflows
Workflow-level scoping rules
Documents (including Document folders, the Documents column, and the Documents Reference column)
Forms
Reports
Agent trigger settings
Unsupported entities
The following items are not updated from the engagement template, even if the template version contains changes:
Non-sheets related elements: Requests, Tasks
Magic column content: Requests and Tasks
Row sync status
Client permissions
Sheet utility settings:
Control locks
Locked columns
Column rollover settings
Scoping rules for:
Financial Statements
Content Blocks
Some of the unsupported entities can still be pulled into the new engagement later through other methods, such as the Update active sheets tool.
How conflicts are resolved
When you select a newer template version, Fieldguide may encounter places where both the prior engagement and the template version contain changes. In these cases, Fieldguide resolves updates using the rules below.
Conflict resolution rules
Fieldguide uses the following logic for supported entities:
Scenario | Outcome |
Both the prior engagement and the template changed the same entity | Template wins (the template version’s update is applied) |
The template changed an entity and the prior engagement did not | Template wins |
The prior engagement changed an entity and the template did not | Engagement wins (your engagement’s existing change is preserved) |
Template deleted an entity | The entity is deleted in the new rolled-over engagement |
Template added a new entity | The entity is added to the new rolled-over engagement |
Viewing changes before finalizing rollover
On the Select version step, click View changes to preview differences between versions. The preview panel displays changes grouped by type, including:
Sheets
Sections
Columns
Expand each group to see what was added, removed, or updated. This helps you confirm whether updating to a newer template version will benefit your team before you proceed.
Cell-level data changes don't appear in the View changes on-screen preview. To export the complete set of changes, click Download Full Change Log in the View changes panel. This downloads a CSV you can review outside of Fieldguide.
If there are conflicts (updates made to both the template and the engagement) for entities whose changes aren't shown in the preview, the template wins. This keeps your engagement aligned with your firm's methodology.
How selecting a template version affects your rollover options
Selecting a template version does not change which configuration toggles appear on the Configure rollover page. You can still choose to carry forward or omit content such as Sheets, Requests, Documents, Forms, and other engagement items defined in the configuration page. The template update step is independent from these rollover selections.
When to use template updates
Template updates during rollover are especially helpful when:
Your firm periodically improves test procedures or methodology.
Teams add new scoping rules to improve risk-based scoping.
Sheets or columns have been redesigned for better efficiency.
Engagement teams want to keep engagements consistent year over year.
If your methodology has not changed—or if the older version is intentionally specific to a client—you can keep the existing version instead.
Engagement templates and versions are managed by your firm's admins. Consider the version names and descriptions your admins provided to help decide which one to use.